sbin/ man page fixes

10 files changed, 213 insertions, 199 deletions

diff --git a/sbin/reboot/boot_atari.8 b/sbin/reboot/boot_atari.8
index ad20feb592f..f77b382e2d3 100644
--- a/sbin/reboot/boot_atari.8
+++ b/sbin/reboot/boot_atari.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_atari.8,v 1.3 1998/09/01 16:38:19 deraadt Exp $
+.\"	$OpenBSD: boot_atari.8,v 1.4 1998/09/17 04:15:00 aaron Exp $
 .\"	$NetBSD: boot_atari.8,v 1.1 1996/06/27 11:07:56 leo Exp $
 .\"
 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
@@ -40,14 +40,14 @@
 .\"	@(#)boot_hp300.8	8.2 (Berkeley) 4/19/94
 .\"
 .Dd June 21, 1996
-.Dt boot_atari 8
+.Dt BOOT_ATARI 8
 .Os
 .Sh NAME
 .Nm boot
 .Nd
 system bootstrapping procedures
 .Sh DESCRIPTION
-.Sy Power fail and crash recovery
+.Ss Power fail and crash recovery
 .Pp
 When the
 .Tn OpenBSD
@@ -60,39 +60,38 @@ to shut the system down is with the
 command.
 .Pp
 If the system crashes, it will enter the kernel debugger,
-.Xr ddb 8
-,if it is configured in the kernel.  If the debugger is not present,
-or the debugger is exited, the system will attempt a dump to the
+.Xr ddb 8 ,
+if it is configured in the kernel.  If the debugger is not present
+or has exited, the system will attempt a dump to the
 configured dump device (which will be automatically recovered with
 .Xr savecore 8
-during the next boot cycle).  After the dump is complete (successful
+during the next boot cycle).  After the dump completes (successful
 or not), the system will attempt a reboot.
 .Pp
-.Sy Booting OpenBSD using the bootloader
+.Ss Booting OpenBSD using the bootloader
 .Pp
 When a bootable
 .Tn OpenBSD
 partition is created by means of
-.Xr installboot 8
-, the Atari BIOS will automatically start the OpenBSD bootloader. By default
+.Xr installboot 8 ,
+the Atari BIOS will automatically start the OpenBSD bootloader. By default,
 it will load the kernel image
 .Pa /bsd
-and attempts to boot it into multi-user mode. This behaviour can be changed by
+and attempt to boot it into multi-user mode. This behaviour can be changed by
 either keeping the
-.Pa Alternate
-or the
-.Pa Right-Shift
-key pressed during the boot. When
+.Sq Alternate
+or
+.Sq Right-Shift
+key pressed during the boot process. When
 the
-.Pa Alternate
+.Sq Alternate
 key is pressed, the bootstrap is aborted, causing the BIOS
 to continue scanning the disks for a bootable partition (this is compatible
 with AHDI 3.0). Pressing the
-.Pa Right-Shift
-key during the boot, causes the boot loader to enter the interactive mode.
+.Sq Right-Shift
+key during the boot causes the bootloader to enter interactive mode.
 In interactive mode, the command line looks like:
 .Bd -ragged -offset indent
-.Pp
 .Op Ar OS-type
 .Op Ar boot-path
 .Op Ar boot-options
@@ -112,28 +111,29 @@ indicated will be used.
 If something other than
 .Pa .OpenBSD
 is specified, control is returned to the BIOS with the boot preference set to
-the selected type. Due to limitations of the BIOS however, the search for
+the selected type. Due to limitations of the BIOS, however, the search for
 bootblocks is continued rather than restarted.
-.It boot-path
+.It Em boot-path
 This gives you the opportunity to boot another kernel, say:
-.Pa /bsd.old.
+.Pa /bsd.old .
 The default is
-.Pa /bsd
-.It boot-options
+.Pa /bsd .
+.It Em boot-options
 These options are a subset of the
 .Xr loadbsd
 options.
+.Pp
 .Bl -tag -width flag -compact
 .It Fl a
-Boot into multi-user mode (the default)
+Boot into multi-user mode (the default).
 .It Fl b
-Ask for a root device
+Ask for a root device.
 .It Fl d
-Enter the kernel debugger
+Enter the kernel debugger.
 .El
 .El
 .Pp
-.Sy Booting using the loadbsd program
+.Ss Booting using the loadbsd program
 .Pp
 When you want (or have to) start OpenBSD from GEM, you have to use the
 .Xr loadbsd
@@ -160,7 +160,7 @@ Print a help screen that tries to explain the same options as mentioned
 here.
 .It Fl o Ar outputfile
 Write all output to the file
-.Ar outputfile.
+.Ar outputfile .
 .It Fl s
 Tell OpenBSD only to use ST compatible RAM. 
 .It Fl t
@@ -186,7 +186,7 @@ This is a GEMDOS path specification of the kernel to boot.
 .Pp
 Note: Because the loadbsd program can only read kernels from a GEMDOS
 filesystem, the file
