grammar, consistency fixes, and typos;

ok miod@

4 files changed, 42 insertions, 42 deletions

diff --git a/distrib/notes/sparc/hardware b/distrib/notes/sparc/hardware
index ea6fb1da4ee..3499941eb2c 100644
--- a/distrib/notes/sparc/hardware
+++ b/distrib/notes/sparc/hardware
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: hardware,v 1.60 2004/03/16 08:25:00 jmc Exp $
+dnl	$OpenBSD: hardware,v 1.61 2004/03/17 09:25:10 jmc Exp $
 OpenBSD/MACHINE OSREV runs on the following classes of machines:
     * sun4: the VME series
 	- 4/100: Original sparc with VME. Many hardware bugs.
@@ -169,7 +169,7 @@ Supported devices {:-include-:}:
 	- PCMCIA Controllers:
 	  + Sun SBus PCMCIA bridge (stp)
 	  + Tadpole PCMCIA controller (tslot)
-	- Wireless ethernet adapters (wi)
+	- Wireless Ethernet adapters (wi)
 	  + Compact Flash Adapters (will show up as PCMCIA adapters)
 	      Buffalo AirStation CF
 	      ELSA XI800 CF
@@ -216,7 +216,7 @@ Supported devices {:-include-:}:
 	      TDK LAK-CD011WL PCMCIA
 	      US Robotics 2410 PCMCIA
 	      US Robotics 2445 PCMCIA
-	- NE2000-based ethernet Adapters
+	- NE2000-based Ethernet Adapters
 	    Accton EN2212, EN2216
 	    Allied Telesis LA-PCM
 	    AmbiCom AMB8002T
@@ -279,7 +279,7 @@ Supported devices {:-include-:}:
 OpenBSD/MACHINE OSREV does NOT run on these machines (yet):
 	- Sun 4/400
 		Lacking support for the I/O cache, and related
-		ethernet problems.
+		Ethernet problems.
 	- sun4d -- SPARCcenter 2000, SPARCserver 1000
 		XDBus and multiprocessor support issues.
 	- sun4u (Ultrasparcs)
diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install
index 23d14405be4..cd85e8e5ece 100644
--- a/distrib/notes/sparc/install
+++ b/distrib/notes/sparc/install
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: install,v 1.60 2004/03/16 08:25:00 jmc Exp $
+dnl	$OpenBSD: install,v 1.61 2004/03/17 09:25:10 jmc Exp $
 OpenBSDInstallPrelude
 
 There are several ways to install OpenBSD onto a disk. The easiest way
@@ -7,8 +7,8 @@ be booted off your local disk's swap partition. The normal way is to
 use the OpenBSD CD-ROM, or the bootable CD-ROM mini image, or an
 installation floppy, or an installation tape, depending on your hardware.
 
-If your Sparc 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
+If your Sparc is hooked up to a network, try and find a server to
+arrange for a diskless setup. This 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.)
@@ -27,13 +27,13 @@ does not necessarily wipe out all the partitions on the hard disk, errors
 during the install process can have unforeseen consequences and you will
 probably render the system unbootable if you start, but do not complete
 the installation.  Having the installation media for the prior installation,
-be it a SunOS or OpenBSD CD-ROM or OpenBSD install diskettes is good
+be it a SunOS or OpenBSD CD-ROM or OpenBSD install diskettes, is good
 insurance if you want to be able to "go back" for some reason.
 
 After taking care of all that, bring your system down gracefully using
 the shutdown(8) and/or halt(8) commands.  This will get you to the monitor
 prompt.  Sun PROM monitor commands and setup differ considerably depending
-on the system architecture and age, you may needed to reference the PROM
+on the system architecture and age; you may needed to reference the PROM
 monitor manual for your system for details.
 
 There are four main cases:
@@ -58,7 +58,7 @@ enter the "n" command to enter the "new command mode".  You can set this
 as the default by doing a "setenv sunmon-compat? false" command, followed
 by a "reset" command.
 
