typos;

ok millert@

9 files changed, 57 insertions, 54 deletions

diff --git a/share/man/man4/idp.4 b/share/man/man4/idp.4
index f31de5f14dd..3097ed0b2c2 100644
--- a/share/man/man4/idp.4
+++ b/share/man/man4/idp.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: idp.4,v 1.7 2001/11/13 13:54:25 mpech Exp $
+.\"	$OpenBSD: idp.4,v 1.8 2003/03/20 07:26:33 jmc Exp $
 .\"	$NetBSD: idp.4,v 1.3 1994/11/30 16:22:15 jtc Exp $
 .\"
 .\" Copyright (c) 1985, 1991, 1993
@@ -83,12 +83,12 @@ Note that the
 port
 space is the same as the
 .Tn SPP
-port space (i.e. a
+port space (i.e. an
 .Tn IDP
 port
 may be
 .Dq connected
-to a
+to an
 .Tn SPP
 port, with certain
 options enabled below).
diff --git a/share/man/man4/inet.4 b/share/man/man4/inet.4
index 2233eb767ad..967774fb52d 100644
--- a/share/man/man4/inet.4
+++ b/share/man/man4/inet.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: inet.4,v 1.9 2001/11/13 13:54:25 mpech Exp $
+.\"	$OpenBSD: inet.4,v 1.10 2003/03/20 07:26:33 jmc Exp $
 .\"	$NetBSD: inet.4,v 1.3 1994/11/30 16:22:18 jtc Exp $
 .\"
 .\" Copyright (c) 1983, 1991, 1993
@@ -134,7 +134,7 @@ number.
 Class B addresses use the high-order 16 bits as the network field,
 and Class C addresses have a 24-bit network part.
 Sites with a cluster of local networks and a connection to the
-Internet may chose to use a single network number for the cluster;
+Internet may choose to use a single network number for the cluster;
 this is done by using subnet addressing.
 The local (host) portion of the address is further subdivided
 into subnet and host parts.
diff --git a/share/man/man4/iop.4 b/share/man/man4/iop.4
index fef1073f9b4..5ac89297edc 100644
--- a/share/man/man4/iop.4
+++ b/share/man/man4/iop.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: iop.4,v 1.6 2002/09/26 07:55:40 miod Exp $
+.\"	$OpenBSD: iop.4,v 1.7 2003/03/20 07:26:33 jmc Exp $
 .\"	$NetBSD: iop.4,v 1.7 2001/03/20 13:09:19 ad Exp $
 .\"
 .\" Copyright (c) 2000 The NetBSD Foundation, Inc.
@@ -59,12 +59,12 @@ I/O processors conforming to the
 specification, revision 1.5 and above.
 .Sh IOCTL INTERFACE
 The following structures and constants are defined in
-.Pa dev/i2o/iopio.h .
+.Aq Pa dev/i2o/iopio.h .
 Note that the headers
-.Pa sys/types.h ,
-.Pa sys/device.h
+.Aq Pa sys/types.h ,
+.Aq Pa sys/device.h
 and
-.Pa dev/i2o/i2o.h
+.Aq Pa dev/i2o/i2o.h
 are prerequisites and must therefore be included beforehand.
 .Bl -tag -width OTTF
 .It Dv IOPIOCPT (struct ioppt)
@@ -143,8 +143,8 @@ control device for IOP unit
 .Xr intro 4 ,
 .Xr ioprbs 4 ,
 .Xr iopsp 4 ,
-.Xr scsibus 4 ,
 .Xr pci 4 ,
+.Xr scsibus 4 ,
 .Xr iopctl 8
 .Pp
 http://www.intelligent-io.com/
diff --git a/share/man/man4/ipsec.4 b/share/man/man4/ipsec.4
index 64bc4d7e57f..6eb27491036 100644
--- a/share/man/man4/ipsec.4
+++ b/share/man/man4/ipsec.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ipsec.4,v 1.52 2003/01/13 19:16:34 kjell Exp $
+.\" $OpenBSD: ipsec.4,v 1.53 2003/03/20 07:26:33 jmc Exp $
 .\"
 .\" Copyright 1997 Niels Provos <provos@physnet.uni-hamburg.de>
 .\" All rights reserved.
@@ -116,7 +116,7 @@ follows the
 .Tn IP
 header).
 Replay protection requires authentication and
