Import buf from Catacomb; split out the dstr bits, and throw away the mp and

[mLib] / man / pkbuf.3

diff --git a/man/pkbuf.3 b/man/pkbuf.3
index cdc6bac33010c6306881178c4ae7fa14a6407a7c..4bcc9d371e9b65409124bf213ca075148d3d6fdb 100644 (file)
--- a/man/pkbuf.3
+++ b/man/pkbuf.3
@@ -78,7 +78,7 @@ This function is given three arguments: a pointer
 .I pk
 to a packet buffer structure; a pointer
 .I p
- to a chunk of data to read; and the size
+to a chunk of data to read; and the size
 .I sz
 of the chunk of data.  The data is pushed through the packet buffer and
 any complete packets are passed on to the packet handler.
@@ -128,7 +128,7 @@ each one in turn to the packet-handler function.
 The
 .B pkbuf_snarf
 function is trivially implemented in terms of the more complex
-.B pkbuf_free / pkbuf_flush
+.BR pkbuf_free / pkbuf_flush
 interface.
 .SS "Packet breaking and the handler function"
 The function
@@ -191,7 +191,7 @@ the object so that it doesn't see any more data.
 .PP
 Clearly, since an
 .B pkbuf_flush
-call can emit more than one packet, so it must be aware that the packet
+call can emit more than one packet, it must be aware that the packet
 handler isn't interested in any more packet.  However, this fact must
 also be signalled to the higher-level object so that it can detach
 itself from its data source.
@@ -222,4 +222,4 @@ general
 .BR selpk (3),
 .BR mLib (3).
 .SH "AUTHOR"
-Mark Wooding, <mdw@nsict.org>
+Mark Wooding, <mdw@distorted.org.uk>