-Note that OpenBoot Proms also do the Sun SCSI-ID shuffle for disks, this
+Note that OpenBoot Proms also do the Sun SCSI-ID shuffle for disks; this
 is described elsewhere in some detail.  For the purposes of this section,
 drive 0 refers to the internal or first SCSI drive, which usually has a
 SCSI-ID of 3.
@@ -80,7 +80,7 @@ Booting from CD-ROM installation media:
 	ok boot cdrom OSREV/MACHINE/bsd.rd	# for version 2 OpenBOOT ROMs
 
 If the boot is successful, you will get a loader version message,
-executable sizes and then the kernel copyright and device probe
+executable sizes, and then the kernel copyright and device probe
 messages.  Boot failure modes are typically a lot of CD-ROM drive
 activity, but no messages or complaints about magic numbers,
 checksums or formats.
@@ -103,7 +103,7 @@ Boot the miniroot by typing the appropriate command at the PROM:
 
 If you've loaded the miniroot onto some other disk than the default
 drive 0, modify the boot specifier accordingly, keeping in mind the
-drive vs. scsi-id shuffling and partition a=0, b=1...
+drive vs. SCSI-ID shuffling and partition a=0, b=1...
 
         > b sd(0,10,1)bsd       # example - scsi target 2 on sun4 monitors*
 	ok boot sd(0,3,1)bsd	# example - scsi target 0 on v1 OpenBOOT ROM
@@ -127,7 +127,7 @@ Boot the miniroot by typing the appropriate command at the PROM:
 					# that won't take tape:n syntax.
 	
 The above instructions assume your tape drive is the default tape drive
-using SCSI id 4. If your drive uses id 5, modify the boot command
+using SCSI ID 4. If your drive uses ID 5, modify the boot command
 accordingly:
 
 	> b st(,28,1)		# example - 2nd tape drive on sun4 monitors
@@ -142,7 +142,7 @@ accordingly:
 Installing using a diskless setup:
 
 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
