From 26984c03505b20a797f46f45adeedce03d426831 Mon Sep 17 00:00:00 2001
From: stanley lieber <stanley.lieber@gmail.com>
Date: Sun, 17 Apr 2011 08:17:01 +0000
Subject: [PATCH] clean up.

---
 sys/man/8/9boot | 59 +++++++++++++++++++++++--------------------------
 1 file changed, 28 insertions(+), 31 deletions(-)

diff --git a/sys/man/8/9boot b/sys/man/8/9boot
index bb5d18e27..3ef167b2b 100644
--- a/sys/man/8/9boot
+++ b/sys/man/8/9boot
@@ -6,7 +6,7 @@ started by BIOS or chainloaded by partition bootsector
 .SH DESCRIPTION
 The bootloader is responsible for reading the
 .IR plan9.ini (8)
-boot parameters and boot a kernel. It interprets the
+boot parameters and booting a kernel. It interprets the
 .B bootfile=
 parameter as a file path on the current boot media
 to locate the kernel image. The path should be in all
@@ -15,19 +15,19 @@ lower case except for
 wich supports case sensitive file names. Read parameters
 are echoed on the console. The boot procedure
 can be interrupted by pressing any key after the configuration
-was read. Then a interactive boot console is shown with a
+was read. The interactive boot console is indicated with a
 .B >
 prompt. The syntax of the boot console is the same as in
 the
 .IR plan9.ini (8)
 file. The word
 .B clear
-will reset all current parameters and
+will reset all current parameters. The word
 .B boot
-will end the console and start booting the kernel. The boot
-console is entered automatically when boot failed, no
+will end the console and resume booting the kernel. The boot
+console is entered automatically when: boot failed, no
 .B bootfile=
-parameter is specified or no 
+parameter was specified or no 
 .IR plan9.ini (8)
 was found.
 .SH FAT BOOTING
@@ -36,42 +36,39 @@ The
 program is responsible for loading the kernel from
 the
 .IR 9fat
-partition into memory and pass it the
+partition into memory and passing it the
 .IR plan9.ini (8)
-boot parameters. It gets chainloaded by
-.IR pbs
+boot parameters. It is chainloaded by
+.IR pbs,
 wich locates it in the root of the active
-FAT partition as
-.B 9BOOTFAT
-file.
-Then
+FAT partition. The
 .B plan9.ini
-is read from the root directory of the FAT
+file is read from the root directory of the FAT
 filesystem.
-.SH CDROM BOOTING
-Booting from cdrom requires
+.SH CD-ROM BOOTING
+Booting from CD-ROM requires
 .IR 9bootiso
-to be included in the iso image under
-.B 386/9bootiso
-and also
-set as a non emulation bootblock see
-.IR mk9660 (8) .
+to be included in the ISO-9660 image under
+.B 386/9bootiso,
+set as a non emulation bootblock. See
+.IR mk9660 (8).
 The BIOS loads the first 2K of 
 .B 386/9bootiso
-into memory and passes execution to it. The program
-then reads the rest of its code from the file to chainload itself.
+into memory and then executes the program. The remainder
+of the file is then read to complete the chainloading process.
 Boot parameters are read from
-.B cfg/plan9.ini
-file.
+.B cfg/plan9.ini.
 .SH NETWORK BOOTING
-With a PXE capable BIOS and network card, it is possible for
+With a PXE capable BIOS and network card it is possible for
 a machine to download
 .IR 9bootpxe
-from a tftp server and load the kernel from there. The
+and a kernel from a tftp server. The location of
+.IR 9bootpxe
+is defined by the
 .B bootf=/386/9bootpxe
-in the machines
+line in the tftp server's
 .IR ndb (6)
-entry will tell the PXE BIOS to use it.
+entry.
 .BR
 Once started,
 .IR 9bootpxe
@@ -79,8 +76,8 @@ will read the file
 .B /cfg/pxe/$ether
 from the tftp server, where
 .B $ether
-is the mac address of the used network card
-in lower case hex, and use it as
+is the MAC address of the client's network card
+in lower case hex, and use this as its
 .IR plan9.ini (8)
 file.
 .SH SOURCE