reduce .Nd to one line and kill .Tn while here

8 files changed, 59 insertions, 149 deletions

diff --git a/share/man/man4/man4.vax/asc.4 b/share/man/man4/man4.vax/asc.4
index 2b086e13aa2..de75a535303 100644
--- a/share/man/man4/man4.vax/asc.4
+++ b/share/man/man4/man4.vax/asc.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: asc.4,v 1.8 2012/08/14 01:08:19 dlg Exp $
+.\"	$OpenBSD: asc.4,v 1.9 2015/09/10 15:16:43 schwarze Exp $
 .\"
 .\" Copyright (c) 1996 Jonathan Stone.
 .\" Copyright (c) 2000 Matt Thomas.
@@ -31,13 +31,12 @@
 .\"
 .\"	$NetBSD: asc.4,v 1.7 2002/01/15 02:03:42 wiz Exp $
 .\"
-.Dd $Mdocdate: August 14 2012 $
+.Dd $Mdocdate: September 10 2015 $
 .Dt ASC 4 vax
 .Os
 .Sh NAME
 .Nm asc
-.Nd
-VAXstation 4000 SCSI controller
+.Nd VAXstation 4000 SCSI controller
 .Sh SYNOPSIS
 .Cd "asc* at vsbus? csr 0x200c0080" Pq VS4000/60 or VLC
 .Cd "asc* at vsbus? csr 0x25000080" Pq VS4000/9x
diff --git a/share/man/man4/man4.vax/dhu.4 b/share/man/man4/man4.vax/dhu.4
index f977886f884..f414680982c 100644
--- a/share/man/man4/man4.vax/dhu.4
+++ b/share/man/man4/man4.vax/dhu.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: dhu.4,v 1.12 2007/05/31 19:19:57 jmc Exp $
+.\"	$OpenBSD: dhu.4,v 1.13 2015/09/10 15:16:43 schwarze Exp $
 .\"	$NetBSD: dhu.4,v 1.4 1996/03/05 15:28:48 ragge Exp $
 .\"
 .\" Copyright (c) 1985, 1991 Regents of the University of California.
@@ -30,28 +30,22 @@
 .\"
 .\"     from: @(#)dhu.4	6.3 (Berkeley) 3/27/91
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: September 10 2015 $
 .Dt DHU 4 vax
 .Os
 .Sh NAME
 .Nm dhu
-.Nd
-.Tn DHU-11/DHV-11
-communications multiplexer
+.Nd DHU-11/DHV-11 communications multiplexer
 .Sh SYNOPSIS
 .Cd "dhu0 at uba0 csr 0160440"
 .Sh DESCRIPTION
-A
-.Tn DHU-11
-provides 16 communication lines.
+A DHU-11 provides 16 communication lines.
 .Pp
 Normal I/O
 control parameters for individual lines are managed by
 .Xr ioctl 2
 calls.
-Individual
-.Tn DHU-11
-lines may be configured to run at any of 13 speeds
+Individual DHU-11 lines may be configured to run at any of 13 speeds
 (50, 200 and 38400 baud are not available);
 the speed may be set via
 .Xr getty 8
@@ -65,9 +59,7 @@ such as
 see
 .Xr tty 4 .
 .Pp
-The
-.Tn DHU-11
-driver normally uses input silos
+The DHU-11 driver normally uses input silos
 and delays receiver interrupts by 20 milliseconds
 rather than taking an interrupt on each input character.
 .Sh FILES
@@ -76,19 +68,12 @@ rather than taking an interrupt on each input character.
 .El
 .Sh NOTES
 The driver currently does not make full use of the hardware
-capabilities of the
-.Tn DHU-11 ,
-for dealing with
-.Tn XON/XOFF
+capabilities of the DHU-11, for dealing with XON/XOFF
 flow-control or hard-wired
 lines for example.
 .Pp
