Imported Upstream version 1.72.0

[platform/upstream/boost.git] / doc / html / boost_asio / overview / networking / bsd_sockets.html

diff --git a/doc/html/boost_asio/overview/networking/bsd_sockets.html b/doc/html/boost_asio/overview/networking/bsd_sockets.html
index 7b4209e..ba7538e 100644 (file)
--- a/doc/html/boost_asio/overview/networking/bsd_sockets.html
+++ b/doc/html/boost_asio/overview/networking/bsd_sockets.html
@@ -37,10 +37,10 @@
           data copying, minimise the use of resources like threads, and so on.
         </p>
 <p>
-          Unsafe and error prone aspects of the BSD socket API not included. For
-          example, the use of <code class="computeroutput">int</code> 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 <code class="computeroutput">ip::tcp::socket</code>,
+          Unsafe and error prone aspects of the BSD socket API are not included.
+          For example, the use of <code class="computeroutput">int</code> 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 <code class="computeroutput">ip::tcp::socket</code>,
           and for UDP one uses <code class="computeroutput">ip::udp::socket</code>.
         </p>
 <p>