typos and consistency fixes;

ok miod@

4 files changed, 14 insertions, 14 deletions

diff --git a/distrib/notes/sparc64/hardware b/distrib/notes/sparc64/hardware
index f8fae4cf08c..1d0063a8ff5 100644
--- a/distrib/notes/sparc64/hardware
+++ b/distrib/notes/sparc64/hardware
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: hardware,v 1.62 2004/03/15 23:21:52 grange Exp $
+dnl	$OpenBSD: hardware,v 1.63 2004/03/16 08:25:00 jmc Exp $
 OpenBSD/MACHINE OSREV runs on the following classes of machines:
 	- SBUS based workstations:
 		Ultra 1
@@ -199,7 +199,7 @@ Supported devices {:-include-:}:
 
 Drivers for hardware marked with [A] are not included in the ramdisk.
 
-Hardware the we do NOT currently support, but get many questions about:
+Hardware that we do NOT currently support, but get many questions about:
 	Multiprocessor machines.
 	Floppy drive (except for booting).
 	SBUS and PCI cards other than those listed above.
diff --git a/distrib/notes/sparc64/install b/distrib/notes/sparc64/install
index e0d2845fe00..f977f234d4a 100644
--- a/distrib/notes/sparc64/install
+++ b/distrib/notes/sparc64/install
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: install,v 1.32 2004/02/09 13:32:52 todd Exp $
+dnl	$OpenBSD: install,v 1.33 2004/03/16 08:25:00 jmc Exp $
 OpenBSDInstallPrelude
 
 There are several ways to install OpenBSD onto a disk. The easiest way
@@ -7,11 +7,11 @@ dnl XXX change back if more than one floppy again.
 dnl cdrom, or an installation floppy.
 cdrom, or the installation floppy.
 
-If your machine is hooked up in a network and you can find a server to
+If your machine is hooked up to a network and you can find a server to
 arrange for a diskless setup, which is a convenient way to install on a
 machine whose disk does not currently hold a usable operating system.
 This is difficult to get set up correctly the first time, but easy to
-use afterwards.  (see ``Installing using a diskless setup'' below).
+use afterwards.  (See ``Installing using a diskless setup'' below.)
 
 It is also possible to install OpenBSD "manually" from a running Solaris
 system, using the system tools, as well as gunzip; see ``Installing from
@@ -83,14 +83,14 @@ which device it has been booted from.  In this case, it will ask you
 for the root and swap devices.  Answer the device and partition you
 booted from as the root partition (likely sd0b or wd0b); you might
 want to rely on the boot messages to find the correct device name
-(see below).  When the kernel asks your for the swap device, just
+(see below).  When the kernel asks you for the swap device, just
 validate the suggested device name; since the installation procedure
 does not use swap, it doesn't matter.
 
 
 Installing using a diskless setup:
 
-First, you must setup a diskless client configuration on a server. If
+First, you must set up a diskless client configuration on a server. If
 you are using a OpenBSD system as the boot-server, have a look at the
 diskless(8) manual page for guidelines on how to proceed with this.
 If the server runs another operating system, you'll have to consult
@@ -132,7 +132,7 @@ OpenBSDBootMsgs
 
 	You will next be asked for your terminal type.  If you are
 	installing from a keyboard/monitor console, the default of
-	"sun" if correct.  If you are installing from a serial console
+	"sun" is correct.  If you are installing from a serial console
 	you should choose the terminal type from amongst those listed.
 	(If your terminal type is xterm, just use vt100).
 
@@ -268,7 +268,7 @@ The GNU gunzip program is not distributed as part of Solaris, but may be
 present in your /usr/local/bin.  If not, you will need to obtain it from a
 GNU archive and install before proceeding.
 
-After the files have been extracted, setup /mnt/etc/fstab to match
+After the files have been extracted, set up /mnt/etc/fstab to match
 your actual disk layout.  (Minus the "/mnt" component of each path, of
 course :-)
 
@@ -305,7 +305,7 @@ After the boot program has been loaded into memory and given control by
 the PROM, it starts locating the machine's remote root directory through
 the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast
 on the local net. The answer to this request (if it comes in) contains
-the client's name. This name is used in next step, a BOOTPARAM GETFILE
+the client's name. This name is used in the next step, a BOOTPARAM GETFILE
 request -- sent to the server that responded to the WHOAMI request --
 requesting the name and address of the machine that will serve the client's
 root directory, as well as the path of the client's root on that server.
diff --git a/distrib/notes/sparc64/prep b/distrib/notes/sparc64/prep
index c7812a016f2..79b171f2a24 100644
--- a/distrib/notes/sparc64/prep
+++ b/distrib/notes/sparc64/prep
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: prep,v 1.14 2003/02/18 03:26:14 henric Exp $
+dnl	$OpenBSD: prep,v 1.15 2004/03/16 08:25:00 jmc Exp $
 If your UltraSPARC machine is somewhat old, it might need a firmware update
 before it can be used under OpenBSD. You are advised to try to install
 OpenBSD first; if it can't boot or fails mysteriously, you might need to
@@ -33,7 +33,7 @@ both OpenBSD and Solaris environments on the same system.
     Solaris would be confused by a filesystem with soft update flags
     enabled.
 
-The OpenBSD "Sun Compatible" disklabel have been extended to support 16
+The OpenBSD "Sun Compatible" disklabel has been extended to support 16
 partitions, which may be compatible with Solaris, but the Solaris
 format(1M) utility only sees the first 8 partitions and may "lose"
 information about the extended partitions.
diff --git a/distrib/notes/sparc64/xfer b/distrib/notes/sparc64/xfer
index d90c2a75b2f..73d48465bd8 100644
--- a/distrib/notes/sparc64/xfer
+++ b/distrib/notes/sparc64/xfer
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: xfer,v 1.19 2003/03/24 11:33:57 miod Exp $
+dnl	$OpenBSD: xfer,v 1.20 2004/03/16 08:25:00 jmc Exp $
 Installation is supported from several media types, including:
 
 	CD-ROM (NOT supported if booting from floppy)
@@ -8,7 +8,7 @@ Installation is supported from several media types, including:
 	HTTP
 
 If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you may be
-able boot from it, or from the supplied bootable CD-ROM mini image. If you
+able to boot from it, or from the supplied bootable CD-ROM mini image. If you
 can boot from the CD-ROM, you are home free and can proceed to the
 installation steps.  If not, you will need to do some setup work to prepare
 a bootable image, either a floppy, hard drive, or compatible net boot