-.Ar /bsd
+.Pa /bsd
 is usually not the same as the actual kernel booted. This can cause some
 programs to fail.
 .Sh FILES
diff --git a/sbin/reboot/boot_hp300.8 b/sbin/reboot/boot_hp300.8
index cebb5e64a23..da91bed4e0b 100644
--- a/sbin/reboot/boot_hp300.8
+++ b/sbin/reboot/boot_hp300.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_hp300.8,v 1.3 1996/06/29 18:24:15 mickey Exp $
+.\"	$OpenBSD: boot_hp300.8,v 1.4 1998/09/17 04:15:00 aaron Exp $
 .\"	$NetBSD: boot_hp300.8,v 1.3 1995/04/23 10:33:34 cgd Exp $
 .\"
 .\" Copyright (c) 1990, 1991, 1993
@@ -46,26 +46,26 @@
 .Nd
 system bootstrapping procedures
 .Sh DESCRIPTION
-.Sy Power fail and crash recovery.
+.Ss Power fail and crash recovery
+.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
-.Sy Cold starts.
+.Ss Cold starts
+.Pp
 On an HP300, the boot procedure uses the boot ROM to load a boot program
 from an
 .Tn LIF
 format directory at the beginning of an attached disk.
 The
 .Pa /usr/mdec
-directory contains a disk boot programs which should be placed in a
+directory contains a disk boot program which should be placed in a
 new pack automatically by
 .Xr newfs 8
 when the ``a'' partition file system on the pack is created.
 .Pp
-This
-.Em boot
-program
+This boot program
 finds the corresponding file on the given device 
 .Pf ( Ar bsd
 by default),
@@ -95,10 +95,10 @@ Currently, ``rd'' and ``sd'' are the only valid
 specifiers.
 .Pp
 For example,
