- section reorder

- new sentence, new line
- some macro fixes

1 files changed, 26 insertions, 24 deletions

diff --git a/sys/arch/sparc/stand/installboot/installboot.8 b/sys/arch/sparc/stand/installboot/installboot.8
index aa6fb3cacb1..2448cb74bdc 100644
--- a/sys/arch/sparc/stand/installboot/installboot.8
+++ b/sys/arch/sparc/stand/installboot/installboot.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: installboot.8,v 1.7 2003/02/07 07:45:12 jmc Exp $
+.\"	$OpenBSD: installboot.8,v 1.8 2003/06/06 21:45:33 jmc Exp $
 .\"	$NetBSD: installboot.8,v 1.1 1995/09/30 21:32:14 pk Exp $
 .\"
 .\" Copyright (c) 1995 Paul Kranenburg
@@ -51,11 +51,12 @@ is written into the superblock area in a partition
 and hence is limited in size to SBSIZE - DEV_BSIZE bytes
 .Pc ,
 and a second-stage program that resides in the filesystem proper.
-The first-stage program is loaded into memory by the PROM. After it receives
-control, it loads the second stage program from a set of filesystem block
-numbers that have been hard-coded into it by the
+The first-stage program is loaded into memory by the PROM.
+After it receives control, it loads the second stage program from a set of
+filesystem block numbers that have been hard-coded into it by the
 .Nm installboot
-program. The second-stage boot program uses the device driver interface to
+program.
+The second-stage boot program uses the device driver interface to
 the PROM and the stand-alone filesystem code in
 .Dq libsa.a
 to locate and load the kernel.
@@ -64,21 +65,21 @@ first-stage bootprogram can be found in
 .Pa /usr/mdec/boot
 and
 .Pa /usr/mdec/bootxx
-respectively. The second-stage program commonly resides in the root directory
-as
+respectively.
+The second-stage program commonly resides in the root directory as
 .Pa /boot .
 The utility
 .Pa /usr/mdec/binstall
-can be used to properly copy the second-stage bootprogram to its
-destination. This script takes care of post-processing that is required
-on
+can be used to properly copy the second-stage bootprogram to its destination.
+This script takes care of post-processing that is required on
 .Pf non- Tn Openboot
 machines.
 .Pp
 The options are as follows:
 .Bl -tag -width flag
 .It Fl a Ar karch
-Set the machine architecture. The argument
+Set the machine architecture.
+The argument
 .Ar karch
 can be one of
 .Dq sun4 ,
@@ -89,8 +90,8 @@ Sun 4c models with
 .Tn Openboot
 PROMs need the header to be present, while Sun 4 systems with the
 .Dq old monitor
-interface require the header to be stripped off. This is normally taken
-care of by
+interface require the header to be stripped off.
+This is normally taken care of by
 .Nm installboot
 automatically, but it's useful when preparing a bootable filesystem for
 another system.
@@ -99,7 +100,8 @@ Leave the
 .Xr a.out 5
 header on the installed
 .Ar bootxx
-program. This option has been superseded by the
+program.
+This option has been superseded by the
 .Fl a Ar karch
 option.
 .It Fl n
@@ -117,8 +119,8 @@ where the first-stage boot program is to be installed.
 the name of the prototype file for the first stage boot program.
 .It Ar device
 the name of the raw device in which the first-stage boot program
-is to be installed.  This should correspond to the block device
-on which the file system containing
+is to be installed.
+This should correspond to the block device on which the file system containing
 .Ar boot
 is mounted.
 .El
@@ -132,6 +134,14 @@ as the second-level boot program:
 .Bd -literal -offset indent
 installboot /boot /usr/mdec/bootxx /dev/rsd0a
 .Ed
+.Sh SEE ALSO
+.Xr disklabel 8 ,
+.Xr init 8
+.Sh HISTORY
+The
+.Nm installboot
+first appeared in
+.Nx 1.1 .
 .Sh BUGS
 .Nm installboot
 requires simultaneous access to the mounted file system and
@@ -143,11 +153,3 @@ so
 .Nm installboot
 only works in single-user mode
 .Pq or insecure mode - see Xr init 8 .
-.Sh SEE ALSO
-.Xr disklabel 8 ,
-.Xr init 8
-.Sh HISTORY
-The
-.Nm installboot
-first appeared in
-.Nx 1.1 .