summaryrefslogtreecommitdiff
path: root/distrib/notes/hp300/prep
diff options
context:
space:
mode:
Diffstat (limited to 'distrib/notes/hp300/prep')
-rw-r--r--distrib/notes/hp300/prep6
1 files changed, 3 insertions, 3 deletions
diff --git a/distrib/notes/hp300/prep b/distrib/notes/hp300/prep
index ddbd0bc580b..f0798fbe6e8 100644
--- a/distrib/notes/hp300/prep
+++ b/distrib/notes/hp300/prep
@@ -1,12 +1,12 @@
The ramdisk kernel may be loaded from the network, from CD-ROM, or other
SCSI devices (such as Zip(tm) disk). This section primarily describes the
-setup required for a network boot, but does offer information pretaining to
+setup required for a network boot, but does offer information pertaining to
installation from other media. Note that loading from HPIB or SCSI cartridge
tape is possible, but not currently supported.
You will need information about your disk's geometry, based on 512-byte
sectors. You must have this information before proceeding. The
-file `HP-IB.geometry' has geometry inforomation for several HP-IB disks,
+file `HP-IB.geometry' has geometry information for several HP-IB disks,
but may be incomplete. Geometry may be calculated from an HP-UX
`/etc/disktab' entry, but note that HP-UX geometry is based on
1024 byte sectors, while OpenBSD's is based on 512 byte sectors.
@@ -31,7 +31,7 @@ In order to complete this process, you will need the following from the
SYS_UBOOT The unified boot block file.
- bsd.rd The gziped RAMDISK kernel image.
+ bsd.rd The gzipped RAMDISK kernel image.
To boot SYS_UBOOT via the network, you will need a system capable of
handling boot requests for an hp300. If you will use this method, see