-Although the devices are not the same, a
-.Tn DHU-11
-can convince the
-.Tn DH-11
-autoconfiguration code that it is a
-.Tn DH-11 .
+Although the devices are not the same, a DHU-11 can convince the DH-11
+autoconfiguration code that it is a DH-11.
 .Pp
 The 4 40-way cables are a pain.
 .Sh SEE ALSO
@@ -106,6 +91,4 @@ driver showed up in
 .Sh BUGS
 Even if the
 .Nm
-hardware supports
-.Tn DMA ,
-the driver cannot make use of this capability.
+hardware supports DMA, the driver cannot make use of this capability.
diff --git a/share/man/man4/man4.vax/dz.4 b/share/man/man4/man4.vax/dz.4
index 46d4a4d3e96..a717d5d97f5 100644
--- a/share/man/man4/man4.vax/dz.4
+++ b/share/man/man4/man4.vax/dz.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: dz.4,v 1.13 2013/06/02 20:42:27 tedu Exp $
+.\"	$OpenBSD: dz.4,v 1.14 2015/09/10 15:16:43 schwarze Exp $
 .\"	$NetBSD: dz.4,v 1.3 1996/03/03 17:13:29 thorpej Exp $
 .\"
 .\" Copyright (c) 1980, 1991 Regents of the University of California.
@@ -30,14 +30,12 @@
 .\"
 .\"     from: @(#)dz.4	6.3 (Berkeley) 3/27/91
 .\"
-.Dd $Mdocdate: June 2 2013 $
+.Dd $Mdocdate: September 10 2015 $
 .Dt DZ 4 vax
 .Os
 .Sh NAME
 .Nm dz
-.Nd
-.Tn DZ-11
-multiplexer device interface
+.Nd DZ-11 multiplexer device interface
 .Sh SYNOPSIS
 .Cd "dz0 at uba0 csr 0160100"
 .Cd "dz0 at vsbus0 csr 0x200a0000" Pq "DC-367"
@@ -46,9 +44,7 @@ multiplexer device interface
 .Cd "lkkbd0 at dz0 line 0"
 .Cd "lkms0  at dz0 line 1"
 .Sh DESCRIPTION
-A
-.Tn DZ-11
-provides 4 or 8 communication lines with partial modem control,
+A DZ-11 provides 4 or 8 communication lines with partial modem control,
 adequate for
 .Ox
 dialup use.
@@ -107,8 +103,7 @@ dialups
 .It dz0: silo overflow.
 The 64 character input silo overflowed
 before it could be serviced.
-This can happen if a hard error occurs when the
-.Tn CPU
+This can happen if a hard error occurs when the CPU
 is running with elevated priority, as the system will
 then print a message on the console with interrupts disabled.
 It is not serious.
diff --git a/share/man/man4/man4.vax/mt.4 b/share/man/man4/man4.vax/mt.4
index 956544684db..fba520f2b26 100644
--- a/share/man/man4/man4.vax/mt.4
+++ b/share/man/man4/man4.vax/mt.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: mt.4,v 1.12 2013/06/02 20:42:27 tedu Exp $
+.\"	$OpenBSD: mt.4,v 1.13 2015/09/10 15:16:43 schwarze Exp $
 .\"	$NetBSD: mt.4,v 1.3 1996/03/03 17:13:52 thorpej Exp $
 .\"
 .\" Copyright (c) 1980, 1991 Regents of the University of California.
@@ -30,29 +30,19 @@
 .\"
 .\"     from: @(#)mt.4	6.4 (Berkeley) 3/27/91
 .\"
-.Dd $Mdocdate: June 2 2013 $
+.Dd $Mdocdate: September 10 2015 $
 .Dt MT 4 vax
 .Os
 .Sh NAME
 .Nm mt
-.Nd
-.Tn TM78 Ns / Tn TU-78
-.Tn MASSBUS
-magtape interface
+.Nd TM78/TU-78 MASSBUS magtape interface
 .Sh SYNOPSIS
 .Cd "mt* at mscpbus? drive?"
 .Sh DESCRIPTION