+you are using an 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
 documentation that came with it (on SunOS systems, add_client(8) and
@@ -185,7 +185,7 @@ OpenBSDBootMsgs
 	installing from a keyboard/monitor console, the default of
 	"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).
+	(If your terminal type is xterm, just use vt100.)
 
 OpenBSDInstallPart3
 
@@ -211,7 +211,7 @@ OpenBSDCommonURL
 
 After completing an installation:
 
-Now try a reboot.  (If needed, swap your scsi id's first).
+Now try a reboot.  (If needed, swap your SCSI IDs first.)
 The Sun monitor normally tries to load a file called "vmunix".
 On OpenBOOT ROM systems you can change it to load OpenBSD instead using
 the following commands:
@@ -256,7 +256,7 @@ least the following pieces:
     (e.g. sun4m or sun4c)
   - an OpenBSD kernel, most likely "/bsd"
 
-All these pieces, except "/boot" and the GNU utilities are supplied in
+All these pieces, except "/boot" and the GNU utilities, are supplied in
 the OpenBSD/MACHINE distribution.
 
 You need to format and partition the disk using SunOS (since
@@ -307,7 +307,7 @@ The installboot man page says to do something like this:
     sunos# sync; sync
     sunos# /usr/mdec/installboot -vlt /mnt/boot /usr/mdec/bootsd /dev/rsd2a
 
-You can now extract the provided "*.tgz files onto your disk.
+You can now extract the provided "*.tgz" files onto your disk.
 
     sunos# ls -FC
     base{:--:}OSrev.tgz      comp{:--:}OSrev.tgz   man{:--:}OSrev.tgz       xfont{:--:}OSrev.tgz
@@ -346,11 +346,11 @@ also need at least the following pieces:
   for ufs filesystem, such as /usr/platform/`uname -i`/lib/fs/ufs/bootblk
 - an OpenBSD kernel, most likely "/bsd"
 
-All these pieces, except the boot block and the GNU utilities are supplied
+All these pieces, except the boot block and the GNU utilities, are supplied
 in the OpenBSD/MACHINE distribution.
 
 You need to format and partition the disk using Solaris (since
-OpenBSD/MACHINE uses Sun compatible disk labels.)  Give yourself adequate
+OpenBSD/MACHINE uses Sun compatible disk labels).  Give yourself adequate
 partition sizes.  Here is an example layout:
 
     solaris# prtvtoc -s /dev/rdsk/c0t1d0s2
@@ -365,7 +365,7 @@ partition sizes.  Here is an example layout:
            6      4    00     936000   3229271   4165270   /usr
 
 Use Solaris to newfs the partitions which will have filesystems on them.
-(OpenBSD's filesystem format is almost identical to Solaris).
+(OpenBSD's filesystem format is almost identical to Solaris.)
 
     solaris# newfs /dev/rdsk/c0t1d0s0
     [... lots of output]
@@ -400,7 +400,7 @@ The installboot man page says to do something like this:
     solaris# sync; sync
     solaris# /usr/sbin/installboot /mnt/bootblk /dev/rdsk/c0t1d0s0
 
-You can now extract the provided "*.tgz files onto your disk.
+You can now extract the provided "*.tgz" files onto your disk.
 
     solaris# ls -FC
     base{:--:}OSrev.tgz      comp{:--:}OSrev.tgz   man{:--:}OSrev.tgz       xfont{:--:}OSrev.tgz
@@ -443,7 +443,7 @@ program via TFTP after having acquired its IP address through RevARP when
 instructed to boot "over the net". It will look for a filename composed of
 the machine's IP address followed by the machine's architecture, separated
 by a period. For example, a sun4c machine which has been assigned IP
-address 130.115.144.11, will make an TFTP request for `8273900B.SUN4C'.
+address 130.115.144.11, will make a TFTP request for `8273900B.SUN4C'.
 Normally, this file is a symbolic link to an appropriate second-stage
 boot program, which should be located in a place where the TFTP daemon
 can find it (remember, many TFTP daemons run in a chroot'ed environment).
@@ -485,7 +485,7 @@ kernel which is then read into memory.
 
 You will want export the miniroot{:--:}OSrev.fs filesystem to the client.  You
 can dd this filesystem image to some spare partition, mount and export
-that partition or use tar to copy the contents to a more convenient spot.
+that partition, or use tar to copy the contents to a more convenient spot.
 
 Alternatively you can build a bootable partition from the distribution sets
 as follows:
diff --git a/distrib/notes/sparc/prep b/distrib/notes/sparc/prep
index 22082584e99..a94fdb3287a 100644
--- a/distrib/notes/sparc/prep
+++ b/distrib/notes/sparc/prep
@@ -15,24 +15,24 @@ this table:
     6		sd6
 
 Unlike SunOS and the OpenBOOT ROM, a generic OpenBSD kernel numbers
-scsi drives sequentially as it finds them.  The drive with the
-lowest scsi-id will be called sd0, the next one sd1, etc.
+SCSI drives sequentially as it finds them.  The drive with the
+lowest SCSI-ID will be called sd0, the next one sd1, etc.
 
 To ease the installation process, two OpenBSD kernels are provided in
 the installation sets.  The default OpenBSD kernel (bsd) is set up
 to use the OpenBSD mapping, while a special kernel (bsd.scsi3) is
-set up to match the Sun mapping above by hard-wiring scsi-id#3 to sd0
-and scsi-id#0 to sd3. The remaining drives will be dynamically mapped
+set up to match the Sun mapping above by hard-wiring SCSI-ID#3 to sd0
+and SCSI-ID#0 to sd3. The remaining drives will be dynamically mapped
 to other sd* numbers.
 
 This is mostly a non-issue if you have only one drive on your system,
 but can get confusing if you have multiple drives.  If you plan
-to eliminate SunOS altogether it may be best to correct the scsi-id's
+to eliminate SunOS altogether it may be best to correct the SCSI-IDs
 of your drives, while if you plan to leave SunOS installed, it may
-be better to install OpenBSD on a drive with scsi-id 1 or 0.
+be better to install OpenBSD on a drive with SCSI-ID 1 or 0.
 
 Older OpenBoot proms (versions 1.x) provide an environment variable,
-sd-targets, that controls the drive<->scsi-id mapping, you can change
+sd-targets, that controls the drive<->SCSI-ID mapping; you can change
 this to reflect the natural ordering or just set the boot related
 variables to boot from the correct drive, whatever the numbering. Its
 default-value is ``31204567'', which means unit 0 and 3 are exchanged.
@@ -41,7 +41,7 @@ To revert to the ``normal'' behaviour, enter the following command:
     ok setenv sd-targets 01234567
 
 NOTE: if you elect to build a custom kernel you may want to "hardwire"
-the scsi-id's to sd0->scsi-id 0 or your desired scheme, this helps
+the SCSI-IDs to sd0->SCSI-ID 0 or your desired scheme, this helps
 prevent accidents if you change the SCSI bus configuration or a drive
 is down.
 
@@ -68,7 +68,7 @@ Make sure that the ROM security modes are disabled:
 
 
 Please note that while OpenBSD and SunOS have a reasonable degree of
-compatibility between disk labels and filesystems there are some problems
+compatibility between disk labels and filesystems, there are some problems
 to watch out for during initial installation or when trying to maintain
 both OpenBSD and SunOS environments on the same system.
 
@@ -100,7 +100,7 @@ OpenBSD partitions.
 
 OpenBSD and Sun BSD bootblocks are similar in concept, though implemented
 differently.  The OpenBSD bootblocks are architecture independent and also
-understand the extended disklabels with 16 partitions.  You can use SunOS
+understand the extended disk labels with 16 partitions.  You can use SunOS
 bootblocks, but remember that OpenBSD bootblocks must be installed with
 OpenBSD installboot and SunOS bootblocks with SunOS installboot.
 
diff --git a/distrib/notes/sparc/xfer b/distrib/notes/sparc/xfer
index 1591dae6204..ab2e8a2e9f0 100644
--- a/distrib/notes/sparc/xfer
+++ b/distrib/notes/sparc/xfer
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: xfer,v 1.37 2004/03/16 08:25:00 jmc Exp $
+dnl	$OpenBSD: xfer,v 1.38 2004/03/17 09:25:10 jmc Exp $
 Installation is supported from several media types, including:
 
 	CD-ROM
@@ -16,7 +16,7 @@ not all sparc systems support booting from CD-ROM, and the current boot
 image is only known to work on sun4c and sun4m architecture workstations.
 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, tape, or compatible net boot
+a bootable image: either a floppy, hard drive, tape, or compatible net boot
 server.
 
 In addition to the bootable image, you also need to consider how to
@@ -42,11 +42,11 @@ Creating a bootable hard disk using SunOS, Solaris or other Un*x-like system:
 	single user mode), and then booting from that partition.
 
 	Using the "b" partition allows you to boot without overwriting
-	any useful parts of the disk, you can also use another partition,
+	any useful parts of the disk; you can also use another partition,
 	but don't use the "a" or "c" partition without understanding
-	the disklabel issues described below under "incompatible systems".
+	the disk label issues described below under "incompatible systems".
 
-	This requires that you be running SunOS, Solaris, OpenBSD or NetBSD
+	This requires that you be running SunOS, Solaris, OpenBSD, or NetBSD,
 	which have a compatible view of SunOS disk labels and partitions.
 
 	Use the dd(1) utility to copy the file to the hard drive.
@@ -68,9 +68,9 @@ Creating a bootable hard disk using SunOS, Solaris or other Un*x-like system:
 	don't care about the hard disk contents, you can also install the
 	bootable image starting at the beginning of the disk. This lets
 	you prepare a bootable hard-drive even if don't have a working
-	operating system on your Sparc, but it important to understand
+	operating system on your Sparc, but it is important to understand
 	that the bootable image installed this way includes a "disk label"
-	which can wipe out any pre-existing disklabels or partitioning for
+	which can wipe out any pre-existing disk labels or partitioning for
 	the drive.
 
 	The floppy image is used only for booting, and can be placed in
@@ -115,7 +115,7 @@ Creating a bootable hard disk using SunOS, Solaris or other Un*x-like system:
 		dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=36b
 		dd if=/tmp/label of=/dev/rsdXc bs=1b count=1
 
-	In either case, you've created a situation where the disklabel
+	In either case, you've created a situation where the disk label
 	and the filesystem information don't agree about the partition
 	size and geometry, however the results will be usable.