-to boot from the `a' file system of unit 0 on HP-IB 2,
+to boot from the ``a'' file system of unit 0 on HP-IB 2,
 type
 .Ql rd(16, 0)bsd
-to the boot prompt.
+at the boot prompt.
 For tapes, the minor device number gives a file offset.
 .Pp
 In an emergency, the bootstrap methods described in the paper
diff --git a/sbin/reboot/boot_i386.8 b/sbin/reboot/boot_i386.8
index f648ab7386f..9652471c48d 100644
--- a/sbin/reboot/boot_i386.8
+++ b/sbin/reboot/boot_i386.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_i386.8,v 1.5 1998/07/11 22:46:09 angelos Exp $
+.\"	$OpenBSD: boot_i386.8,v 1.6 1998/09/17 04:15:00 aaron Exp $
 .\"
 .\" Copyright (c) 1997 Tobias Weingartner
 .\"
@@ -32,19 +32,21 @@
 .\" 
 
 .Dd September 4, 1997
-.Dt BOOT_i386 8 i386
+.Dt BOOT_I386 8 i386
 .Os
 .Sh NAME
 .Nm boot
 .Nd
 system bootstrapping procedures
 .Sh DESCRIPTION
-.Sy Power fail and crash recovery.
+.Ss Power fail and crash recovery
+.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
-.Sy Cold starts.
+.Ss Cold starts
+.Pp
 The
 .Tn "PC AT"
 clones will perform a POST (Power On Self Test) upon being booted cold.
@@ -60,31 +62,31 @@ if it is an older BIOS, it will start with checking for a disk in floppy
 drive A (otherwise known as drive 0) first, and failing that, attempt to
 boot the hard disk C (otherwise known as hard disk controller 1, drive 0).
 .Pp
-.Sy Warm starts.
+.Ss Warm starts
+.Pp
 The BIOS loads the first block (at physical location: track 0, head 0,
 sector 1) off the boot device into memory, and if the last two bytes in the
 block match the signature 0x55AA, the BIOS considers the block a valid
 bootable drive.  The BIOS then proceeds to call the machine code program
 in this block.  If the BIOS is current, it will also pass the boot drive
-to the boot block in register
-.Sy %dl.
+to the boot block in register %dl.
 .Pp
 There are two different types of boot blocks on devices.  There is the
-MBR (master boot record), and the PBR (partition boot record).  A digression
+MBR (master boot record) and the PBR (partition boot record).  A digression
 into a little piece of history will quickly give light as to why this is so.
 In the beginning, the PC ``architecture'' came with a single or dual floppy
 drives, and no hard drives.  The only type of bootable sectors on any device
 were the PBRs.  They were responsible for loading the rest of the operating
-system from the right device.  When hard disks came out, it was felt that
+system from the correct device.  When hard disks came out, it was felt that
 such a huge space should be able to be partitioned into separate drives,
-and this is where the MBR was invented.
+and this is when the MBR was invented.
 .Pp
 The MBR relocates itself upon being loaded and invoked by the BIOS.
-Embeded within the MBR is a partition table, with four partitions table
+Embeded within the MBR is a partition table, with four partition table
 entries.  The MBR code traverses this table (which was loaded with the
 MBR by the BIOS), looking for an active entry, and then loads the MBR or
 PBR from the disk location specified by the partition table entry.  So
-in all reality, the MBR is nothing more than a fancy chaining PBR.
+in reality, the MBR is nothing more than a fancy chaining PBR.
 .Pp
 Note: The MBR could load another MBR, which is the case when you are booting
 off an extended partition.  In other words, the first block of an extended
@@ -110,7 +112,7 @@ cylinder/head/sector of the real drive geometry into something that would
 allow the applications using the BIOS to access a larger portion of the
 drive, still using the restricted BIOS API.
 .Pp
-The reason this has become a problem, is that any modern OS will use its own
+The reason this has become a problem is that any modern OS will use its own
 drivers to access the disk drive, bypassing the BIOS completely.  However,
 the MBR, PBR, and partition tables are all still written using the original
 BIOS access methods.  This is for backwards compatibility to the original
@@ -141,7 +143,7 @@ system second stage bootstrap
 .Xr boot 8
 .Sh BUGS
 The ``PC BIOS Architecture'' makes this process very prone to weird and
-wonderfull interactions between differing operating systems.  There is
+wonderful interactions between differing operating systems.  There is
 no published standard to the MBR and PBR, which makes coding these a
 nightmare.  Somebody *please* write me a decent BIOS, and make them (the
 masses) use it!
diff --git a/sbin/reboot/boot_mac68k.8 b/sbin/reboot/boot_mac68k.8
index cf605e7cff9..bacff4a7fad 100644
--- a/sbin/reboot/boot_mac68k.8
+++ b/sbin/reboot/boot_mac68k.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_mac68k.8,v 1.5 1998/02/26 16:32:40 gene Exp $
+.\"	$OpenBSD: boot_mac68k.8,v 1.6 1998/09/17 04:15:00 aaron Exp $
 .\"	$NetBSD: boot_mac68k.8,v 1.1 1995/07/02 02:09:52 briggs Exp $
 .\"
 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
@@ -47,7 +47,8 @@
 .Nd
 system bootstrapping procedures
 .Sh DESCRIPTION
-.Sy Power fail and crash recovery.
+.Ss Power fail and crash recovery
+.Pp
 Normally, the
 .Ox
 kernel on the mac68k architecture is booted from the native operating
@@ -61,15 +62,15 @@ command.
 .Pp
 If the system crashes, it will enter the kernel debugger,
 .Xr ddb 8 ,
-if it is configured in the kernel.  If the debugger is not present,
-or the debugger is exited, the system will attempt a dump to the
+if it is configured in the kernel.  If the debugger is not present
+or has exited, the system will attempt a dump to the
 configured dump device (which will be automatically recovered with
 .Xr savecore 8
-during the next boot cycle).  After the dump is complete (successful
+during the next boot cycle).  After the dump completes (successful
 or not), the system will attempt a reboot.
 .Pp
 On most mac68k machines with "soft-power" after the IIcx, the power
-switch can be physically rotated and locked in the 'on' position.
+switch can be physically rotated and locked in the ``on'' position.
 The native OS can be configured to automatically start the
 .Ox
 boot program.  Additionally, the OpenBSD boot program can be configured
@@ -79,11 +80,12 @@ without intervention.  When a system is so configured, it can crash
 or lose power and reboot back to a fully multi-user state without
 any intervention.
 .Pp
-.Sy The boot application
+.Ss The boot application
+.Pp
 The boot application runs in the native OS on the system.  It has a
 dialog where booting preferences may be changed and an option whereby
 these options may be saved.  The preferences are stored in the program
-itself, not in a preferences folder--thus allowing two separate copies
+itself, not in a preferences folder, thus allowing two separate copies
 of the program to be configured differently (e.g. to boot different
 bsd or bsd.test, or to boot from two different drives).
 .Pp
@@ -99,7 +101,7 @@ file.
 Another useful option that may be specified is the "serial console"
 option.  This will allow a serial device (terminal or computer) to
 act as a console for the system.  This device must be configured to
-use 9600 baud, eight bits, no parity, and one stop bit (9600-N81).
+use 9600 baud, eight bits, no parity, and one stop bit (9600-8N1).
 Either the printer port or the modem port (tty01 and tty00,
 respectively) may be used for this.
 .Pp
@@ -108,7 +110,7 @@ in native OS rather than from the usual location in the
 .Ox
 file system.  A radio button is supplied for this purpose.  Note that
 some programs will not run properly if the kernel is not found as
-.Ar /bsd
+.Pa /bsd
 within the 
 .Tn OpenBSD
 file system.
diff --git a/sbin/reboot/boot_pmax.8 b/sbin/reboot/boot_pmax.8
index 532b979d910..cd9439b4ab9 100644
--- a/sbin/reboot/boot_pmax.8
+++ b/sbin/reboot/boot_pmax.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_pmax.8,v 1.6 1998/07/24 20:49:08 deraadt Exp $
+.\"	$OpenBSD: boot_pmax.8,v 1.7 1998/09/17 04:15:00 aaron Exp $
 .\"	$NetBSD: boot_pmax.8,v 1.1 1995/04/25 23:55:11 mellon Exp $
 .\"
 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
@@ -52,31 +52,33 @@ Since the system is not reenterable,
 it is necessary to read it in from disk or tape
 each time it is to be bootstrapped.
 .Pp
-.Sy Power fail and crash recovery.
+.Ss Power fail and crash recovery
+.Pp
 Normally, the system will boot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
-.Sy Cold starts.
+.Ss Cold starts
+.Pp
 At power up, all DECstation ROMs consult the
 .Nm haltaction
 environment
-variable in EEPROM to determine whether or not to attempt to boot
-automatically.   If this
-variable is set to \fBh\fR, the ROM prints a prompt on the console and
-waits for user commands.   If set to \fBb\fR, the ROM attempts to autoboot.
+variable in EEPROM to determine whether or not to attempt an automatic
+boot.  If this
+variable is set to ``h'', the ROM prints a prompt on the console and
+waits for user commands.  If set to ``b'', the ROM attempts to autoboot.
 .Pp
 On the DECstation 2100 and 3100, the path used for automatic booting is
 stored in the
 .Nm bootpath
-environment variable.   The path is made up of a 
-device type specifier (e.g., rz, tz, mop or tftp) followed by
+environment variable.  The path is made up of a 
+device type specifier (e.g., rz, tz, mop or tftp), followed by
 a triplet in the form (x,y,z), followed by a filename to load.
 .Pp
-Within the triplet, x is the controller (always 0), y is the SCSI id of
+Within the triplet, ``x'' is the controller (always 0), ``y'' is the SCSI ID of
 the drive to
-boot from or 0 for net boots, and z is the partition to boot from
-(usually 0 for SCSI devices, always zero for network booting.
+boot from or 0 for net boots, and ``z'' is the partition to boot from
+(usually 0 for SCSI devices, always zero for network booting).
 For network boots, () may be specified instead of (0,0,0).
 .Pp
 The filename is optional for bootp/tftp and mop booting, since in
@@ -84,9 +86,11 @@ these cases the network protocol can be used to determine which
 file to boot.  When booting off the tape, no filename should be
 specified, and when booting off of disk, the filename of a kernel
 must be specified.  Generally, the kernel is named
-.Nm bsd.
+.Pa bsd .
 .Pp
-An example bootpath setting would be:
+An example
+.Nm bootpath
+setting would be:
 .nf
 .sp 1
 .ce 1
@@ -95,17 +99,17 @@ setenv bootpath rz(0,1,0)bsd
 .Pp
 For automatic boots, the ROM automatically passes a
 .Fl a
-argument to the boot
-loader, requesting that
+argument to the bootloader,
+requesting that
 .Tn OpenBSD
-attempt to come up to multi-user mode.   At the boot ROM prompt,
+attempt to come up to multi-user mode.  At the boot ROM prompt,
 the user may boot
 .Tn OpenBSD
 with either the
 .Nm auto
 or the
 .Nm boot
-command.   If the
+command.  If the
 .Nm auto
 command is used, the
 .Fl a
@@ -120,8 +124,9 @@ When either the
 .Nm boot
 or the
 .Nm auto
-command is issued with no arguments, the kernel specified in the bootpath
-environment variable is booted.   An alternate kernel may be specified
+command is issued with no arguments, the kernel specified in the
+.Nm bootpath
+environment variable is booted.  An alternate kernel may be specified
 with the
 .Fl f
 flag, followed by the path of the kernel to boot, as described above.
@@ -130,14 +135,16 @@ For example:
 .ce 1
 boot -f rz(0,4,0)bsd.new
 .Pp
-On TurboChannel machines (all DECstation 5000 models), the boot path
-is specified in the boot environment variable, along with any arguments
-to be passed to the kernel.   Note that to specify boot arguments (e.g.,
-.Fl a)
+On TurboChannel machines (all DECstation 5000 models), the bootpath
+is specified in the
+.Nm boot
+environment variable, along with any arguments
+to be passed to the kernel.  Note that to specify boot arguments (e.g.,
+.Fl a )
 when setting the
 .Nm boot
 environment variable, the filename and arguments
-must be enclosed in quotes.   For example:
+must be enclosed in quotes.  For example:
 .nf
 .sp 1
 .ce 1
@@ -146,19 +153,19 @@ setenv boot "3/rz4/bsd -a"
 .Pp
 The device from which to boot is specified as the TurboChannel slot
 number, a TurboChannel-option-specific device name, and a path to the
-file to load, all separated by slashes.   You can get a list of the
+file to load, all separated by slashes.  You can get a list of the
 devices installed in your TurboChannel slots (as well as any built-in
 devices which appear as TurboChannel slots) by typing the
 .Nm cnfg
 command
-at the boot prompt.   You can get more detailed information about a specific
+at the boot prompt.  You can get more detailed information about a specific
 TurboChannel option by typing
 .Nm cnfg
 followed by the slot number of that
 option.
 .Pp
-For SCSI devices, the option-specific device identifier is either rz# for
-disks or tz# for tapes, where # is the SCSI id of the device.   For network
+For SCSI devices, the option-specific device identifier is either ``rz#'' for
+disks or ``tz#'' for tapes, where # is the SCSI ID of the device.  For network
 devices, the option-specific protocol identifier is either mop or tftp.
 Filename requirements are as for the DECstation 2100 and 3100.
 .Pp
@@ -166,18 +173,20 @@ To start
 .Tn OpenBSD
 from the boot prompt, the
 .Nm boot
-command must be used.   With no arguments, this simply boots the default
+command must be used.  With no arguments, this simply boots the default
 kernel with the default arguments as set with
 .Nm setenv
-.Nm boot.
-If no boot environment variable is set or if an alternate kernel is to be
+.Nm boot .
+If no
+.Nm boot
+environment variable is set, or if an alternate kernel is to be
 booted, the path of that kernel may be specified after the boot command as
-described above, and any arguments may be passed similarly.   For example:
+described above, and any arguments may be passed similarly.  For example:
 .sp 1
 .ce 1
 boot 3/rz4/bsd.new -a
 .Sh SEE ALSO
-.Xr crash 8m ,
+.Xr crash 8 ,
 .Xr fsck 8 ,
 .Xr halt 8 ,
 .Xr init 8 ,
diff --git a/sbin/reboot/boot_sparc.8 b/sbin/reboot/boot_sparc.8
index 87712f482db..d92e7f01c1f 100644
--- a/sbin/reboot/boot_sparc.8
+++ b/sbin/reboot/boot_sparc.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_sparc.8,v 1.5 1998/07/11 22:46:12 angelos Exp $
+.\"	$OpenBSD: boot_sparc.8,v 1.6 1998/09/17 04:15:00 aaron Exp $
 .\"	$NetBSD: boot_sparc.8,v 1.4 1995/04/25 11:37:25 pk Exp $
 .\"
 .\" Copyright (c) 1992, 1993
@@ -35,7 +35,7 @@
 .\"     @(#)boot_sparc.8	8.2 (Berkeley) 4/19/94
 .\"
 .Dd April 19, 1994
-.Dt boot_sparc 8 sparc
+.Dt BOOT_SPARC 8 sparc
 .Os
 .Sh NAME
 .Nm reboot
@@ -47,57 +47,57 @@ bootstrapping procedures
 .Op Fl n
 .Op Fl q
 .Sh DESCRIPTION
-.Sy Power fail and crash recovery.
+.Ss Power fail and crash recovery
+.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed
-as described in
-.Xr fsck 8 .
+(as described in
+.Xr fsck 8 ),
 and unless this fails, the system will resume multi-user operations.
 .Pp
-.Sy Cold starts
+.Ss Cold starts
+.Pp
 The SPARC system currently uses the SunOS bootstrap loaders.
 This will be changed in a future version of the system.
 The SunOS boot will attempt to load
 .Pa bsd
-from partition A of the boot device,
+from partition ``a'' of the boot device,
 which must currently be an ``sd'' disk.
 .Pp
 The
-.Op Fl s
-flag to the SunOS boot loader will being the system up in single-user mode.
+.Fl s
+flag to the SunOS bootloader will bring the system up in single-user mode.
 The
-.Op Fl a
+.Fl a
 flag instructs the system to prompt for the location of the root filesystem
 and the primary swap partition.
 .\"The
 .\".Op Fl d
-.\"flag to the SunOS boot loader will bring the system up in debug mode.
+.\"flag to the SunOS bootloader will bring the system up in debug mode.
 .\"Here it waits for a kernel debugger connect; see
 .\".Xr kgdb 8 .
 Other flags are currently ignored.
 .Pp
-The Sparc boot rom comes in two flavours: an ``old-style'' rom is used in
-sun4 machines, while A ``new-style'' rom can be found on sun4c and sun4m models.
-The ``new-style'' Sparc boot rom is a full-featured Forth system with emacs
+The SPARC boot ROM comes in two flavours: an ``old-style'' ROM is used in
+sun4 machines, while a ``new-style'' ROM can be found on sun4c and sun4m models.
+The ``new-style'' SPARC boot ROM is a full-featured Forth system with emacs
 key bindings. It can be put in ``old-style'' user-interface compatibility
 mode (in which case it shows a simple `>' prompt), but this is essentially
