mdoc(7) fixes.

4 files changed, 63 insertions, 36 deletions

diff --git a/share/man/man4/man4.i386/arl.4 b/share/man/man4/man4.i386/arl.4
index 4a3f3ad..4f2a2ee 100644
--- a/share/man/man4/man4.i386/arl.4
+++ b/share/man/man4/man4.i386/arl.4
@@ -30,7 +30,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd August 26, 2003 
+.Dd August 26, 2003
 .Dt ARL 4 i386
 .Os
 .Sh NAME
@@ -41,18 +41,18 @@
 .Sh DESCRIPTION
 The
 .Nm
-driver provides support for Aironet Arlan 655 
+driver provides support for Aironet Arlan 655
 wireless network adapters.
 The Arlan 655 series adapters operate at 354kbps, 512kbps, 1Mbps and 2Mbps.
 .Pp
-The Aironet Arlan 655 devices support Aironet TMA, Aironet Non-TMA 
+The Aironet Arlan 655 devices support Aironet TMA, Aironet Non-TMA
 and PSP operating modes.
 .Pp
 By default, the
 .Nm
 driver configures the Aironet Arlan 655 card for TMA operation.
 .Pp
-To set up Radio Network parameters, use 
+To set up Radio Network parameters, use
 .Xr arlcontrol 8 .
 .Sh SEE ALSO
 .Xr arp 4 ,
@@ -63,22 +63,22 @@ To set up Radio Network parameters, use
 When using
 .Xr ifconfig 8
 for setting
-.Ar SSID
+.Va SSID
 you must use a 4-byte even hexadecimal digit value and it must start with
 00 or 02.
 .Pp
 You can change
-.Ar channel
-for current 
-.Ar country
+.Va channel
+for current
+.Va country
 only through
-.Xr ifconfig 8 . 
+.Xr ifconfig 8 .
 You must use
-.Xr arlcontrol 8 
+.Xr arlcontrol 8
 for changing
-.Ar country .
+.Va country .
 .Pp
-Can't change lladdr.
+Cannot change link-level address.
 .Sh HISTORY
 The
 .Nm
@@ -90,10 +90,14 @@ The
 .Nm
 driver was initially written by
 .An Ivan Sharov Aq ivan.sharov@iname.com .
-.Aq ran@styx.aic.net 
-wrote the arlcontrol utility and added ioctl support to the driver.
+.Aq ran@styx.aic.net
+wrote the
+.Xr arlcontrol 8
+utility and added
+.Xr ioctl 2
+support to the driver.
 .An Stanislav Svirid Aq count@riss-telecom.ru
-ported this driver to the new ISA architecture, merged some al driver changes, 
+ported this driver to the new ISA architecture, merged some al driver changes,
 fixed some bugs and made it a module.
 .An Yuri Kurenkov Aq y.kurenkov@init.ru
 wrote this manpage.
diff --git a/share/man/man4/man4.i386/cp.4 b/share/man/man4/man4.i386/cp.4
index 17feb11..1f450db 100644
--- a/share/man/man4/man4.i386/cp.4
+++ b/share/man/man4/man4.i386/cp.4
@@ -14,7 +14,7 @@
 .\" $FreeBSD$
 .\"
 .Dd June 21, 2004
-.Dt CP 4 PCI
+.Dt CP 4 i386
 .Os
 .Sh NAME
 .Nm cp
@@ -26,7 +26,6 @@ Additional options:
 .Cd "device sppp"
 .Cd "options NETGRAPH"
 .Cd "options NETGRAPH_CRONYX"
-.Pp
 .Sh DESCRIPTION
 The
 .Nm
@@ -49,7 +48,8 @@ support.
 The
 .Nm
 driver supports the following models of Tau-PCI WAN adapters:
-.Bl -tag -width 20n
+.Pp
+.Bl -tag -width 20n -compact
 .It Cronyx Tau-PCI
 V.35 and RS-232 interfaces
 .It Cronyx Tau-PCI/R
diff --git a/share/man/man4/man4.i386/ct.4 b/share/man/man4/man4.i386/ct.4
index c31877c..692fa97 100644
--- a/share/man/man4/man4.i386/ct.4
+++ b/share/man/man4/man4.i386/ct.4
@@ -25,7 +25,7 @@
 .\" $FreeBSD$
 .\"
 .Dd November 18, 2003
