Imported Upstream version 1.72.0

[platform/upstream/boost.git] / libs / asio / doc / overview / bsd_sockets.qbk

diff --git a/libs/asio/doc/overview/bsd_sockets.qbk b/libs/asio/doc/overview/bsd_sockets.qbk
index 2c78500..0628d8f 100644 (file)
--- a/libs/asio/doc/overview/bsd_sockets.qbk
+++ b/libs/asio/doc/overview/bsd_sockets.qbk
@@ -15,10 +15,10 @@ scalable applications. For example, it permits programmers to exert finer
 control over the number of system calls, avoid redundant data copying, minimise
 the use of resources like threads, and so on.
 
-Unsafe and error prone aspects of the BSD socket API not included. For example,
-the use of `int` to represent all sockets lacks type safety. The socket
-representation in Boost.Asio uses a distinct type for each protocol, e.g. for TCP one
-would use `ip::tcp::socket`, and for UDP one uses `ip::udp::socket`.
+Unsafe and error prone aspects of the BSD socket API are not included. For
+example, the use of `int` to represent all sockets lacks type safety. The
+socket representation in Boost.Asio uses a distinct type for each protocol, e.g. for
+TCP one would use `ip::tcp::socket`, and for UDP one uses `ip::udp::socket`.
 
 The following table shows the mapping between the BSD socket API and Boost.Asio: