Assorted markup, spelling, and grammar fixes.

26 files changed, 177 insertions, 143 deletions

diff --git a/share/man/man4/acpi.4 b/share/man/man4/acpi.4
index 003eb57..575a975 100644
--- a/share/man/man4/acpi.4
+++ b/share/man/man4/acpi.4
@@ -250,7 +250,7 @@ except that the
 ACPI namespace will still be scanned.
 .It Li button
 .Pq Vt device
-Supports ACPI button devices (typically power and sleep buttons.)
+Supports ACPI button devices (typically power and sleep buttons).
 .It Li cmbat
 .Pq Vt device
 Control-method batteries device.
@@ -271,7 +271,7 @@ Supports an ACPI laptop lid switch, which typically puts a
 system to sleep.
 .It Li quirks
 .Pq Vt feature
-Don't honor quirks.
+Do not honor quirks.
 Quirks automatically disable ACPI functionality based on the XSDT table's
 OEM vendor name and revision date.
 .It Li pci
@@ -374,7 +374,7 @@ must be set to 1.
 .It Va hw.acpi.cpu.cx_supported
 List of supported CPU idle states and their transition latency
 in microseconds.
-Each state has a type (e.g., C2.)
+Each state has a type (e.g., C2).
 C1 is equivalent to the ia32 HLT instruction, C2 provides a deeper
 sleep with the same semantics, and C3 provides the deepest sleep
 but additionally requires bus mastering to be disabled.
diff --git a/share/man/man4/aha.4 b/share/man/man4/aha.4
index 0371e1f..d44c75d 100644
--- a/share/man/man4/aha.4
+++ b/share/man/man4/aha.4
@@ -57,7 +57,7 @@ driver.
 .Pp
 One device hint entry for every card to be attached by the system is
 required.
-Specific values for the port address, irq, and drq may be specified.
+Specific values for the port address, IRQ, and DRQ may be specified.
 If wildcard values are used, the driver will query the device for its
 current settings and use those.
 If the port address
@@ -67,7 +67,7 @@ The possible
 port addresses for this card are 0x330, 0x334, 0x230, 0x234, 0x130, and
 0x134.
 .Pp
-The AHA-1640 is a MCA bus card.
+The AHA-1640 is an MCA bus card.
 Since the MCA bus is a self-identifying bus, no setting of hints is
 required.
 .Sh BUGS
@@ -81,7 +81,7 @@ The AHA-154xCP is a plug and play controller.
 However, its resources are set using the on-board BIOS and cannot be
 moved.
 Failures to attached for this card are often caused when the resources
-set in the BIOS conflict
+set in the BIOS conflict.
 .Sh SEE ALSO
 .Xr ahb 4 ,
 .Xr ahc 4 ,
diff --git a/share/man/man4/ata.4 b/share/man/man4/ata.4
index 281e998..c714511 100644
--- a/share/man/man4/ata.4
+++ b/share/man/man4/ata.4
@@ -97,7 +97,7 @@ The
 .Nm
 driver provides access to ATA (IDE) and SerialATA disk drives,
 ATAPI CDROM/DVD drives, ZIP/LS120 ATAPI drives and ATAPI tape drives
-connected to controllers according to the ATA/ATAPI standards. 
+connected to controllers according to the ATA/ATAPI standards.
 .Pp
 The currently supported ATA/SATA controller chips are:
 .Pp
@@ -134,7 +134,7 @@ SIS5513, SIS530, SIS540, SIS550, SIS620, SIS630, SIS630S, SIS633, SIS635, SIS730
 VT82C586, VT82C586B, VT82C596, VT82C596B, VT82C686, VT82C686A, VT82C686B, VT8231, VT8233, VT8233A, VT8233C, VT8235, VT8237.
 .El
 .Pp
-Unknown ATA chipsets are supported in PIO modes, and if the standard 
+Unknown ATA chipsets are supported in PIO modes, and if the standard
 busmaster DMA registers are present and contain valid setup, DMA is
 also enabled, although the max mode is limitted to UDMA33, as it is
 not known what the chipset can do and how to program it.
@@ -147,7 +147,7 @@ See
 .Xr atacontrol 8 .
 .Pp
 The
-.nm
+.Nm
 driver sets the maximum transfer mode supported by the hardware as default.
 However the
 .Nm
@@ -158,7 +158,7 @@ the
 .Nm
 driver has detected that the required 80 conductor cable is not present
 or could not be detected properly,
-or that one of the devices on the channel only accepts up 
+or that one of the devices on the channel only accepts up
 to UDMA2/ATA33.
 .Pp
 ATAPI devices are set to PIO mode by default because severe DMA problems are
@@ -205,7 +205,6 @@ even when not present.
 This is useful in hotswap senarios
 where disks should always show up as the same numbered device,
 and not depend on attach order.
-.Pp
 .Sh SEE ALSO
 .Xr atacontrol 8 ,
 .Xr burncd 8