-integrity (these two go always together).
+integrity (these two always go together).
 Confidentiality (encryption) can be used with or without
 authentication/integrity.
 Similarly, one could use authentication/integrity with or without
@@ -153,11 +153,11 @@ When two peers have established matching
 .Tn SAs
 (one at each end),
 packets protected with one end's
-.Tn SA ,
+.Tn SA
 may be verified and/or decrypted
 using the information in the other end's
 .Tn SA.
-The only issue remaining left is to ensure that both ends have matching
+The only issue remaining is to ensure that both ends have matching
 .Tn SAs .
 This may be done manually, or automatically using a key management daemon.
 .Pp
@@ -199,15 +199,15 @@ confidentiality.
 Both the algorithm and the encryption key are parameters of the SA.
 .Pp
 .Ss Security Parameter Indexes (SPIs)
-In order to identify a SA we need to have a unique name for it.
+In order to identify an SA we need to have a unique name for it.
 This name is a triplet, consisting of the destination address, security
 parameter index (aka SPI) and the security protocol (ESP or AH).
-Since the destination address is part of the name, a SA is necessarily a
+Since the destination address is part of the name, an SA is necessarily a
 unidirectional construct.
 For a bidirectional communication channel, two SAs are required, one
 outgoing and one incoming, where the destination address is our local
 IP address.
-The SPI is just a number that helps us making the name unique, it can be
+The SPI is just a number that helps us make the name unique, it can be
 arbitrarily chosen in the range 0x100 - 0xffffffff.
 The security protocol number should be 50 for
 .Tn ESP
@@ -232,7 +232,7 @@ Tunnel mode can be used for establishing VPNs, virtual
 private networks, where parts of the networks can be spread out over an
 unsafe public network, but security gateways at each subnet are responsible
 for encrypting and decrypting the data passing over the public net.
-A SA will hold information telling if it is a tunnel or transport mode SA,
+An SA will hold information telling if it is a tunnel or transport mode SA,
 and for tunnels, it will contain values to fill in into the outer
 .Tn IP
 header.
@@ -240,7 +240,7 @@ header.
 .Ss Lifetimes
 The SA also holds a couple of other parameters, especially useful for
 automatic keying, called lifetimes, which puts a limit on how much we can
-use a SA for protecting our data.
+use an SA for protecting our data.
 These limits can be in wall-clock time or in volume of our data.
 .Pp
 .Ss IPsec Examples
@@ -412,8 +412,7 @@ A list of all security associations in the kernel tables can be
 obtained via the kernfs file
 .Aq Pa ipsec
 (typically in
-.Aq Pa /kern/ipsec
-).
+.Aq Pa /kern/ipsec ) .
 .Sh DIAGNOSTICS
 A socket operation may fail with one of the following errors returned:
 .Bl -tag -width [EINVAL]
diff --git a/share/man/man4/isa.4 b/share/man/man4/isa.4
index 4617c8db144..f1716a2d537 100644
--- a/share/man/man4/isa.4
+++ b/share/man/man4/isa.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: isa.4,v 1.21 2002/12/31 16:22:26 miod Exp $
+.\"	$OpenBSD: isa.4,v 1.22 2003/03/20 07:26:33 jmc Exp $
 .\"	$NetBSD: isa.4,v 1.19 2000/03/18 16:54:37 augustss Exp $
 .\"
 .\" Copyright (c) 2000 Theo de Raadt.  All rights reserved.
@@ -64,7 +64,7 @@ Your system may support additional
 devices.
 Drivers for
 .Tn ISA
-device not listed here are machine-dependent.
+devices not listed here are machine-dependent.
 Consult your system's
 .Xr intro 4
 for additional information.
@@ -284,8 +284,8 @@ These are listed in
 .Xr sb 4 ,
 .Xr sea 4 ,
 .Xr sf2r 4 ,