-The
-.Tn TM78 Ns / Tn TU-78
-combination provides a standard tape drive
+The TM78/TU-78 combination provides a standard tape drive
 interface as described in
 .Xr mtio 4 .
-Only 1600 and 6250
-.Tn BPI
-are supported; the
-.Tn TU-78
-runs at 125
-.Tn IPS
+Only 1600 and 6250 BPI are supported; the TU-78 runs at 125 IPS
 and autoloads tapes.
 .Sh DIAGNOSTICS
 .Bl -diag
@@ -98,9 +88,7 @@ If a physical error (non-data) occurs,
 .Nm
 may hang ungracefully.
 .Pp
-Because 800
-.Tn BPI
+Because 800 BPI
 tapes are not supported, the numbering of minor devices
 is inconsistent with triple-density tape units.
-Unit 0 is drive 0, 1600
-.Tn BPI .
+Unit 0 is drive 0, 1600 BPI.
diff --git a/share/man/man4/man4.vax/mtc.4 b/share/man/man4/man4.vax/mtc.4
index 373530d1fff..dd114e38465 100644
--- a/share/man/man4/man4.vax/mtc.4
+++ b/share/man/man4/man4.vax/mtc.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: mtc.4,v 1.8 2015/02/15 22:26:45 bentley Exp $
+.\"	$OpenBSD: mtc.4,v 1.9 2015/09/10 15:16:43 schwarze Exp $
 .\"	$NetBSD: mtc.4,v 1.4 2001/04/11 19:23:01 wiz Exp $
 .\"
 .\" Copyright (c) 1980, 1987, 1991 Regents of the University of California.
@@ -30,14 +30,12 @@
 .\"
 .\"     from: @(#)uda.4	6.6 (Berkeley) 3/27/91
 .\"
-.Dd $Mdocdate: February 15 2015 $
+.Dd $Mdocdate: September 10 2015 $
 .Dt MTC 4 vax
 .Os
 .Sh NAME
 .Nm mtc
-.Nd
-.Tn UNIBUS
-MSCP tape controller driver
+.Nd UNIBUS MSCP tape controller driver
 .Sh SYNOPSIS
 .Cd "mtc0 at uba? csr 0174500"
 .Cd "mscpbus* at mtc?"
@@ -56,8 +54,7 @@ Among these controllers are:
 The
 .Nm
 communicates with the host through
-a packet protocol known as the Mass Storage Control Protocol
-.Pq Tn MSCP .
+a packet protocol known as the Mass Storage Control Protocol (MSCP).
 Consult the file
 .In mscp/mscp.h
 for a detailed description of this protocol.
diff --git a/share/man/man4/man4.vax/ncr.4 b/share/man/man4/man4.vax/ncr.4
index 85fb9b9589d..a4f02b20077 100644
--- a/share/man/man4/man4.vax/ncr.4
+++ b/share/man/man4/man4.vax/ncr.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ncr.4,v 1.7 2012/08/14 01:08:19 dlg Exp $
+.\"	$OpenBSD: ncr.4,v 1.8 2015/09/10 15:16:43 schwarze Exp $
 .\"
 .\" Copyright (c) 2003 Jason L. Wright (jason@thought.net)
 .\" All rights reserved.
@@ -24,13 +24,12 @@
 .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: August 14 2012 $
+.Dd $Mdocdate: September 10 2015 $
 .Dt NCR 4 vax
 .Os
 .Sh NAME
 .Nm ncr
-.Nd
-VAXstation 2000/3100 SCSI controller
+.Nd VAXstation 2000/3100 SCSI controller
 .Sh SYNOPSIS
 .Cd "ncr0 at vsbus0 csr 0x200c0080"
 .Cd "ncr1 at vsbus0 csr 0x200c0180"