-.Dt CT 4
+.Dt CT 4 i386
 .Os
 .Sh NAME
 .Nm ct
@@ -63,8 +63,7 @@ For adapters with SMIT transfer mode to enable SMIT transfer:
 .Cd hint.ct.0.flags="0x40000"
 .Cd hint.ct.0.maddr="0xdc000"
 .Pp
-.Ar Flag
-meaning:
+Flags meaning:
 .Bl -tag -offset indent -compact -width 0x000000
 .It 0x00000
 DMA transfer mode for an NEC PC-9801-55, -92 (or
@@ -83,6 +82,7 @@ SMIT transfer mode (for supported adapters only)
 .It 0x50000
 bus-master transfer mode for a Logitec LHA-20x series,
 ICM IF-2766, IF-2766ET, IF-2767 or IF-2769
+.El
 .Sh DESCRIPTION
 The
 .Nm
@@ -123,18 +123,26 @@ host adapters.
 .Xr scsi 4
 .Sh NOTES
 Historically, the driver for the Cronyx Tau WAN adapters was
-ct.
-This device name was changed to ctau to avoid conflicts
-with this pc98 ct driver.
-The network device name for ctau
-is 'ct'.
+.Dq ct .
+This device name was changed to
+.Dq ctau
+to avoid conflicts
+with this pc98
+.Nm
+driver.
+The network device name for
+.Xr ctau 4
+is
+.Dq Li ct .
 Please see
 .Xr ctau 4
 for the details for that device.
 .Sh HISTORY
 The
 .Nm
-device driver has been developed for NetBSD/pc98 and ported for
+device driver has been developed for
+.Nx Ns /pc98
+and ported for
 .Fx .
 It first appeared in
 .Fx 4.4 .
diff --git a/share/man/man4/man4.i386/ndis.4 b/share/man/man4/man4.i386/ndis.4
index 93d1601..75d0b18 100644
--- a/share/man/man4/man4.i386/ndis.4
+++ b/share/man/man4/man4.i386/ndis.4
@@ -43,26 +43,35 @@
 .Sh DESCRIPTION
 The
 .Nm
-driver is a wrapper designed to allow binary Windows(r) NDIS miniport
+driver is a wrapper designed to allow binary
+.Tn Windows\[rg]
+NDIS miniport
 network drivers to be used with
 .Fx .
 The
 .Nm
 driver is provided in source code form and must be combined with
-the Windows(r) driver supplied with your network adapter.
+the
+.Tn Windows\[rg]
+driver supplied with your network adapter.
 The
 .Nm
 driver uses the
 .Xr ndisapi 9
-kernel subsystem to relocate and link the Windows(r) binary so
+kernel subsystem to relocate and link the
+.Tn Windows\[rg]
+binary so
 that it can be used in conjunction with native code.
 The
 .Xr ndisapi 9
 subsystem provides an interface between the NDIS API and the
 .Fx
 networking infrastructure.
-The Windows(r) driver is essentially
-fooled into thinking it's running on Windows(r).
+The
+.Tn Windows\[rg]
+driver is essentially
+fooled into thinking it is running on
+.Tn Windows\[rg] .
 Note that this
 means the
 .Nm
@@ -71,8 +80,12 @@ driver is only useful on x86 machines.
 To build a functional driver, the user must have a copy of the
 driver distribution media for his or her card.
 From this distribution,
-the user must extract two files: the .SYS file containing the driver
-binary code, and its companion .INF file, which contains the
+the user must extract two files: the
+.Pa .SYS
+file containing the driver
+binary code, and its companion
+.Pa .INF
+file, which contains the
 definitions for driver-specific registry keys and other installation
 data such as device identifiers.
 These two files can be converted
@@ -86,8 +99,10 @@ registry key data.
 When the
 .Nm
 driver loads, it will create
-.Xr sysctl 9
-nodes for each registry key extracted from the .INF file.
+.Xr sysctl 3
+nodes for each registry key extracted from the
+.Pa .INF
+file.
 .Pp
 The
 .Nm