-.Xr sm 4 ,
 .Xr sfr 4 ,
+.Xr sm 4 ,
 .Xr uha 4 ,
 .Xr usb 4 ,
 .Xr wdc 4 ,
diff --git a/share/man/man4/iso.4 b/share/man/man4/iso.4
index 36cb8982635..70025f033da 100644
--- a/share/man/man4/iso.4
+++ b/share/man/man4/iso.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: iso.4,v 1.9 2001/10/05 14:45:53 mpech Exp $
+.\"	$OpenBSD: iso.4,v 1.10 2003/03/20 07:26:33 jmc Exp $
 .\"	$NetBSD: iso.4,v 1.3 1994/11/30 16:22:20 jtc Exp $
 .\"
 .\" Copyright (c) 1990, 1991, 1993
@@ -77,7 +77,9 @@ by providing direct access (for debugging) to the
 addresses are based upon
 .Tn ISO
 8348/AD2,
-.%T "Addendum to the Network Service Definition Covering Network Layer Addressing."
+.Rs
+.%T "Addendum to the Network Service Definition Covering Network Layer Addressing"
+.Re
 .Pp
 Sockets bound to the OSI protocol family use
 the following address structure:
@@ -102,23 +104,23 @@ struct sockaddr_iso {
 .Pp
 The fields of this structure are:
 .Bl -tag -width Ds
-.It Ar siso_len:
+.It Ar siso_len :
 Length of the entire address structure, in bytes, which may grow to
 be longer than the 32 bytes shown above.
-.It Ar siso_family:
+.It Ar siso_family :
 Identifies the domain:
 .Dv AF_ISO .
-.It Ar siso_tlen:
+.It Ar siso_tlen :
 Length of the transport selector.
-.It Ar siso_slen:
+.It Ar siso_slen :
 Length of the session selector.
 This is not currently supported by the kernel and is provided as
 a convenience for user level programs.
-.It Ar siso_plen:
+.It Ar siso_plen :
 Length of the presentation selector.
 This is not currently supported by the kernel and is provided as
 a convenience for user level programs.
-.It Ar siso_addr:
+.It Ar siso_addr :
 The network part of the address, described below.
 .El
 .Sh TRANSPORT ADDRESSING
diff --git a/share/man/man4/ksyms.4 b/share/man/man4/ksyms.4
index a7a5881a411..3c6f5ca6978 100644
--- a/share/man/man4/ksyms.4
+++ b/share/man/man4/ksyms.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ksyms.4,v 1.7 2002/01/31 21:13:08 pvalchev Exp $
+.\" $OpenBSD: ksyms.4,v 1.8 2003/03/20 07:26:33 jmc Exp $
 .\"
 .\" Copyright (c) 1998 Todd C. Miller <Todd.Miller@courtesan.com>
 .\" All rights reserved.
@@ -35,18 +35,18 @@
 .Sy pseudo-device Nm ksyms 1
 .Sh DESCRIPTION
 The
-.Nm /dev/ksyms
+.Pa /dev/ksyms
 device masquerades as an
 .Em a.out
 executable with the symbols from the running kernel as its
 symbol segment.
 Use of
-.Nm /dev/ksyms
+.Pa /dev/ksyms
 requires that the boot loader preserve the kernel symbols and place
 them at the end of the kernel's address space.
 .Pp
 The
-.Nm /dev/ksyms
+.Pa /dev/ksyms
 device is used to look up the symbol table name list from the running
 kernel.
 Because it represents the running kernel it is guaranteed
@@ -61,7 +61,7 @@ routines (note that
 and
 .Xr kvm_openfiles 3
 will try
-.Nm /dev/ksyms
+.Pa /dev/ksyms
 automatically if the first parameter to them is the
 .Dv NULL
 pointer).
@@ -71,7 +71,7 @@ pointer).
 .El
 .Sh ERRORS
 An open of
-.Nm /dev/ksyms
+.Pa /dev/ksyms
 will fail if:
 .Bl -tag -width Er
 .It Bq Er EPERM
