15 files changed, 108 insertions, 92 deletions
diff --git a/libexec/ftp-proxy/ftp-proxy.8 b/libexec/ftp-proxy/ftp-proxy.8
index 830cbcfc0c3..52a2b9c703e 100644
--- a/libexec/ftp-proxy/ftp-proxy.8
+++ b/libexec/ftp-proxy/ftp-proxy.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ftp-proxy.8,v 1.30 2003/01/31 21:54:40 jmc Exp $
+.\"	$OpenBSD: ftp-proxy.8,v 1.31 2003/02/26 15:05:07 david Exp $
 .\"
 .\" Copyright (c) 1996-2001
 .\"	Obtuse Systems Corporation, All rights reserved.
@@ -200,7 +200,8 @@ statefully:
 .Pp
 Alternatively, rules can make use of the fact that by default,
 .Nm ftp-proxy
-runs as user "proxy" to allow the backchannel connections, as in the following example:
+runs as user "proxy" to allow the backchannel connections, as in the
+following example:
 .Bd -literal
   block in on $ext_if proto tcp all
   pass  in on $ext_if inet proto tcp from any to $ext_if \\
@@ -208,8 +209,9 @@ runs as user "proxy" to allow the backchannel connections, as in the following e
 .Ed
 .Pp
 These examples do not cover the connections from the proxy to the
-foreign ftp server. If one does not pass outgoing connections by default
-additional rules are needed.
+foreign ftp server.
+If one does not pass outgoing connections by default additional rules
+are needed.
 .Sh SEE ALSO
 .Xr ftp 1 ,
 .Xr pf 4 ,
diff --git a/libexec/spamd/spamd.8 b/libexec/spamd/spamd.8
index 8e26f1947cc..99fe382d0ce 100644
--- a/libexec/spamd/spamd.8
+++ b/libexec/spamd/spamd.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: spamd.8,v 1.10 2003/02/13 08:23:39 jmc Exp $
+.\"	$OpenBSD: spamd.8,v 1.11 2003/02/26 15:05:07 david Exp $
 .\"
 .\" Copyright (c) 2002 Theo de Raadt.  All rights reserved.
 .\"
@@ -59,8 +59,8 @@ does not
 .Xr fork 2
 into the background.
 .It Fl r
-The SMTP error to return to the spammer, ie 450, 451, 550.  This defaults
-to 450.
+The SMTP error to return to the spammer, i.e., 450, 451, 550.
+This defaults to 450.
 .It Fl c
 The maximum number of concurrent connections to allow.
 .It Fl p
@@ -73,9 +73,11 @@ The SMTP version banner that is reported upon initial connection.
 .Pp
 .Nm
 is designed to be very efficient so that it does not slow down the
-receiving machine.  SPAM is never accepted, but always rejected with
-either a 450 or 550 error message.  The normal way that SPAM has been
-dealt with in the past is to either accept and drop, or outright block.
+receiving machine.
+SPAM is never accepted, but always rejected with either a 450 or 550
+error message.
+The normal way that SPAM has been dealt with in the past is to either
+accept and drop, or outright block.
 When configured to use 450 responses,
 .Nm
 takes neither of these actions: it rejects the mail back to the senders'
diff --git a/libexec/telnetd/telnetd.8 b/libexec/telnetd/telnetd.8
index 0499f720e4e..14980bc054b 100644
--- a/libexec/telnetd/telnetd.8
+++ b/libexec/telnetd/telnetd.8
@@ -203,11 +203,13 @@ This option is only enabled when
 is compiled for
 .Dv UNICOS .
 It specifies an inclusive range of pseudo-terminal devices to
-use.  If the system has sysconf variable
+use.
+If the system has sysconf variable
 .Dv _SC_CRAY_NPTY
 configured, the default pty search range is 0 to
 .Dv _SC_CRAY_NPTY ;
-otherwise, the default range is 0 to 128.  Either
+otherwise, the default range is 0 to 128.
+Either
 .Ar lowpty
 or
 .Ar highpty
