From 8eb05fddab0dd125579b5c7fb9266420ee7d668a Mon Sep 17 00:00:00 2001 From: Yuri Goldfeld Date: Wed, 15 Jan 2025 11:22:06 -0800 Subject: [PATCH] Comment and/or doc changes. --- src/flow/net_flow/detail/socket_buffer.hpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/flow/net_flow/detail/socket_buffer.hpp b/src/flow/net_flow/detail/socket_buffer.hpp index 5eaa342ab..ba8500f37 100644 --- a/src/flow/net_flow/detail/socket_buffer.hpp +++ b/src/flow/net_flow/detail/socket_buffer.hpp @@ -150,7 +150,7 @@ class Socket_buffer : * Type that models the boost.asio `ConstBufferSequence` concept (see Boost docs). * Basically, it's any container with elements convertible to `boost::asio::const_buffer`; * and bidirectional iterator support. Examples: `vector`, `list`. - * Why allow `const_buffer` instead of, say, Sequence of bytes? Same reason as boost.asio's + * Why allow `const_buffer` instead of, say, `Sequence` of bytes? Same reason as boost.asio's * send functions: it allows a great amount of flexibility without sacrificing performance, * since `boost::asio::buffer()` function can adapt lots of different objects (arrays, * vectors, strings, and more of bytes, integers, and more). @@ -199,7 +199,7 @@ class Socket_buffer : * Type that models the boost.asio `MutableBufferSequence` concept (see Boost docs). * Basically, it's any container with elements convertible to `boost::asio::mutable_buffer`; * and bidirectional iterator support. Examples: `vector`, - * l`ist.` Why allow `mutable_buffer` instead of, say, Sequence of bytes? + * `list.` Why allow `mutable_buffer` instead of, say, `Sequence` of bytes? * Same reason as boost.asio's receive functions: it allows a great amount of flexibility * without sacrificing performance, since `boost::asio::buffer()` function can adapt lots of * different objects (arrays, `vector`s, `string`s, and more of bytes, integers, and more).