@@ -86,13 +86,13 @@ they were removed with
 .Xr nlist 3
 .Sh HISTORY
 The
-.Nm /dev/ksyms
+.Pa /dev/ksyms
 device appeared in
 .Ox 2.4 .
 .Sh BUGS
 It is not possible to
 .Xr mmap 2
-.Nm /dev/ksyms
+.Pa /dev/ksyms
 because the boot loader does not load the symbol table onto a page
 boundary (so it is not page aligned).
 If all the boot loaders were fixed,
diff --git a/share/man/man4/lmc.4 b/share/man/man4/lmc.4
index b73e4197551..e120684a2ec 100644
--- a/share/man/man4/lmc.4
+++ b/share/man/man4/lmc.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: lmc.4,v 1.16 2003/03/06 04:03:40 david Exp $
+.\" $OpenBSD: lmc.4,v 1.17 2003/03/20 07:26:33 jmc Exp $
 .\"
 .\" Copyright (c) 1999 Chris Cappuccio
 .\"
@@ -58,7 +58,9 @@ The ability to set cable length is not currently implemented.
 Using the
 .Xr sppp 4
 driver, you can also use the ppp protocol.
-In either case, the lmc interface should be configured as a point-to-point
+In either case, the
+.Nm
+interface should be configured as a point-to-point
 link.
 .Sh DIAGNOSTICS
 .Bl -diag
@@ -67,25 +69,25 @@ A fatal initialization error has occurred.
 .It "lmc%d: couldn't establish interrupt"
 A fatal initialization error has occurred.
 .It "lmc%d: enabling keepalive"
-Cisco HDLC keepalive packets will be transmitted
+Cisco HDLC keepalive packets will be transmitted.
 .It "lmc%d: disabling keepalive"
-Cisco HDLC keepalive packets will not be transmitted
+Cisco HDLC keepalive packets will not be transmitted.
 .It "lmc%d: clock internal"
-The card is using internal clocking for the line
+The card is using internal clocking for the line.
 .It "lmc%d: clock external"
-The card is using external clocking for the line
+The card is using external clocking for the line.
 .It "lmc%d: asserting DTR and RTS"
-The card is sending DTR and RTS signals on the line
+The card is sending DTR and RTS signals on the line.
 .It "lmc%d: deasserting DTR and RTS"
-The card is not sending DTR and RTS signals on the line
+The card is not sending DTR and RTS signals on the line.
 .It "lmc%d: Abnormal interrupt"
 The card received an incomplete request.
 This may be a sign of a hardware fault.
 .It "lmc%d: tx_intr: failed to dequeue mbuf?!?"
-Only available if compiled with LMC_DEBUG
+Only available if compiled with LMC_DEBUG.
 .It "lmc%d: txput: tx not running"
-Problem from tulip,
-Only available if compiled with LMC_DEBUG
+Problem from tulip.
+Only available if compiled with LMC_DEBUG.
 .El
 .Sh SEE ALSO
 .Xr netintro 4 ,
diff --git a/share/man/man4/mtio.4 b/share/man/man4/mtio.4
index 8fa69ae53d2..e9689798241 100644
--- a/share/man/man4/mtio.4
+++ b/share/man/man4/mtio.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: mtio.4,v 1.10 2002/09/26 07:52:09 miod Exp $
+.\"	$OpenBSD: mtio.4,v 1.11 2003/03/20 07:26:33 jmc Exp $
 .\"	$NetBSD: mtio.4,v 1.4 1996/03/03 17:13:54 thorpej Exp $
 .\"
 .\" Copyright (c) 1983, 1991 The Regents of the University of California.
@@ -85,7 +85,7 @@ Two end-of-file markers mark the end of a tape, and
 one end-of-file marker marks the end of a tape file.
 If the tape is not to be rewound it is positioned with the
 head in between the two tape marks, where the next write
-will over write the second end-of-file marker.
+will overwrite the second end-of-file marker.
 .Pp
 All of the magtape devices may be manipulated with the
 .Xr mt 1