diff --git a/share/man/man4/man4.vax/rx.4 b/share/man/man4/man4.vax/rx.4
index 4fd34b7f306..fd47894d2ce 100644
--- a/share/man/man4/man4.vax/rx.4
+++ b/share/man/man4/man4.vax/rx.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: rx.4,v 1.17 2014/11/15 14:41:02 bentley Exp $
+.\"	$OpenBSD: rx.4,v 1.18 2015/09/10 15:16:43 schwarze Exp $
 .\"	$NetBSD: rx.4,v 1.3 1996/03/03 17:14:03 thorpej Exp $
 .\"
 .\" Copyright (c) 1983, 1991 Regents of the University of California.
@@ -30,53 +30,33 @@
 .\"
 .\"     from: @(#)rx.4	6.2 (Berkeley) 3/27/91
 .\"
-.Dd $Mdocdate: November 15 2014 $
+.Dd $Mdocdate: September 10 2015 $
 .Dt RX 4 vax
 .Os
 .Sh NAME
 .Nm rx
-.Nd
-.Tn DEC
-.Tn RX02
-floppy disk interface
+.Nd DEC RX02 floppy disk interface
 .Sh SYNOPSIS
 .Cd "rx* at mscpbus? drive?"
 .Sh DESCRIPTION
 The
 .Nm rx
-device provides access to a
-.Tn DEC
-.Tn RX02
-floppy disk
-unit with M8256 interface module
-.Pf ( Tn RX211
-configuration).
-The
-.Tn RX02
-uses 8-inch, single-sided, soft-sectored floppy
+device provides access to a DEC RX02 floppy disk
+unit with M8256 interface module (RX211 configuration).
+The RX02 uses 8-inch, single-sided, soft-sectored floppy
 disks (with pre-formatted industry-standard headers) in
 either single or double density.
 .Pp
-Floppy disks handled by the
-.Tn RX02
-contain 77 tracks, each with 26
+Floppy disks handled by the RX02 contain 77 tracks, each with 26
 sectors (for a total of 2,002 sectors).
 The sector size is 128 bytes for single density, 256 bytes for double density.
-Single density disks are compatible with the
-.Tn RX01
-floppy disk unit and with
-.Tn IBM
-3740 Series Diskette 1 systems.
+Single density disks are compatible with the RX01
+floppy disk unit and with IBM 3740 Series Diskette 1 systems.
 .Pp
