mdoc nits. New sentence, new line. Remove a comment about tahoe.

sbin/disklabel/disklabel.8

@@ -1,4 +1,4 @@
-.\"	$NetBSD: disklabel.8,v 1.40 2002/08/19 01:54:58 enami Exp $
+.\"	$NetBSD: disklabel.8,v 1.41 2002/09/28 00:24:13 wiz Exp $
 .\"
 .\" Copyright (c) 1987, 1988, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
@@ -36,7 +36,7 @@
 .\"
 .\"	@(#)disklabel.8	8.2 (Berkeley) 4/19/94
 .\"
-.Dd April 19, 1994
+.Dd December 14, 2001
 .Dt DISKLABEL 8
 .Os
 .Sh NAME
@@ -133,14 +133,14 @@ flag are described with the affected commands.
 The read and install forms also support the
 .Fl B
 option to install bootstrap code on some platforms,
-e.g. hp300, vax, and arm32.
+e.g., hp300, vax, and arm32.
 The
 .Fl B
 option is not supported on all platforms.
 These variants are described later.
 .Pp
 The first form of the command (read) is used to examine the label on the named
-disk drive (e.g. sd0 or /dev/rsd0c).
+disk drive (e.g., sd0 or /dev/rsd0c).
 It will display all of the parameters associated with the drive
 and its partition layout.
 Unless the
@@ -206,7 +206,8 @@ The
 .Fl C
 flag causes the partition offset and size values to be displayed in
 .Aq cylinder/track/sector
-format. Note that, regardless of whether
+format.
+Note that, regardless of whether
 .Fl C
 was specified, this format is always accepted by
 .Nm
@@ -268,8 +269,11 @@ the secondary boot program.
 If the names are not explicitly given, standard boot programs will be used.
 The boot programs are located in
 .Pa /usr/mdec .
-The names of the programs are taken from the ``b0'' and ``b1'' parameters
-of the
+The names of the programs are taken from the
+.Dq b0
+and
+.Dq b1
+parameters of the
 .Xr disktab 5
 entry for the disk if
 .Ar disktype
@@ -308,16 +312,19 @@ Display the in-core label for sd0 as obtained via
 .Pp
 .Dl disklabel -w -r /dev/rsd0c sd2212 foo
 .Pp
-Create a label for sd0 based on information for ``sd2212'' found in
+Create a label for sd0 based on information for
+.Dq sd2212
+found in
 .Pa /etc/disktab ,
 using
 .Pa foo
 as the disk pack label.
-Any existing bootstrap code will be clobbered.  If you do not have an
-entry for your disk in
+Any existing bootstrap code will be clobbered.
+If you do not have an entry for your disk in
 .Pa /etc/disktab ,
 you can use this style to put
-an initial label onto a new disk.  Then dump the label to a file (using
+an initial label onto a new disk.
+Then dump the label to a file (using
 .Em disklabel sd0 \*[Gt]
 .Em protofile ) ,
 editing the file, and replacing the label with
@@ -361,15 +368,17 @@ On-disk and in-core labels are unchanged.
 Install a new label and bootstrap (on platforms which support the
 .Fl B
 option, see above).
-The label is derived from disktab information for ``sd2212'' and
-installed both in-core and on-disk.
+The label is derived from disktab information for
+.Dq sd2212
+and installed both in-core and on-disk.
 The bootstrap code comes from the file
 .Pa /usr/mdec/newboot .
 .Pp
 .Dl disklabel -R -r sd0 \*[Lt]protofile\*[Gt]
 .Pp
 Install a new label and bootstrap on a disk, from a prototype label
-file.  This is a good way to install a label on a previously unlabeled
+file.
+This is a good way to install a label on a previously unlabeled
 disk for which no entry appears in
 .Pa  /etc/disktab ,
 if you create the
@@ -379,17 +388,22 @@ it appropriately (total size, partition offsets, types, etc.)
 The kernel device drivers will not allow the size of a disk partition
 to be decreased or the offset of a partition to be changed while it is open.
 Some device drivers create a label containing only a single large partition
-if a disk is unlabeled; thus, the label must be written to the ``a''
+if a disk is unlabeled; thus, the label must be written to the
+.Dq a
 partition of the disk while it is open.
 This sometimes requires the desired label to be set in two steps,
 the first one creating at least one other partition,
 and the second setting the label on the new partition
-while shrinking the ``a'' partition.
+while shrinking the
+.Dq a
+partition.
 .Pp
 On some machines the bootstrap code may not fit entirely in the area
 allocated for it by some filesystems.
 As a result, it may not be possible to have filesystems on some partitions
-of a ``bootable'' disk.
+of a
+.Dq bootable
+disk.
 When installing bootstrap code,
 .Nm
 checks for these cases.
@@ -409,31 +423,36 @@ will not install bootstrap code that overlaps it.
 .Xr mbrlabel 8
 .Sh BUGS
 If the disk partition is not specified in the disk name
-(i.e. ``xy0'' instead of ``/dev/rxy0c''),
+(i.e.,
+.Dq xy0
+instead of
+.Dq /dev/rxy0c ) ,
 .Nm
-will construct the full pathname of the disk and use
-the ``a'' partition on the tahoe,
-the ``d'' partition on i386 or hpcmips or arc, and
-the ``c'' partition on all others.
+will construct the full pathname of the disk and use the
+.Dq d
+partition on i386, hpcmips, or arc, and the
+.Dq c
+partition on all others.
 .Pp
-On the sparc, sparc64, sun2 and sun3
+On the sparc, sparc64, sun2, and sun3
 .Nx
 systems, the size of each partition must be a multiple of the number
-of sectors per cylinder (i.e. each partition must be an integer
+of sectors per cylinder (i.e., each partition must be an integer
 number of cylinders), or the boot ROMs will declare the label
 invalid and fail to boot the system.
 .Pp
 In addition, the
 .Fl r
-option should never be used on a sparc, sparc64, sun2 or sun3 system 
+option should never be used on a sparc, sparc64, sun2 or sun3 system
 boot disk - the
 .Nx
 kernel translates the
 .Nx
 disk label into a SunOS compatible format (which is required by the
-boot PROMs) when it writes the label. Using the
+boot PROMs) when it writes the label.
+Using the
 .Fl r
-causes
+flag causes
 .Nm
 to write directly to disk, and bypass the format translation.
 This will result in a disk label that the PROMs will not recognize,