5 files changed, 19 insertions, 19 deletions
diff --git a/distrib/notes/atari/contents b/distrib/notes/atari/contents
index 3c6790b6169..e26179314ee 100644
--- a/distrib/notes/atari/contents
+++ b/distrib/notes/atari/contents
@@ -27,7 +27,7 @@ Bootable Kernel floppy:
 
 	This TOS disk contains the loadbsd and chg_part programs
 	and the GENERIC kernel.  It is setup so that you can insert it
-	int your floppy drive, and start the programs from GEM.
+	into your floppy drive, and start the programs from GEM.
 
 	This floppy is named boot-22.fs
 
diff --git a/distrib/notes/atari/hardware b/distrib/notes/atari/hardware
index 86c5d6968df..0d9209cac90 100644
--- a/distrib/notes/atari/hardware
+++ b/distrib/notes/atari/hardware
@@ -16,7 +16,7 @@ large and bulky to accommodate all people, BOOT is small and might
 not have all the features you want).
 
 Supported devices include:
-	- The buildin SCSI host adapter
+	- The built-in SCSI host adapter
 		- Should support most SCSI-drives. The drives that are
 		  currently tested are:
 			MAXTOR 7245S, MAXTOR 7080S, SEAGATE ST157N
diff --git a/distrib/notes/atari/install b/distrib/notes/atari/install
index eb1c8089e65..3112ecb1a52 100644
--- a/distrib/notes/atari/install
+++ b/distrib/notes/atari/install
@@ -30,8 +30,8 @@ begin again from scratch.
 	kernel to load the install filesystem into RAMdisk. While
 	While the kernel is loading, it will show a '.' for each
 	track loaded. After loading 80 tracks, it will ask you
-	to insert the next floppy. At this time, inser the BSD
-	install floppy 2 and hit any key. The kernel continous
+	to insert the next floppy. At this time, insert the BSD
+	install floppy 2 and hit any key. The kernel continuous
 	loading another 40 tracks before it continues to boot.
 
 	The system should continue to boot.  For now ignore WARNING:
@@ -128,7 +128,7 @@ begin again from scratch.
 			Extract game20
 
 		If the distribution sets are in different directories,
-		you will need to cd to each directory in turn, runing
+		you will need to cd to each directory in turn, running
 		"Set_tmp_dir" and the appropriate "Extract" command(s).
 
 		Continue this process until you've finished installing
@@ -225,7 +225,7 @@ boot OpenBSD this time with the command:
 
 	loadbsd bsd
 
-You need to do your final tweeks now.  First mount your file systems
+You need to do your final tweaks now.  First mount your file systems
 like so:
 
 	mount -av
@@ -251,7 +251,7 @@ you could do the following:
 	into this partition. Also, edit your /etc/fstab to always
 	mount this partition, say as /kernels. Now make a symlink
 	from /bsd to /kernels/bsd.
-	This sceme is particulary handy when you want to make your
+	This scheme is particularly handy when you want to make your
 	own kernel. When compilation is finished, you just copy
 	your kernel to /kernels/bsd and reboot. It's wise to
 	make sure there is _always_ a 'know to work' kernel image
diff --git a/distrib/notes/atari/prep b/distrib/notes/atari/prep
index 2aa186071ad..80705768931 100644
--- a/distrib/notes/atari/prep
+++ b/distrib/notes/atari/prep
@@ -19,14 +19,14 @@ OpenBSD/atari system.  How this should be done is described in
 "upgrading to OpenBSD-labeling".
 
 Using AHDI partitioning:
-	The paritioning can be done with the AHDI-disk that is
-	provided with your TT or Falcon. Note that the AHDI partioning
-	function erases all partions on your harddisk even if they are
+	The partitioning can be done with the AHDI-disk that is
+	provided with your TT or Falcon. Note that the AHDI partitioning
+	function erases all partitions on your hard disk even if they are
 	not changed!
 	I know this is rather stupid, but don't say I didn't warn you.
 
-	You will need the 'chg_part' program from the bootdisk to
-	prepare your harddisk a bit more. This program will change the
+	You will need the 'chg_part' program from the boot disk to
+	prepare your hard disk a bit more. This program will change the
 	partition-id so OpenBSD knows which partitions it can use. The
 	synopsis is:
 		chg_part <driveno> <partno> <new_id>
@@ -49,12 +49,12 @@ Using AHDI partitioning:
 
 Upgrading to OpenBSD-labeling:
 	First of all the new disk label functions are fully backwards
-	compatible with the current (old) behaviour, therefore you don't
+	compatible with the current (old) behavior, therefore you don't
 	have to rename partition identifiers if you don't want to. The only
 	limitation is that you won't be able to write a disklabel to your
 	harddisk ("Device not configured.").
 
-	If you'ld like to have the flexibility of the OpenBSD disk label,
+	If you'd like to have the flexibility of the OpenBSD disk label,
 	the procedure is very simple: change the identifier of the AHDI
 	partition that contains your OpenBSD root filesystem from NBR to NBD.
 	Boot OpenBSD; run `disklabel -e sd?'; disklabel will start vi;
@@ -91,7 +91,7 @@ Upgrading to OpenBSD-labeling:
 	So what do you do if you have a new disk, that will be exclusively
 	used by OpenBSD? Very simple: don't let it get `infected' by the
 	AHDI `virus'. ,-) Just connect the disk to your TT/Falcon; boot
-	OpenBSD; run `disklabel -e'; you'll see only one large partiton `d'
-	(there won't be any filesytem on it yet); you can create partitions
+	OpenBSD; run `disklabel -e'; you'll see only one large partition `d'
+	(there won't be any filesystem on it yet); you can create partitions
 	in any way you want, as you're no longer limited by an AHDI partition
 	table.
diff --git a/distrib/notes/atari/xfer b/distrib/notes/atari/xfer
index d1d9b8b16f6..4d386a35459 100644
--- a/distrib/notes/atari/xfer
+++ b/distrib/notes/atari/xfer
@@ -14,12 +14,12 @@ the disk. To write onto fd0 use:
 
 	dd if=inst-10.fs.1 of=/dev/rfd0b bs=9b
 
-If you are using TOS to make the floppies, grab the 'rawwrite' utility
+If you are using TOS to make the floppies, grab the 'rawrite' utility
 from the "atari/utils" directory and issue the command:
-	rawwrite boot-10.fs
+	rawrite boot-10.fs
 
 This will create the boot-floppy on the floppy in drive a. The floppies
-should be pre-formatted on 720Kb for both the 'dd' and 'rawwrite' commands
+should be pre-formatted on 720Kb for both the 'dd' and 'rawrite' commands
 to work. Pre-formatting can be best done using the desktop format command.
 Some other utilities seem to be giving problems.