diff --git a/share/man/man4/man4.hppa/gsc.4 b/share/man/man4/man4.hppa/gsc.4
index faa93a89c94..ab46a33bf42 100644
--- a/share/man/man4/man4.hppa/gsc.4
+++ b/share/man/man4/man4.hppa/gsc.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: gsc.4,v 1.9 2003/01/31 23:03:12 miod Exp $
+.\"	$OpenBSD: gsc.4,v 1.10 2003/02/26 15:05:07 david Exp $
 .\"
 .\"
 .\" Copyright (c) 1999 Michael Shalayeff
@@ -40,16 +40,16 @@
 .Cd "gsc* at asp?"
 .Cd "gsc* at wax?"
 .Sh DESCRIPTION
-This is core I/O bus for all HP9000/700 series workstations. All I/O subsystems
-connect to this bus.
+This is core I/O bus for all HP9000/700 series workstations.
+All I/O subsystems connect to this bus.
 The devices can be either on seperate chips, expansion
 cards or on an integrated megacell, like the LASI MBA.
 .Pp
 The
 .Tn GSC
-bus is a 32-bit wide, address and data multiplexed bus. In its "standard"
-implementation it has a maximum throughput of 160MB/s, the "2x" implementation
-reaches up to 250MB/s.
+bus is a 32-bit wide, address and data multiplexed bus.
+In its "standard" implementation it has a maximum throughput of 160MB/s,
+the "2x" implementation reaches up to 250MB/s.
 Some HPPA CPUs directly attach to this bus, namely the PA7100LC and PA7300LC.
 .Pp
 As for the expansion cards, there appeared different form-factors, depending on
diff --git a/share/man/man4/man4.hppa/ie.4 b/share/man/man4/man4.hppa/ie.4
index a2c8a0a9615..c81a00e52fe 100644
--- a/share/man/man4/man4.hppa/ie.4
+++ b/share/man/man4/man4.hppa/ie.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ie.4,v 1.5 2003/01/07 20:37:10 mickey Exp $
+.\"	$OpenBSD: ie.4,v 1.6 2003/02/26 15:05:07 david Exp $
 .\"
 .\" Copyright (c) 2001 Paul Weissmann
 .\" All rights reserved.
@@ -67,11 +67,13 @@ The i82596 comes basically in two different flavors:
 .It i82596DX
 Systems with an ASP or WAX Main Bus Adapter (MBA), e.g. 720, 735 etc.
 These types of systems generally have only AUI or BNC and AUI connectors at