diff --git a/share/man/man4/awi.4 b/share/man/man4/awi.4
index 1dd2fb8..3e5036b 100644
--- a/share/man/man4/awi.4
+++ b/share/man/man4/awi.4
@@ -113,8 +113,8 @@ The device failed to complete the request from the system.
 .El
 .Sh SEE ALSO
 .Xr arp 4 ,
-.Xr cnw 4 ,
 .Xr card 4 ,
+.Xr cnw 4 ,
 .Xr miibus 4 ,
 .Xr netintro 4 ,
 .Xr pccard 4 ,
diff --git a/share/man/man4/bpf.4 b/share/man/man4/bpf.4
index 2bb89c5..b9a3d33 100644
--- a/share/man/man4/bpf.4
+++ b/share/man/man4/bpf.4
@@ -711,7 +711,7 @@ struct bpf_insn insns[] = {
 .Xr ioctl 2 ,
 .Xr byteorder 3 ,
 .Xr ng_bpf 4 ,
-.Xr bpf 9 .
+.Xr bpf 9
 .Rs
 .%A McCanne, S.
 .%A Jacobson V.
diff --git a/share/man/man4/bridge.4 b/share/man/man4/bridge.4
index 37b8e1b..1098f2e 100644
--- a/share/man/man4/bridge.4
+++ b/share/man/man4/bridge.4
@@ -121,7 +121,9 @@ section for more examples.
 The list of interfaces is rescanned every time the list is
 modified, bridging is enabled, or new interfaces are created or
 destroyed.
-An explicit request to refresh the bridge configuration can also
+An explicit request to refresh the
+.Nm
+configuration can also
 be done by writing any value to
 .Va net.link.ether.bridge.refresh .
 Interfaces that are in the list but cannot be used
@@ -139,7 +141,9 @@ Also, bridging is not compatible with interfaces which
 use hardware loopback, because there is no way to tell locally
 generated packets from externally generated ones.
 .Sh EXAMPLES
-A simple bridge configuration with three interfaces in the same
+A simple
+.Nm
+configuration with three interfaces in the same
 cluster can be set as follows.
 No cluster-ID is specified here, which
 will cause the interfaces to appear as part of cluster #1.
diff --git a/share/man/man4/ddb.4 b/share/man/man4/ddb.4
index 1e2c6ac..58ed5c7 100644
--- a/share/man/man4/ddb.4
+++ b/share/man/man4/ddb.4
@@ -132,7 +132,7 @@ variable, it displays
 and waits for a response.
 The valid responses for it are:
 .Pp
-.Bl -tag -compact -width SPC
+.Bl -tag -compact -width ".Li SPC"
 .It Li SPC
 one more page
 .It Li RET
@@ -196,19 +196,19 @@ display as an instruction
 .It Li I
 display as an instruction with possible alternate formats depending on the
 machine:
-.Bl -tag -width powerpc -compact
+.Bl -tag -width ".Tn powerpc" -compact
 .It Tn alpha
 Show the registers of the instruction.
 .It Tn amd64
-No alternate format
+No alternate format.
 .It Tn i386
-No alternate format
+No alternate format.
 .It Tn ia64
-No alternate format
+No alternate format.
 .It Tn powerpc
-No alternate format
+No alternate format.
 .It Tn sparc64
-No alternate format
+No alternate format.
 .El
 .El
 .It Cm xf
@@ -513,7 +513,7 @@ modifier to indicate user register (e.g.,
 .Li $eax:u ) .
 .Pp
 Built-in variables currently supported are:
-.Bl -tag -width tabstops -compact
+.Bl -tag -width ".Li tabstops" -compact
 .It Li radix
 Input and output radix
 .It Li maxoff
@@ -541,7 +541,7 @@ and unary
 Special rules in
 .Nm
 are:
-.Bl -tag -width Identifiers
+.Bl -tag -width ".Em Identifiers"
 .It Em Identifiers
 The name of a symbol is translated to the value of the symbol, which
 is the address of the corresponding object.
diff --git a/share/man/man4/gre.4 b/share/man/man4/gre.4
index e8c903b..d45b903 100644
--- a/share/man/man4/gre.4
+++ b/share/man/man4/gre.4
@@ -75,7 +75,7 @@ GRE mode is also the default tunnel mode on Cisco routers.
 This is also the default mode of operation of the
 .Nm
 interfaces.
-As part of the GRE mode
+As part of the GRE mode,
 .Nm
 also supports Cisco WCCP protocol, both version 1 and version 2.
 Since there is no reliable way to distinguish between WCCP versions, it
diff --git a/share/man/man4/inet.4 b/share/man/man4/inet.4
index cff0783..b922bf9 100644
--- a/share/man/man4/inet.4
+++ b/share/man/man4/inet.4
@@ -58,12 +58,12 @@ interface provides access to the
 protocol.
 .Sh ADDRESSING
 Internet addresses are four byte quantities, stored in
-network standard format (on little endian machines, such as the 
+network standard format (on little endian machines, such as the
 .Tn alpha ,
 .Tn amd64 ,
-.Tn i386 
+.Tn i386
 and
-.Tn ia64 
+.Tn ia64
 these are word and byte reversed).
 The include file
 .In netinet/in.h
diff --git a/share/man/man4/ip.4 b/share/man/man4/ip.4
index 575725f..1c17866 100644
--- a/share/man/man4/ip.4
+++ b/share/man/man4/ip.4
@@ -326,9 +326,9 @@ consequences that the administrator should carefully evaluate before
 modifying these settings.
 .Pp
 Ports are allocated at random within the specified port range in order
-to increase the difficulty of random spoofing attacks.  In scenarios
-such as benchmarking, this behavior may be undesireable.  In these
-cases,
+to increase the difficulty of random spoofing attacks.
+In scenarios such as benchmarking, this behavior may be undesireable.
+In these cases,
 .Va net.inet.ip.portrange.randomized
 can be used to toggle randomization off.
 .Ss "Multicast Options"
@@ -431,7 +431,7 @@ struct ip_mreq {
 }
 .Ed
 .Pp
-.Dv imr_interface
+.Va imr_interface
 should be set to
 .Dv INADDR_ANY
 to choose the default multicast interface,
@@ -442,7 +442,7 @@ the host is multihomed.
 Since
 .Fx 4.4 ,
 if the
-.Dv imr_interface
+.Va imr_interface
 member is within the network range
 .Li 0.0.0.0/8 ,
 it is treated as an interface index in the system interface MIB,
diff --git a/share/man/man4/kame.4 b/share/man/man4/kame.4
index a0284f4..a9d57c3 100644
--- a/share/man/man4/kame.4
+++ b/share/man/man4/kame.4
@@ -80,8 +80,8 @@ See below for conformance to standards and/or internet drafts.
 .Xr mchat 1
 .Pq - ,
 .Xr ifmcstat 8 ,
-.Xr pim6dd 8 [ /usr/ports/net/pim6dd ] ,
-.Xr pim6sd 8 [ /usr/ports/net/pim6sd ] ,
+.Xr pim6dd 8 Pq Pa ports/net/pim6dd ,
+.Xr pim6sd 8 Pq Pa ports/net/pim6sd ,
 .Xr pim6stat 8 .
 .\"
 .Ss Transition Tools
@@ -96,7 +96,7 @@ is not yet integrated into
 .\"
 .Ss IPsec and tunnelling
 .Xr ipsec 4 ,
-.Xr racoon 8 [ /usr/ports/security/racoon ] ,
+.Xr racoon 8 Pq Pa ports/security/racoon ,
 .Xr setkey 8 .
 .Pp
 Dozen of existing tools are modified for IPsec support, like
diff --git a/share/man/man4/kue.4 b/share/man/man4/kue.4
index ec34399..c9d09e8 100644
--- a/share/man/man4/kue.4
+++ b/share/man/man4/kue.4
@@ -47,7 +47,7 @@ The
 driver provides support for USB ethernet adapters based on the Kawasaki
 LSI KL5KLUSB101B chipset, including the following:
 .Pp
-.Bl -bullet
+.Bl -bullet -compact
 .It
 3Com 3c19250
 .It
diff --git a/share/man/man4/mac_portacl.4 b/share/man/man4/mac_portacl.4
index 4abb0cf..250eb2d 100644
--- a/share/man/man4/mac_portacl.4
+++ b/share/man/man4/mac_portacl.4
@@ -96,12 +96,12 @@ these are automatically selected by the IP stack.
 .Pp
 When
 .Nm
-is enabled it will control binding access to ports up to the port
+is enabled, it will control binding access to ports up to the port
 number set in the
 .Va security.mac.portacl.port_high
 .Xr sysctl 8
 variable.
-By default all attempts to bind to
+By default, all attempts to bind to
 .Nm
 controlled ports will fail if not explicitly allowed by the port
 access control list, though binding by the superuser will be allowed,
@@ -198,7 +198,7 @@ entry will not function
 port).
 .El
 .It Va security.mac.portacl.suser_exempt
-Allow superuser (i.e. root) to bind to all
+Allow superuser (i.e., root) to bind to all
 .Nm
 protected ports, even if the port access control list does not
 explicitly allow this.
diff --git a/share/man/man4/man4.i386/cx.4 b/share/man/man4/man4.i386/cx.4
index 6cf1474..c880990 100644
--- a/share/man/man4/man4.i386/cx.4
+++ b/share/man/man4/man4.i386/cx.4
@@ -38,9 +38,11 @@ The
 .Nm
 driver needs either
 .Xr sppp 4
-or 
+or
 .Xr netgraph 4 .
-Which one to use is determined by the NETGRAPH_CRONYX option.
+Which one to use is determined by the
+.Dv NETGRAPH_CRONYX
+option.
 If this option is present in your kernel configuration file, the
 .Nm
 driver will be compiled with
@@ -80,9 +82,9 @@ for information about the
 .Nm
 adapter configuration.
 .Sh SEE ALSO
-.Xr sppp 4 , 
-.Xr ifconfig 8 , 
-.Xr sconfig 8 , 
+.Xr sppp 4 ,
+.Xr ifconfig 8 ,
+.Xr sconfig 8 ,
 .Xr spppcontrol 8
 .Sh HISTORY
 The
diff --git a/share/man/man4/mpt.4 b/share/man/man4/mpt.4
index 0ee6fd2..2e5cb57 100644
--- a/share/man/man4/mpt.4
+++ b/share/man/man4/mpt.4
@@ -34,7 +34,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd 07 November, 2003
+.Dd November 7, 2003
 .Dt MPT 4
 .Os
 .Sh NAME
diff --git a/share/man/man4/ng_one2many.4 b/share/man/man4/ng_one2many.4
index b340441..2bdcd56 100644
--- a/share/man/man4/ng_one2many.4
+++ b/share/man/man4/ng_one2many.4
@@ -76,12 +76,12 @@ Before an interface or link can be plumbed into a group, its status
 must be marked as being
 .Dq up .
 This is normally setup during the initial boot stages by
-.Xr rc.conf 5 . 
-It is also possible to change an interfaces status to
-.Dq up 
+.Xr rc.conf 5 .
+It is also possible to change an interface's status to
+.Dq up
 by using the
 .Xr ifconfig 8
-utility. 
+utility.
 .Sh TRANSMIT ALGORITHMS
 .Bl -tag -width foo
 .It NG_ONE2MANY_XMIT_ROUNDROBIN
@@ -125,7 +125,7 @@ following:
 Sets the node configuration using a
 .Dv "struct ng_one2many_link_config"
 as the control message argument:
-.Bd -literal -offset 0n
+.Bd -literal
 /* Node configuration structure */
 struct ng_one2many_config {
   u_int32_t   xmitAlg;        /* how to distribute packets */
@@ -155,7 +155,7 @@ returns a
 containing statistics for the corresponding
 .Dv many
 link, which may or may not be currently connected:
-.Bd -literal -offset 0n
+.Bd -literal
 /* Statistics structure (one for each link) */
 struct ng_one2many_link_stats {
   u_int64_t   recvOctets;     /* total octets rec'd on link */
@@ -189,7 +189,7 @@ corresponding to networking interfaces
 .Dv fxp0
 through
 .Dv fxp3 :
-.Bd -literal -offset 0n
+.Bd -literal
   # Plumb nodes together
 
   ngctl mkpeer fxp0: one2many upper one
diff --git a/share/man/man4/ng_rfc1490.4 b/share/man/man4/ng_rfc1490.4
index 52a7099..bcba26d 100644
--- a/share/man/man4/ng_rfc1490.4
+++ b/share/man/man4/ng_rfc1490.4
@@ -53,16 +53,18 @@ DLCI channels.
 .Pp
 The
 .Dv downstream
-hook is used to transmit and receive encapsulated frames. On the other
-side of the node, the
+hook is used to transmit and receive encapsulated frames.
+On the other side of the node, the
 .Dv inet
 and
 .Dv ppp
 hooks are used to transmit and receive raw IP frames and PPP frames,
-respectively. PPP frames are transmitted and received according to
+respectively.
+PPP frames are transmitted and received according to
 RFC 1973; in particular, frames appearing on the
 .Dv ppp
-hook begin with the PPP protocol number. The
+hook begin with the PPP protocol number.
+The
 .Dv ethernet
 hook can be used to transmit and receive Ethernet frames (without a
 checksum) in RFC 1490's bridging format.
@@ -89,18 +91,18 @@ Transmits and receives PPP frames.
 .El
 .Sh CONTROL MESSAGES
 This node type supports the generic control messages, plus the following:
-.Bl -tag -width foo
+.Bl -tag -width indent
 .It Dv NGM_RFC1490_SETENCAP
 This command sets encapsulation method for the node.
 The desired method must be passed as a string message argument,
 and must be one of the following supported encapsulation modes:
-.Bl -tag
-.It Qq ietf-ip
+.Bl -tag -width ".Qq Li ietf-snap"
+.It Qq Li ietf-ip
 IP packets are sent using simple RFC1490/2427 encapsulation.
-.It Qq ietf-snap
+.It Qq Li ietf-snap
 IP packets are sent inside SNAP frames.
 Also conforms to RFC1490/2427.
-.It Qq cisco
+.It Qq Li cisco
 IP packets are sent and received using proprietary Cisco encapsulation
 method.
 .El
@@ -129,9 +131,8 @@ Not all of RFC 1490 is implemented.
 .%T "PPP in Frame Relay"
 .%O RFC 1973
 .Re
-.Rs
-http://www.cisco.com/warp/public/121/frf8modes.pdf
-.Re
+.Pp
+.Pa http://www.cisco.com/warp/public/121/frf8modes.pdf
 .Sh HISTORY
 The
 .Nm
diff --git a/share/man/man4/pcm.4 b/share/man/man4/pcm.4
index 3179aca..718d8c4 100644
--- a/share/man/man4/pcm.4
+++ b/share/man/man4/pcm.4
@@ -31,7 +31,9 @@
 .Sh NAME
 .Nm pcm ,
 .Nm snd
-.Nd FreeBSD PCM audio device infrastructure
+.Nd
+.Fx
+PCM audio device infrastructure
 .Sh SYNOPSIS
 For a card with bridge driver support, and a PnP card:
 .Cd "device pcm"
@@ -106,33 +108,37 @@ in
 .Ss Boot Variables
 In general, the module
 .Pa snd_foo
-corresponds to device foo and can be
-loaded by the boot loader via
-.Pa boot/loader.conf
+corresponds to
+.Cd "device foo"
+and can be
+loaded by the boot
+.Xr loader 8
+via
+.Xr loader.conf 5
 or from the command line using the
 .Xr kldload 8
 utility.
 Options which can be specified in
 .Pa /boot/loader.conf
 include:
-.Bl -tag -width snd_emu10k1_load -offset indent
+.Bl -tag -width ".Va snd_emu10k1_load" -offset indent
 .It Va snd_driver_load
-.Pq Dq NO
+.Pq Dq Li NO
 If set to
-.Dq YES ,
+.Dq Li YES ,
 this option loads all available drivers.
 .It Va snd_emu10k1_load
-.Pq Dq NO
+.Pq Dq Li NO
 If set to
-.Dq YES ,
-Only the SoundBlaster 5.1 driver and dependent modules will be loaded.
+.Dq Li YES ,
+only the SoundBlaster 5.1 driver and dependent modules will be loaded.
 .It Va snd_foo_load
-.Pq Dq NO
+.Pq Dq Li NO
 If set to
-.Dq YES ,
+.Dq Li YES ,
 load driver for card/chipset foo.
 .El
-.Ss VCHANS
+.Ss VCHANs
 Each device can optionally support more playback channels
 that physical hardware provides by using
 .Dq virtual channels
@@ -145,8 +151,8 @@ interface but can only be manipulated while the device is inactive.
 .Ss Runtime Configuration
 The following
 .Xr sysctl 8
-tunables are available:
-.Bl -tag -width ".It Va hw.snd.report_soft_formats" -offset indent
+variables are available:
+.Bl -tag -width ".Va hw.snd.report_soft_formats" -offset indent
 .It Va hw.snd.pcm%d.buffersize
 Configure the amount of
 .Tn DMA
@@ -167,7 +173,7 @@ the default device for
 Equivalent to a symlink from
 .Pa /dev/dsp
 to
-.Pa /dev/dsp${hw.snd.unit} .
+.Pa /dev/dsp Ns Va ${hw.snd.unit} .
 .It Va hw.snd.report_soft_formats
 Controls the internal format conversion if it is
 available transparently to the application software.
@@ -178,15 +184,21 @@ Level of verbosity for the
 .Pa /dev/sndstat
 device.
 Higher values include more output and the highest level,
-three, should be used when reported problems.
+three, should be used when reporting problems.
 Other options include:
-0 - Installed devices and their allocated bus resources.
-1 - The number of playback, record, virtual channels, and
+.Bl -tag -width 2n
+.It 0
+Installed devices and their allocated bus resources.
+.It 1
+The number of playback, record, virtual channels, and
 flags per device.
-2 - Channel information per device including the channel's
+.It 2
+Channel information per device including the channel's
 current format, speed, and pseudo device statistics such as
 buffer overruns and buffer underruns.
-3 - File names and versions of the currently sound loaded modules.
+.It 3
+File names and versions of the currently sound loaded modules.
+.El
 .It Va hw.snd.maxautovchans
 Global
 .Tn VCHAN
@@ -225,7 +237,9 @@ The driver supports most of the
 .Fn ioctl
 functions, and most applications work unmodified.
 A few differences exist, while memory mapped playback is
-supported natively and in Linux emulation, memory mapped recording is
+supported natively and in
+.Tn Linux
+emulation, memory mapped recording is
 not due to
 .Tn VM
 system design.
@@ -236,7 +250,7 @@ See
 for a complete list of the supported
 .Fn ioctl
 functions.
-.Ss SUPPORTED CARDS
+.Ss Supported Cards
 Below we include a list of supported codecs/cards.
 If your sound card
 is not listed here, it may be supported by a bridge driver.
@@ -254,12 +268,13 @@ not wired to the ISA DMA controller.
 .It Yamaha OPL-SAx (ISA)
 Works perfectly in all modes.
 This chip is used in several PnP cards,
-but also (in non-PnP mode) on motherboards and laptops (e.g. the
+but also (in non-PnP mode) on motherboards and laptops (e.g., the
 Toshiba Libretto).
 .It OPTi931 (ISA)
 The chip is buggy, but the driver has many workarounds to make it work
 in full duplex because for some time these were the only full duplex
-cards I could find. u-law formats uses U8 format internally because of
+cards I could find.
+U-law format uses U8 format internally because of
 a bug in the chip.
 .It Trident 4DWave DX/NX (PCI)
 .It ENSONIQ AudioPCI ES1370/1371 (PCI)
@@ -273,7 +288,7 @@ The
 drivers may create the following
 device nodes:
 .Pp
-.Bl -tag -width "/dev/dspr%d.%dXXX" -compact
+.Bl -tag -width ".Pa /dev/audio%d.%d" -compact
 .It Pa /dev/audio%d.%d
 Sparc-compatible audio device.
 .It Pa /dev/dsp%d.%d
@@ -292,36 +307,39 @@ status, including all channels and drivers.
 .Pp
 The first number in the device node
 represents the unit number of the
-.Nm PCM
+.Nm
 device.
 All
 .Nm
-PCM
 devices are listed
 in
-.Pa /dev/sndstat.
+.Pa /dev/sndstat .
 Additional messages are sometimes recorded when the
 device is probed and attached, these messages can be viewed with the
 .Xr dmesg 8
 utility.
 .Sh DIAGNOSTICS
-.Bl -tag -width 2m
+.Bl -diag
 .It ac97: dac not ready
 AC97 codec is not likely to be accompanied with the sound card.
 .It unsupported subdevice XX
 A device node is not created properly.
 .El
 .Sh BUGS
-Some features of your cards (e.g. global volume control) might not
+Some features of your cards (e.g., global volume control) might not
 be supported on all devices.
 .Sh HISTORY
 The
 .Nm
 device driver first appeared in
-.Fx 2.2.6 written by Luigi Rizzo.
+.Fx 2.2.6
+written by
+.An Luigi Rizzo .
 It was later
 rewritten in
-.Fx 4.0 by Cameron Grant.
+.Fx 4.0
+by
+.An Cameron Grant .
 The API evolved from the VOXWARE
 standard which later became OSS standard.
 .Sh SEE ALSO
@@ -349,4 +367,4 @@ later revised the device driver for
 .An Seigo Tanimura Aq tanimura@r.dl.itc.u-tokyo.ac.jp
 revised this manual page.
 It was then rewritten for
-.Fx 5.2 .
\ No newline at end of file
+.Fx 5.2 .
diff --git a/share/man/man4/random.4 b/share/man/man4/random.4
index 4cd998f..f483b5b 100644
--- a/share/man/man4/random.4
+++ b/share/man/man4/random.4
@@ -32,6 +32,7 @@
 .Sh DESCRIPTION
 The
 .Nm
+device
 returns an endless supply of random bytes when read.
 It also accepts and reads data
 as any ordinary (and willing) file,
@@ -81,6 +82,7 @@ kern.random.yarrow.fastthresh: 100
 kern.random.yarrow.slowthresh: 160
 kern.random.yarrow.slowoverthresh: 2
 .Ed
+.Pp
 (These would not be seen if a
 hardware generator is present.)
 .Pp
@@ -322,7 +324,7 @@ algorithm by Bruce Schneier,
 .Em et al .
 The only hardware implementation
 currently is for the
-.Em VIA C3 Nehemiah
+.Tn VIA C3 Nehemiah
 (stepping 3 or greater)
 CPU.
 More will be added in the future.
diff --git a/share/man/man4/sbp.4 b/share/man/man4/sbp.4
index 128e36f..866a917 100644
--- a/share/man/man4/sbp.4
+++ b/share/man/man4/sbp.4
@@ -72,8 +72,8 @@ If you want to force to detach the device, run
 .Dq Nm fwcontrol Fl r
 several times.
 .Pp
-Some (broken) HDDs don't work well with tagged queuing. If you have problems
-with such drives, try
+Some (broken) HDDs do not work well with tagged queuing.
+If you have problems with such drives, try
 .Dq Nm camcontrol [device id] tags -N 1
 to disable tagged queuing.
 .Sh SEE ALSO
diff --git a/share/man/man4/smb.4 b/share/man/man4/smb.4
index 8645c03..1c6556b 100644
--- a/share/man/man4/smb.4
+++ b/share/man/man4/smb.4
@@ -40,7 +40,7 @@ character device driver provides generic i/o to any
 .Xr smbus 4
 instance.
 In order to control SMB devices, use
-.Pa /dev/smb Ns Em ?
+.Pa /dev/smb?
 with the ioctls described below.
 Any of these ioctl commands takes a pointer to
 .Vt struct smbcmd
@@ -73,40 +73,40 @@ The
 field is always used, and provides the address of the
 SMBus slave device to talk to.
 .Pp
-.Bl -column ".Sy SMB_QUICK_WRITE" -compact
+.Bl -column ".Dv SMB_QUICK_WRITE" -compact
 .It Em Ioctl Ta Em Description
 .Pp
-.It Sy SMB_QUICK_WRITE Ta
+.It Dv SMB_QUICK_WRITE Ta
 The
 .Em QuickWrite
 command just issues the device address with write intent
 to the bus, without transferring any data.
-.It Sy SMB_QUICK_READ Ta
+.It Dv SMB_QUICK_READ Ta
 The
 .Em QuickRead
 command just issues the device address with read intent
 to the bus, without transferring any data.
-.It Sy SMB_SENDB Ta
+.It Dv SMB_SENDB Ta
 The
 .Em SendByte
 command sends the byte provided in the
 .Fa cmd
 field to the device.
-.It Sy SMB_RECVB Ta
+.It Dv SMB_RECVB Ta
 The
 .Em ReceiveByte
 command reads a single byte from the device which will
 be returned in the
 .Fa cmd
 field.
-.It Sy SMB_WRITEB Ta
+.It Dv SMB_WRITEB Ta
 The
 .Em WriteByte
 command first sends the byte from the
 .Fa cmd
 field to the device, followed by the byte given in
 .Fa data.byte .
-.It Sy SMB_WRITEW Ta
+.It Dv SMB_WRITEW Ta
 The
 .Em WriteWord
 command first sends the byte from the
@@ -114,7 +114,7 @@ command first sends the byte from the
 field to the device, followed by the word given in
 .Fa data.word .
 Note that the SMBus byte-order is little-endian by definition.
-.It Sy SMB_READB Ta
+.It Dv SMB_READB Ta
 The
 .Em ReadByte
 command first sends the byte from the
@@ -123,7 +123,7 @@ field to the device, and then reads one byte of data from
 the device.
 The returned data will be stored in the location pointed to by
 .Fa data.byte_ptr .
-.It Sy SMB_READW Ta
+.It Dv SMB_READW Ta
 The
 .Em ReadWord
 command first sends the byte from the
@@ -132,7 +132,7 @@ field to the device, and then reads one word of data from
 the device.
 The returned data will be stored in the location pointed to by
 .Fa data.word_ptr .
-.It Sy SMB_PCALL Ta
+.It Dv SMB_PCALL Ta
 The
 .Em ProcedureCall
 command first sends the byte from the
@@ -142,7 +142,7 @@ field to the device, followed by the word provided in
 It then reads one word of data from the device, and returns it
 in the location pointed to by
 .Fa data.process.rdata .
-.It Sy SMB_BWRITE Ta
+.It Dv SMB_BWRITE Ta
 The
 .Em BlockWrite
 command first sends the byte from the
@@ -155,7 +155,7 @@ The SMBus specification mandates that no more than 32 bytes of
 data can be transferred in a single block read or write command.
 This value is available in the constant
 .Dv SMB_MAXBLOCKSIZE .
-.It Sy SMB_BREAD Ta
+.It Dv SMB_BREAD Ta
 The
 .Em BlockRead
 command first sends the byte from the
diff --git a/share/man/man4/smp.4 b/share/man/man4/smp.4
index c15ccdb..81a42d0 100644
--- a/share/man/man4/smp.4
+++ b/share/man/man4/smp.4
@@ -60,7 +60,7 @@ command may be used to view the status of multi-processor support.
 .Fx
 supports hyperthreading on Intel CPU's on the i386 platform.
 Since using logical CPUs can cause performance penalties under certain loads,
-the logical CPUs can be disabled by setting the 
+the logical CPUs can be disabled by setting the
 .Va machdep.hlt_logical_cpus
 sysctl to one.
 .Sh SEE ALSO
diff --git a/share/man/man4/syscons.4 b/share/man/man4/syscons.4
index a99324f..cd2000b 100644
--- a/share/man/man4/syscons.4
+++ b/share/man/man4/syscons.4
@@ -148,7 +148,7 @@ variable in
 to the desired keymap file so that it will be automatically loaded
 when the system starts up.
 .Ss Software Font
-For most modern video cards, e.g. VGA, the
+For most modern video cards, e.g., VGA, the
 .Nm
 driver and the video card driver allow the user to change
 the font used on the screen.
@@ -345,11 +345,16 @@ unless you explicitly load a software font at startup.
 See
 .Sx EXAMPLES
 below.
-.It SC_NO_SUSPEND_VTYSWITCH
-This option, which is also available as loader tunable and sysctl
-.Va ( hw.syscons.sc_no_suspend_vtswitch ) ,
+.It Dv SC_NO_SUSPEND_VTYSWITCH
+This option, which is also available as
+.Xr loader 8
+tunable and
+.Xr sysctl 8
+variable
+.Pq Va hw.syscons.sc_no_suspend_vtswitch ,
 disables switching between virtual terminals (graphics <-> text) during
-suspend/resume (ACPI and APM).  Use this option if your system is freezing
+suspend/resume (ACPI and APM).
+Use this option if your system is freezing
 when you are running X and trying to suspend.
 .El
 .Pp
diff --git a/share/man/man4/tcp.4 b/share/man/man4/tcp.4
index 51959e1..3ba5598 100644
--- a/share/man/man4/tcp.4
+++ b/share/man/man4/tcp.4
@@ -121,7 +121,7 @@ supports a number of socket options which can be set with
 .Xr setsockopt 2
 and tested with
 .Xr getsockopt 2 :
-.Bl -tag -width ".Dv TCP_MD5SIG"
+.Bl -tag -width ".Dv TCP_NODELAY"
 .It Dv TCP_NODELAY
 Under most circumstances,
 .Tn TCP
@@ -183,10 +183,14 @@ digests on incoming traffic are not verified.
 The current default behavior for the system is to respond to a system
 advertising this option with TCP-MD5; this may change.
 .Pp
-One common use for this in a FreeBSD router deployment is to enable
+One common use for this in a
+.Fx
+router deployment is to enable
 based routers to interwork with Cisco equipment at peering points.
 Support for this feature conforms to RFC 2385.
-Only IPv4 (AF_INET) sessions are supported.
+Only IPv4
+.Pq Dv AF_INET
+sessions are supported.
 .Pp
 In order for this option to function correctly, it is necessary for the
 administrator to add a tcp-md5 key entry to the system's security
diff --git a/share/man/man4/umass.4 b/share/man/man4/umass.4
index 372898d..a49ee5b 100644
--- a/share/man/man4/umass.4
+++ b/share/man/man4/umass.4
@@ -86,15 +86,15 @@ Among the supported digital cameras are:
 Asahi Optical (PENTAX) Optio 230 & 330
 .El
 .Pp
-.Nm usb
+.Xr usb 4
 and one of
-.Nm uhci
+.Xr uhci 4
 or
-.Nm ohci
+.Xr ohci 4
 must be configured in the kernel as well.
 Last but not least, support for
 SCSI drives,
-.Nm da .
+.Xr da 4 .
 .Sh EXAMPLES
 .Bd -literal -offset indent
 device umass
@@ -130,9 +130,9 @@ mount -t ufs /dev/da0c /mnt
 .Ed
 .Pp
 Write a disklabel to the Zip drive (see
-.Nm vpo
+.Xr vpo 4
 for the
-.Nm disktab
+.Xr disktab 5
 entry), creates the file system and mounts the new file system on /mnt.
 .Pp
 .Dl "newfs_msdos /dev/da0"
@@ -149,7 +149,7 @@ based file systems when storing information such as images and
 videos.
 These file systems can be accessed by specifying the file system
 type as
-.Nm msdos
+.Cm msdos
 when using
 .Xr mount 8 .
 .Sh SEE ALSO
@@ -158,8 +158,8 @@ when using
 .Xr usb 4 ,
 .Xr vpo 4 ,
 .Xr disktab 5 ,
-.Xr camcontrol 8 ,
-.Xr bsdlabel 8
+.Xr bsdlabel 8 ,
+.Xr camcontrol 8
 .\".Sh HISTORY
 .Sh AUTHORS
 .An -nosplit
diff --git a/share/man/man4/wlan.4 b/share/man/man4/wlan.4
index 035d339..e560195 100644
--- a/share/man/man4/wlan.4
+++ b/share/man/man4/wlan.4
@@ -46,24 +46,23 @@ and
 drivers but will eventually be required by all 802.11 drivers.
 .Pp
 If the associated interface is marked for debugging with, for example,
-.Bd -literal -offset indent
-ifconfig wi0 debug
-.Ed
+.Pp
+.Dl "ifconfig wi0 debug"
 .Pp
 then messages describing the operation of the 802.11 protocol will
 be sent to the console.
 With the interface marked for debugging, doing:
-.Bd -literal -offset indent
-sysctl debug.ieee80211=1
-.Ed
+.Pp
+.Dl "sysctl debug.ieee80211=1"
 .Pp
 causes additional messages to be generated.
 Many drivers will also display the contents of each 802.11 frame
 sent and received when the interface is marked with
-both debugging and ``link2''; e.g.
-.Bd -literal -offset indent
-ifconfig wi0 debug link2
-.Ed
+both debugging and
+.Cm link2 ;
+e.g.,
+.Pp
+.Dl "ifconfig wi0 debug link2"
 .Pp
 Beware however that some management frames may be processed entirely within
 the device and not be received by the host.