-useless. However, by default the rom runs in old-mode; to enter new-mode type `n'.
-The rom then shows a Forth-style `ok' prompt. It is recommended to have
-the rom always start in its native ``new-style'' mode. Utter the following
-incantation in new-mode to force the rom to always start in new-mode.
+useless. However, by default the ROM runs in old-mode; to enter new-mode type `n'.
+The ROM then shows a Forth-style `ok' prompt. It is recommended to have
+the ROM always start in its native ``new-style'' mode. Utter the following
+incantation in new-mode to force the ROM to always start in new-mode:
 .Pp
-.Pa \	ok
+.Em \	ok
 setenv sunmon-compat? false
 .Pp
-The rom will normally load the kernel from "sd(0,0,0)bsd". To change the
-default so that
-.Pa OpenBSD
-will be loaded type the following
+The ROM will normally load the kernel from "sd(0,0,0)bsd". To change the
+default so that OpenBSD will be loaded, type the following:
 .Pp
-.Pa \	ok
+.Em \	ok
 setenv boot-from sd(0,0,0)bsd
 .Pp
-At any time you can break back to the rom by pressing the `L1' and `a'
+At any time you can break back to the ROM by pressing the `L1' and `a'
 keys at the same time (if the console is a serial port the same is
 achieved by sending a `break').
 If you do this accidentally you can continue whatever was in progress
diff --git a/sbin/reboot/boot_sun3.8 b/sbin/reboot/boot_sun3.8
index 902dbcec9f6..8f050a286cc 100644
--- a/sbin/reboot/boot_sun3.8
+++ b/sbin/reboot/boot_sun3.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_sun3.8,v 1.4 1998/07/11 22:46:13 angelos Exp $
+.\"	$OpenBSD: boot_sun3.8,v 1.5 1998/09/17 04:15:01 aaron Exp $
 .\"	$NetBSD: boot_sun3.8,v 1.1 1995/08/08 20:46:20 gwr Exp $
 .\"
 .\" Copyright (c) 1992, 1993
@@ -35,7 +35,7 @@
 .\"     @(#)boot_sparc.8	8.2 (Berkeley) 4/19/94
 .\"
 .Dd April 19, 1994
-.Dt boot_sun3 8 sun3
+.Dt BOOT_SUN3 8 sun3
 .Os
 .Sh NAME
 .Nm reboot
@@ -47,38 +47,44 @@ bootstrapping procedures
 .Op Fl n
 .Op Fl q
 .Sh DESCRIPTION
-.Sy Power fail and crash recovery.
+.Ss Power fail and crash recovery
+.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed
 as described in
 .Xr fsck 8 .
 and unless this fails, the system will resume multi-user operations.
 .Pp
-.Sy Cold starts
-A disk-boot program (/usr/mdec/ufsboot) will attempt to load
+.Ss Cold starts
+.Pp
+A disk-boot program
+.Pq Pa /usr/mdec/ufsboot
+will attempt to load
 .Pa bsd
-from partition A of the boot device,
+from partition ``a'' of the boot device,
 which must currently be an ``sd'' disk.
-Alternatively, network boot program (/usr/mdec/netboot) will load
+Alternatively, the network boot program
+.Pq Pa /usr/mdec/netboot
+will load
 .Pa bsd
 from the NFS root as determined by the procedure described in
 .Xr diskless 8 .
 .Pp
 The
-.Op Fl s
-flag to the boot loader will being the system up in single-user mode.
+.Fl s
+flag to the bootloader will bring the system up in single-user mode.
 The
-.Op Fl a
+.Fl a
 flag instructs the system to prompt for the location of the root filesystem
 and the primary swap partition.
 The
-.Op Fl d
-flag to the boot loader will bring the system up in debug mode.
+.Fl d
+flag to the bootloader will bring the system up in debug mode.
 Here it waits for a kernel debugger connect; see
 .Xr ddb 8 .
 Other flags are currently ignored.
 .Pp
-At any time you can break back to the rom by pressing the `L1' and `a'
+At any time you can break back to the ROM by pressing the `L1' and `a'
 keys at the same time (if the console is a serial port the same is
 achieved by sending a `break').
 If you do this accidentally you can continue whatever was in progress
diff --git a/sbin/reboot/boot_vax.8 b/sbin/reboot/boot_vax.8
index f7e91dc89a9..beca7f8d00d 100644
--- a/sbin/reboot/boot_vax.8
+++ b/sbin/reboot/boot_vax.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_vax.8,v 1.4 1998/07/11 22:46:14 angelos Exp $
+.\"	$OpenBSD: boot_vax.8,v 1.5 1998/09/17 04:15:01 aaron Exp $
 .\"	$NetBSD: boot_vax.8,v 1.3 1995/04/23 10:33:39 cgd Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
@@ -35,25 +35,27 @@
 .\"     @(#)boot_vax.8	8.2 (Berkeley) 4/19/94
 .\"
 .Dd April 19, 1994
-.Dt boot_vax 8 vax
+.Dt BOOT_VAX 8 vax
 .Os
 .Sh NAME
 .Nm boot
 .Nd
 system bootstrapping procedures
 .Sh DESCRIPTION
-.Sy Power fail and crash recovery.
+.Ss Power fail and crash recovery
+.Pp
 Normally, the system will reboot itself at power-up or after crashes.
-Provided the auto-restart is enabled on the machine front panel,
+Provided the auto-restart is enabled on the machine's front panel,
 an automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
-.Sy Cold starts.
+.Ss Cold starts
+.Pp
 These are processor-type dependent.
 On an 11/780, there are two floppy files for each disk controller,
 both of which cause boots from unit 0 of the root file system
 of a controller located on mba0 or uba0.
-One gives a single user shell, while the other invokes the multi-user
+One gives a single-user shell, while the other invokes the multi-user
 automatic reboot.
 Thus these files are
 .Tn HPS
@@ -124,9 +126,9 @@ The current encoding has a historical basis, and is shown in the following
 table:
 .Pp
 .Bd -unfilled -offset indent -compact
-bits	usage
-0-7	boot device type (the device major number)
-8-15	disk partition
+bits		usage
+0-7		boot device type (the device major number)
+8-15		disk partition
 16-19	drive unit
 20-23	controller number
 24-27	adaptor number (UNIBUS or MASSBUS as appropriate)
@@ -147,14 +149,14 @@ may specify
 .Li \&>>>B/ Ns Fl n No DMA0
 .Ed
 .Pp
-where, giving a
+where, giving an
 .Ar n
 of 1 causes the boot program
 to ask for the name of the system to be bootstrapped,
-giving a
+giving an
 .Ar n
-of 2 causes the boot program to come up single
-user, and a
+of 2 causes the boot program to come up single-user,
+and an
 .Ar n
 of 3 causes both of these actions to occur.
 The ``DM'' specifies RK07, the ``A'' represents the adaptor number
@@ -181,8 +183,10 @@ to autoboot or to halt.
 When halted, the processor may be booted using the same syntax
 as on the 11/750.
 .Pp
-The 11/750 boot procedure uses the boot roms to load block 0 off of
-the specified device.  The /usr/mdec directory contains a number
+The 11/750 boot procedure uses the boot ROMs to load block 0 off of
+the specified device.  The
+.Pa /usr/mdec
+directory contains a number
 of bootstrap programs for the various disks which should be placed
 in a new pack by
 .Xr disklabel 8 .
@@ -199,7 +203,7 @@ disk such
 as the RD53.
 .Pp
 On any processor, the 
-.Em boot
+.Nm boot
 program
 finds the corresponding file on the given device 
 .Pf ( Pa bsd
@@ -261,7 +265,7 @@ of unit 0 of a
 .Tn MASSBUS
 disk, type
 .Ql hp(0,0)bsd
-to the boot prompt;
+at the boot prompt;
 .Ql hp(2,0,1,0)bsd
 would specify drive 1 on
 .Tn MASSBUS
@@ -292,7 +296,7 @@ at
 .Pp
 On an 11/750 with patchable control store,
 microcode patches will be installed by
-.Em boot
+.Nm boot
 if the file
 .Pa psc750.bin
 exists in the root of the filesystem from which the system is booted.
diff --git a/sbin/reboot/boot_x68k.8 b/sbin/reboot/boot_x68k.8
index 5e3b32594d0..836f883e18e 100644
--- a/sbin/reboot/boot_x68k.8
+++ b/sbin/reboot/boot_x68k.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: boot_x68k.8,v 1.4 1996/07/10 03:52:56 ccappuc Exp $
+.\"	$OpenBSD: boot_x68k.8,v 1.5 1998/09/17 04:15:01 aaron Exp $
 .\"	$NetBSD: boot_x68k.8,v 1.1 1996/06/15 18:54:22 oki Exp $
 .\"
 .\" Copyright (c) 1980, 1991, 1993
@@ -34,7 +34,7 @@
 .\"
 .\"	@(#)boot_x68k.8	8.2 (Berkeley) 4/19/94
 .\"
-.Dd Jun 16, 1996
+.Dd June 16, 1996
 .Dt BOOT_X68K 8 x68k
 .Os
 .Sh NAME
@@ -42,40 +42,44 @@
 .Nd
 system bootstrapping procedures
 .Sh DESCRIPTION
-.Sy Power fail and crash recovery.
+.Ss Power fail and crash recovery
+.Pp
 Normally, the system will reboot itself at power-up or after crashes.
 An automatic consistency check of the file systems will be performed,
 and unless this fails, the system will resume multi-user operations.
 .Pp
-.Sy Cold starts.
+.Ss Cold starts
+.Pp
 The X68000/X68030 system boots from the device
 which is determined by the configuration of
 battery-backuped SRAM.
-By default, the boot rom attempt to boot from
+By default, the boot ROM attempts to boot from a
 floppy disk drive (from 0 to 3) first,
-and then attempt to boot from hard disk (SASI or SCSI).
-On the OpenBSD/X68k, booting from partition A of SCSI disks (sd?a) 
+and then from a hard disk (SASI or SCSI).
+On the OpenBSD/X68k, booting from partition ``a'' of SCSI disks (sd?a) 
 and 2HD floppy disks (fd?a, fd?c) is currently supported.
 .Pp
 First, the initial program loader of IOCS ROM or SCSI disk
-(or equivalent) reads
-.Pa boot
+(or equivalent) reads the
+.Nm boot
 program at the top of the disk,
-and then the boot program loads the OpenBSD kernel
+and then the
+.Nm boot
+program loads the OpenBSD kernel
 .Pa /bsd
 which is in the same partition of the disk.
-If you press
-.Pa [SHIFT]
-key when booting, the boot program enables you to change
+If you press the
+.Sq SHIFT
+key when booting, the boot program enables you to change the
 boot flag
 .Dv RB_SINGLE
 with the
-.Pa [SHIFT]
+.Sq SHIFT
 key, and to choose which kernel
 to be used with arrow keys.
-If the LED of
-.Pa [HIRAGANA]
-key is turned on, the boot program adds
+If the LED of the
+.Sq HIRAGANA
+key is turned on, the boot program adds the
 .Dv RB_KDB
 flag and tries to boot the system in debug mode; see
 .Xr ddb 8
@@ -87,9 +91,9 @@ other operating systems such as Human68k and OS-9.
 .Pp
 Note for X68030/040turbo(68040 accelerator by BEEPs) systems:
 OpenBSD can boot under 040 mode.
-It can also boot under 030 mode if you have MC68030 on the board.
+It can also boot under 030 mode if you have an MC68030 on the board.
 .Pp
-Note for X68000/Xellent30(68030 accelerator by TSR)+MC68030 systems:
+Note for X68000/Xellent30(68030 accelerator by TSR) + MC68030 systems:
 In order to boot OpenBSD, you must choose 030 mode by using
 .Pa CH30.SYS ,
 which must reside in the battery-backuped SRAM.
diff --git a/sbin/reboot/reboot.8 b/sbin/reboot/reboot.8
index 708a0caf354..02d29565974 100644
--- a/sbin/reboot/reboot.8
+++ b/sbin/reboot/reboot.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: reboot.8,v 1.9 1998/07/24 00:43:51 espie Exp $
+.\"	$OpenBSD: reboot.8,v 1.10 1998/09/17 04:15:01 aaron Exp $
 .\"	$NetBSD: reboot.8,v 1.3 1995/10/05 05:36:21 mycroft Exp $
 .\"
 .\" Copyright (c) 1990, 1991, 1993
@@ -53,42 +53,28 @@ The
 and
 .Nm reboot
 utilities flush the file system cache to disk, run the system
-shutdown script, send all running processes a SIGTERM (and
-subsequently a SIGKILL) and, respectively, halt or restart the system.
+shutdown script, send all running processes a
+.Dv SIGTERM
+.Pq and subsequently a Dv SIGKILL ,
+and, respectively, halt or restart the system.
 The action is logged, including entering a shutdown record into the login
 accounting file.
 .Pp
 The options are as follows:
 .Bl -tag -width Ds
 .It Fl d
-If the
-.Fl d
-option is specified,
-system will dump crash into swap partition.
+Causes system to create a dump before rebooting.
+This option is useful for debugging system dump procedures or
+capturing the state of a corrupted or misbehaving system.
 .It Fl n
-If the
-.Fl n
-option is specified,
-the file system cache is not flushed.
+Prevent file system cache from being flushed.
 This option should probably not be used.
 .It Fl q
-If the
-.Fl q
-option is specified,
-the system is halted or restarted quickly and ungracefully, and only
+Quick. The system is halted or restarted quickly and ungracefully, and only
 the flushing of the file system cache is performed.
 This option should probably not be used.
-.It Fl d
-If the
-.Fl d
-option is specified,
-the system will create a dump before rebooting.
-This option is useful for debugging system dump procedures or
-capturing the state of a corrupted or misbehaving system.
 .It Fl p
-The
-.Fl p
-option causes the system to power down, if it is being halted, and the
+Causes the system to power down, if it is being halted, and the
 hardware supports automatic power down.  (Currently supported on some
 i386 and sparc platforms.)
 .El
@@ -98,8 +84,9 @@ Normally, the
 utility is used when the system needs to be halted or restarted, giving
 users advance warning of their impending doom.
 .Sh FILES
-.Pa /etc/rc.shutdown
-- The script which is run at shutdown time.
+.Bl -width /etc/rc.shutdown -compact
+/etc/rc.shutdown
+script which is run at shutdown time
 .Sh SEE ALSO
 .Xr sync 8 ,
 .Xr utmp 5 ,