-In addition to normal (`block' and `raw')
-.Tn I/O ,
-the driver supports
+In addition to normal (`block' and `raw') I/O, the driver supports
 formatting of disks for either density and
 the ability to invoke a 2 for 1 interleaved sector mapping
-compatible with the
-.Tn DEC
-operating system
-.Tn RT-11 .
+compatible with the DEC operating system RT-11.
 .Pp
 The minor device number is interpreted as follows:
 .Bl -column "Other" "Description" -offset indent
@@ -87,15 +67,9 @@ The minor device number is interpreted as follows:
 .It Other Ta "Drive number"
 .El
 .Pp
-The two drives in a single
-.Tn RX02
-unit are treated as
+The two drives in a single RX02 unit are treated as
 two disks attached to a single controller.
-Thus, if there are two
-.Tn RX02 Ns 's
-on a system, the drives on the first
-.Tn RX02
-are
+Thus, if there are two RX02's on a system, the drives on the first RX02 are
 .Dq Li rx0
 and
 .Dq Li rx1 ,
diff --git a/share/man/man4/man4.vax/uda.4 b/share/man/man4/man4.vax/uda.4
index c07bc33e32a..4bf2ab59386 100644
--- a/share/man/man4/man4.vax/uda.4
+++ b/share/man/man4/man4.vax/uda.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: uda.4,v 1.23 2015/02/15 22:26:45 bentley Exp $
+.\"	$OpenBSD: uda.4,v 1.24 2015/09/10 15:16:43 schwarze Exp $
 .\"	$NetBSD: uda.4,v 1.3 1996/03/03 17:14:10 thorpej Exp $
 .\"
 .\" Copyright (c) 1980, 1987, 1991 Regents of the University of California.
@@ -30,28 +30,21 @@
 .\"
 .\"     from: @(#)uda.4	6.6 (Berkeley) 3/27/91
 .\"
-.Dd $Mdocdate: February 15 2015 $
+.Dd $Mdocdate: September 10 2015 $
 .Dt UDA 4 vax
 .Os
 .Sh NAME
 .Nm uda
-.Nd
-.Tn UDA50
-disk controller interface
+.Nd UDA50 disk controller interface
 .Sh SYNOPSIS
 .Cd "uda0 at uba? csr 0172150"
 .Cd "uda1 at uba? csr 0160334"
 .Cd "mscpbus* at uda?"
 .Sh DESCRIPTION
-This is a driver for the
-.Tn DEC UDA50
-disk controller and other
+This is a driver for the DEC UDA50 disk controller and other
 compatible controllers.
-The
-.Tn UDA50
-communicates with the host through
-a packet protocol known as the Mass Storage Control Protocol
-.Pq Tn MSCP .
+The UDA50 communicates with the host through
+a packet protocol known as the Mass Storage Control Protocol (MSCP).
 Consult the file
 .In vax/mscp.h
 for a detailed description of this protocol.
@@ -262,10 +255,7 @@ The controller reported an error.
 The error code is printed in
 octal, along with a short description if the code is known (see the
 .%T UDA50 Maintenance Guide ,
-.Tn DEC
-part number
-.Tn AA-M185B-TC ,
-pp. 18-22).
+DEC part number AA-M185B-TC, pp. 18-22).
 If this occurs during normal
 operation, the driver will reset it and retry pending I/O.
 If
@@ -279,9 +269,7 @@ The driver will retry initialization later.
 .It "uda0: version X model Y"
 An informational message giving the revision level of the controller.
 .It "uda0: DMA burst size set to N"
-An informational message showing the
-.Tn DMA
-burst size, in words.
+An informational message showing the DMA burst size, in words.
 .It "uda0: SETCTLRC failed:  `detail'"
 The Set Controller Characteristics command (the last part of the
 controller initialization sequence) failed.
@@ -302,12 +290,8 @@ The
 .Em detail
 message should tell why.
 .It "panic: udareplace"
-The controller reported completion of a
-.Tn REPLACE
-operation.
-The driver never issues any
-.Tn REPLACE Ns s ,
-so something is wrong.
+The controller reported completion of a REPLACE operation.
+The driver never issues any REPLACE operations, so something is wrong.
 .It "panic: udabb"
 The controller reported completion of bad block related I/O.
 The
@@ -385,8 +369,7 @@ read.
 A typical disk error; the retry count and error recovery levels are
 printed, along with the block type (`lbn', or logical block; or `rbn',
 or replacement block) and number.
-If the string is something else,
-.Tn DEC
+If the string is something else, DEC
 has been clever, or your hardware has gone to Australia for vacation
 (unless you live there; then it might be in New Zealand, or Brazil).
 .It unit N: ... N
@@ -443,11 +426,7 @@ The Format Control
 Table cannot be read (`fct unread - edc'), there is a bad sector
 header (`invalid sector header'), the drive is not set for 512-byte
 sectors (`not 512 sectors'), the drive is not formatted (`not formatted'),
-or the
-.Tn FCT
-has an uncorrectable
-.Tn ECC
-error (`fct ecc').
+or the FCT has an uncorrectable ECC error (`fct ecc').
 .It "write protected (...) (code 6, subcode N)"
 The drive is write protected, either by the front panel switch
 (`hardware') or via the driver (`software').
@@ -466,13 +445,9 @@ no bad block replacement, so these should not occur.
 A `header compare' error probably means the block is shot.
 A `sync timeout' presumably has something to do with sector synchronisation.
 An `uncorrectable ecc' error is an ordinary data error that cannot
-be fixed via
-.Tn ECC
-logic.
+be fixed via ECC logic.
 A `N symbol ecc' error is a data error
-that can be (and presumably has been) corrected by the
-.Tn ECC
-logic.
+that can be (and presumably has been) corrected by the ECC logic.
 It might indicate a sector that is imperfect but usable, or that
 is starting to go bad.
 If any of these errors recur, the sector