cleanup: All the whitespace fixes, all at once.

[mLib] / man / lbuf.3

diff --git a/man/lbuf.3 b/man/lbuf.3
index b887130acddf927acd6a2eb4f4b6573e457bda0b..6595f30ceee75094cb72d32cd043806e440ec518 100644 (file)
--- a/man/lbuf.3
+++ b/man/lbuf.3
@@ -96,11 +96,11 @@ The complex interface is the pair of functions
 and
 .BR lbuf_flush .
 .PP
-The 
+The
 .B lbuf_free
 function returns the address and size of a free portion of the line
 buffer's memory into which data may be written.  The function is passed
-the address 
+the address
 .I b
 of the line buffer.  Its result is the size of the free area, and it
 writes the base address of this free space to the location pointed to by
@@ -207,18 +207,18 @@ the object so that it doesn't see any more data.
 .PP
 Clearly, since an
 .B lbuf_flush
-call can emit more than one line, so it must be aware that the line
-handler isn't interested in any more lines.  However, this fact must
-also be signalled to the higher-level object so that it can detach
-itself from its data source.
+call can emit more than one line, it must be aware that the line handler
+isn't interested in any more lines.  However, this fact must also be
+signalled to the higher-level object so that it can detach itself from
+its data source.
 .PP
 Rather than invent some complex interface for this, the line buffer
-exports one of its structure members,
-.BR flags .
+exports one of its structure members, a flags word called
+.BR f .
 A higher-level object wishing to disable the line buffer simply clears
 the bit
 .B LBUF_ENABLE
-in the flags word.
+in this flags word.
 .PP
 Disabling a buffer causes an immediate return from
 .BR lbuf_flush .
@@ -237,4 +237,4 @@ general
 .BR selbuf (3),
 .BR mLib (3).
 .SH "AUTHOR"
-Mark Wooding, <mdw@nsict.org>
+Mark Wooding, <mdw@distorted.org.uk>