-the back. On the models with both you usually have to switch a big
+the back.
+On the models with both you usually have to switch a big
 jumper-block on the mainboard to choose which one to activate.
 .It i82596CA
 Systems with LASI MBA, e.g. 712/*, 715/100 have the i82596CA 
-integrated on the LASI macrochip. They usually have TP and AUI 
+integrated on the LASI macrochip.
+They usually have TP and AUI 
 connectors and autodetect to which one the network is connected to.
 .El
 .Pp
diff --git a/share/man/man4/man4.i386/elansc.4 b/share/man/man4/man4.i386/elansc.4
index 49d45dc8fa1..bf2505d762c 100644
--- a/share/man/man4/man4.i386/elansc.4
+++ b/share/man/man4/man4.i386/elansc.4
@@ -50,15 +50,15 @@ The SC520 consists of an AMD Am5x86 processor core, integrated PCI host
 controller, and several standard on-chip devices, such as NS16550-compatible
 UARTs, real-time clock, and timers.
 .Pp
-The Elan SC520 also provides several special on-chip devices.  The following
-are supported by the
+The Elan SC520 also provides several special on-chip devices.
+The following are supported by the
 .Nm
 driver:
 .Bl -bullet
 .It
-Watchdog timer.  The watchdog timer may be configured for a 1
-second, 2 second, 4 second, 8 second, 16 second, or 32 second
-expiration period.
+Watchdog timer.
+The watchdog timer may be configured for a 1 second, 2 second, 4 second,
+8 second, 16 second, or 32 second expiration period.
 .El
 .Sh SEE ALSO
 .Xr sysctl 8
diff --git a/share/man/man4/ubsec.4 b/share/man/man4/ubsec.4
index 542ddae281e..dd19d3c2b82 100644
--- a/share/man/man4/ubsec.4
+++ b/share/man/man4/ubsec.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ubsec.4,v 1.20 2002/11/08 08:08:47 mpech Exp $
+.\"	$OpenBSD: ubsec.4,v 1.21 2003/02/26 15:05:07 david Exp $
 .\"
 .\" Copyright (c) 2000 Jason L. Wright (jason@thought.net)
 .\" All rights reserved.
@@ -93,5 +93,5 @@ The
 device driver appeared in
 .Ox 2.8 .
 .Sh BUGS
-The BCM5801 and BCM5802 have not actually been tested.  The Sun Crypto
-Accelerator 1000 is suspected to be a Broadcom 5821.
+The BCM5801 and BCM5802 have not actually been tested.
+The Sun Crypto Accelerator 1000 is suspected to be a Broadcom 5821.
diff --git a/share/man/man5/elf.5 b/share/man/man5/elf.5
index f5efb5b969c..f64d4dcb43e 100644
--- a/share/man/man5/elf.5
+++ b/share/man/man5/elf.5
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: elf.5,v 1.3 2003/01/17 17:48:55 millert Exp $
+.\"	$OpenBSD: elf.5,v 1.4 2003/02/26 15:05:07 david Exp $
 .\"Copyright (c) 1999 Jeroen Ruigrok van der Werven
 .\"All rights reserved.
 .\"
@@ -352,8 +352,8 @@ If the
 file has no section header table this member holds zero.
 .It Dv e_flags
 This member holds processor-specific flags associated with the file.
-Flag
-names take the form EF_`machine_flag'. Currently no flags have been defined.
+Flag names take the form EF_`machine_flag'.
+Currently no flags have been defined.
 .It Dv e_ehsize
 This member holds the ELF header's size in bytes.
 .It Dv e_phentsize
@@ -519,10 +519,9 @@ The array element specifies dynamic linking information.
 The array element specifies the location and size of a null-terminated
 path name to invoke as an interpreter.
 This segment type is meaningful
-only for executable files (though it may occur for shared objects). However
-it may not occur more than once in a file.
-If it is present it must precede
-any loadable segment entry.
+only for executable files (though it may occur for shared objects).
+However it may not occur more than once in a file.
+If it is present it must precede any loadable segment entry.
 .It Dv PT_NOTE
 The array element specifies the location and size for auxiliary information.
 .It Dv PT_SHLIB
diff --git a/share/man/man5/genassym.cf.5 b/share/man/man5/genassym.cf.5
index 11bd766315c..41a79a7aed8 100644
--- a/share/man/man5/genassym.cf.5
+++ b/share/man/man5/genassym.cf.5
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: genassym.cf.5,v 1.3 2003/01/18 23:40:58 deraadt Exp $
+.\"	$OpenBSD: genassym.cf.5,v 1.4 2003/02/26 15:05:07 david Exp $
 .\"	$NetBSD: genassym.cf.5,v 1.8 2001/06/19 12:34:27 wiz Exp $
 .\"
 .\" Copyright (c) 1997 Matthias Pfaller.
@@ -115,10 +115,10 @@ can be used to customize the output of
 .Xr genassym.sh 8 .
 .br
 When producing C output, values are cast to <ctype> (default: long)
-before they get handed to printf. <gcc constraint> (default: n) is the
-constraint used in the __asm__ statements. <asm print modifier> (default:
-empty) can be used to force gcc to output operands in different ways
-than normal.
+before they get handed to printf.
+<gcc constraint> (default: n) is the constraint used in the __asm__ statements.
+<asm print modifier> (default: empty) can be used to force gcc to output
+operands in different ways than normal.
 The "a" modifier e.g. stops gcc from emitting immediate
 prefixes in front of constants for the i386 and m68k port.
 .Sh FILES
diff --git a/share/man/man8/genassym.sh.8 b/share/man/man8/genassym.sh.8
index 5b4773a88a9..8993ec0296d 100644
--- a/share/man/man8/genassym.sh.8
+++ b/share/man/man8/genassym.sh.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: genassym.sh.8,v 1.4 2002/11/08 08:08:47 mpech Exp $
+.\"	$OpenBSD: genassym.sh.8,v 1.5 2003/02/26 15:05:07 david Exp $
 .\"	$NetBSD: genassym.sh.8,v 1.5 1999/03/17 20:31:19 garbled Exp $
 .\"
 .\" Copyright (c) 1997 Matthias Pfaller.
@@ -81,7 +81,8 @@ The
 flag instructs
 .Nm
 to create slightly different code, generate an executable from this code
-and run it. In both cases the assym.h file is written to stdout.
+and run it.
+In both cases the assym.h file is written to stdout.
 .Sh DIAGNOSTICS
 Either self-explanatory, or generated by one of the programs
 called from the script.
diff --git a/share/man/man8/ssl.8 b/share/man/man8/ssl.8
index 220832fecb5..7d0cccfcf29 100644
--- a/share/man/man8/ssl.8
+++ b/share/man/man8/ssl.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ssl.8,v 1.40 2003/02/15 11:45:53 deraadt Exp $
+.\"	$OpenBSD: ssl.8,v 1.41 2003/02/26 15:05:07 david Exp $
 .\" 
 .\" Copyright (c) 1999 Theo de Raadt, Bob Beck
 .\" All rights reserved.
@@ -96,9 +96,9 @@ directory.
 Private keys can be encrypted using
 .Ar 3DES
 and a passphrase to protect their integrity should the encrypted file
-be disclosed. However, it is
-important to note that encrypted server keys mean that the passphrase
-needs to be typed in every time the server is started.
+be disclosed.
+However, it is important to note that encrypted server keys mean that the
+passphrase needs to be typed in every time the server is started.
 If a passphrase is not used, you will need to be absolutely sure your
 key file is kept secure.
 .Sh GENERATING DSA SERVER CERTIFICATES
diff --git a/share/man/man9/mbuf_tags.9 b/share/man/man9/mbuf_tags.9
index fb8fd9cb026..38e134c3319 100644
--- a/share/man/man9/mbuf_tags.9
+++ b/share/man/man9/mbuf_tags.9
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: mbuf_tags.9,v 1.13 2002/09/30 23:30:47 frantzen Exp $
+.\"	$OpenBSD: mbuf_tags.9,v 1.14 2003/02/26 15:05:07 david Exp $
 .\"
 .\" The author of this man page is Angelos D. Keromytis (angelos@cis.upenn.edu)
 .\"
@@ -180,9 +180,9 @@ Contains no data.
 Used to mark fragmented packets cached by the packet filter
 .Xr pf 4 .
 Packets with this tag have been cached by the fragment cache already
-and will short circuit it if processed again.  If they were to re-enter
-the fragcache, they would be indistinguishable from a duplicate of a
-previous packet and would be dropped.
+and will short circuit it if processed again.
+If they were to re-enter the fragcache, they would be indistinguishable
+from a duplicate of a previous packet and would be dropped.
 Contains no data.
 .El
 .Pp
diff --git a/share/man/man9/style.9 b/share/man/man9/style.9
index f9c44597f36..f4229630855 100644
--- a/share/man/man9/style.9
+++ b/share/man/man9/style.9
@@ -22,7 +22,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"	$OpenBSD: style.9,v 1.30 2003/02/25 08:51:31 jmc Exp $
+.\"	$OpenBSD: style.9,v 1.31 2003/02/26 15:05:07 david Exp $
 .\"
 .Dd June 18, 2001
 .Dt STYLE 9
@@ -500,8 +500,8 @@ volatile char *volatile foo;
 .Ed
 .Pp
 .Dq const
-is also a type-qualifier and the same rules apply.  The description of
-a read-only hardware register might look something like:
+is also a type-qualifier and the same rules apply.
+The description of a read-only hardware register might look something like:
 .Bd -literal -offset 0i
 const volatile char *reg;
 .Ed
diff --git a/share/man/man9/vnode.9 b/share/man/man9/vnode.9
index 9d9a71b7468..160349f55aa 100644
--- a/share/man/man9/vnode.9
+++ b/share/man/man9/vnode.9
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: vnode.9,v 1.13 2003/01/27 09:19:30 art Exp $
+.\"     $OpenBSD: vnode.9,v 1.14 2003/02/26 15:05:07 david Exp $
 .\"
 .\" Copyright (c) 2001 Constantine Sapuntzakis
 .\" All rights reserved.
@@ -31,8 +31,8 @@
 .Nd an overview of vnodes
 .Sh DESCRIPTION
 A vnode is an object in kernel memory that speaks the UNIX file
-interface (open, read, write, close, readdir, etc.). Vnodes can
-represent files, directories, FIFOs, domain sockets, block devices,
+interface (open, read, write, close, readdir, etc.).
+Vnodes can represent files, directories, FIFOs, domain sockets, block devices,
 character devices.
 .Pp
 Each vnode has a set of methods which start with string 'VOP_'.
@@ -47,37 +47,41 @@ File systems cannot allocate their own vnodes; they must use the functions
 provided by the VFS to create and manage vnodes.
 .Ss Vnode life cycle
 When a client of the VFS requests a new vnode, the vnode allocation
-code can reuse an old vnode object that is no longer in use.  Whether
-a vnode is in use is tracked by the vnode reference count
-(v_usecount). By convention, each open file handle holds a reference
-as do VM objects backed by files. A vnode with a reference count of 1
-or more will not be de-allocated or re-used to point to a different
-file. So, if you want to ensure that your vnode doesn't become a different
-file under you, you better be sure you have a reference to it. A vnode
-that points to a valid file and has a reference count of 1 or more is called
-"active".
+code can reuse an old vnode object that is no longer in use.
+Whether a vnode is in use is tracked by the vnode reference count
+(v_usecount).
+By convention, each open file handle holds a reference
+as do VM objects backed by files.
+A vnode with a reference count of 1 or more will not be de-allocated or
+re-used to point to a different file.
+So, if you want to ensure that your vnode doesn't become a different
+file under you, you better be sure you have a reference to it.
+A vnode that points to a valid file and has a reference count of 1 or more
+is called "active".
 .Pp
 When a vnode's reference count drops to zero, it becomes "inactive",
-that is, a candidate for reuse. An "inactive" vnode still refers to a
-valid file and one can try to reactivate it using vget (this is used a
-lot by caches).
+that is, a candidate for reuse.
+An "inactive" vnode still refers to a valid file and one can try to
+reactivate it using vget (this is used a lot by caches).
 .Pp
 Before the VFS can reuse an inactive vnode to refer to another file,
-it must clean all information pertaining to the old file. A cleaned
-out vnode is called a "reclaimed" vnode.
+it must clean all information pertaining to the old file.
+A cleaned out vnode is called a "reclaimed" vnode.
 .Pp
 To support forceable unmounts and the 
 .Xr revoke 2
 system call, the VFS may "reclaim" a vnode with a positive reference
-count. The "reclaimed" vnode is given to the dead file system, which
-returns errors for most operations.  The reclaimed vnode will not be
+count.
+The "reclaimed" vnode is given to the dead file system, which
+returns errors for most operations.
+The reclaimed vnode will not be
 re-used for another file until its reference count hits zero.
 .Ss Vnode pool
 The
 .Xr getnewvnode 9 
 system call allocates a vnode from the pool, possible reusing an
-"inactive" vnode, and returns it to the caller. The vnode returned has
-a reference count (v_usecount) of 1.
+"inactive" vnode, and returns it to the caller.
+The vnode returned has a reference count (v_usecount) of 1.
 .Pp
 The 
 .Xr vref 9 
@@ -120,28 +124,30 @@ The vnode lock and its consistent use accomplishes the following:
 .Bl -bullet
 .It
 It keeps a locked vnode from changing across certain pairs of VOP_ calls,
-thus preserving cached data. For example, it keeps the directory from
-changing between a VOP_LOOKUP call and a VOP_CREATE. The VOP_LOOKUP
-call makes sure the name doesn't already exist in the directory and
-finds free room in the directory for the new entry. The VOP_CREATE can
-then go ahead and create the file without checking if it already
-exists or looking for free space.
+thus preserving cached data.
+For example, it keeps the directory from
+changing between a VOP_LOOKUP call and a VOP_CREATE.
+The VOP_LOOKUP call makes sure the name doesn't already exist in the
+directory and finds free room in the directory for the new entry.
+The VOP_CREATE can then go ahead and create the file without checking if
+it already exists or looking for free space.
 .It
 Some file systems rely on it to ensure that only one "thread" at a time
-is calling VOP_ vnode operations on a given file or directory. Otherwise,
-the file system's behavior is undefined.
+is calling VOP_ vnode operations on a given file or directory.
+Otherwise, the file system's behavior is undefined.
 .It
 On rare occasions, code will hold the vnode lock so that a series of
-VOP_ operations occurs as an atomic unit. (Of course, this doesn't
-work with network file systems like NFSv2 that don't have any notion
-of bundling a bunch of operations into an atomic unit)
+VOP_ operations occurs as an atomic unit.
+(Of course, this doesn't work with network file systems like NFSv2 that don't
+have any notion of bundling a bunch of operations into an atomic unit)
 .It
 While the vnode lock is held, the vnode will not be reclaimed.
 .El
 .Pp
-There is a discipline to using the vnode lock. Some VOP_ operations
-require that the vnode lock is held before being called. A description
-of this rather arcane locking discipline is in sys/kern/vnode_if.src.
+There is a discipline to using the vnode lock.
+Some VOP_ operations require that the vnode lock is held before being called.
+A description of this rather arcane locking discipline is in
+sys/kern/vnode_if.src.
 .Pp
 The vnode lock is acquired by calling 
 .Xr vn_lock 9 
@@ -151,7 +157,8 @@ and released by calling
 A process is allowed to sleep while holding the vnode lock.
 .Pp
 The implementation of the vnode lock is the responsibility of the individual
-file systems. Not all file systems implement it.
+file systems.
+Not all file systems implement it.
 .Pp
 To prevent deadlocks, when acquiring locks on multiple vnodes, the lock
 of parent directory must be acquired before the lock on the child directory.
diff --git a/share/man/man9/vwaitforio.9 b/share/man/man9/vwaitforio.9
index 43ed11b2779..2f9bca817eb 100644
--- a/share/man/man9/vwaitforio.9
+++ b/share/man/man9/vwaitforio.9
@@ -1,4 +1,4 @@
-.\"     $OpenBSD: vwaitforio.9,v 1.6 2002/12/20 06:16:34 art Exp $
+.\"     $OpenBSD: vwaitforio.9,v 1.7 2003/02/26 15:05:07 david Exp $
 .\"
 .\" Copyright (c) 2001 Constantine Sapuntzakis
 .\" All rights reserved.
@@ -45,7 +45,8 @@ that the writes they initiated have completed.
 .Pp
 The
 .Fn vwaitforio
-call sleeps at PRIBIO + 1. The 
+call sleeps at PRIBIO + 1.
+The 
 .Nm slpflag ,
 .Nm wmesg , 
 and