X-Git-Url: https://git.rrq.au/?a=blobdiff_plain;f=readme%2FREADME.raid1;h=c2e19153061d3938b06a6e5f5b78c5ae710cb470;hb=6474a619fc4572914f921cbff9d72784c1792966;hp=62c57e769f024b77669b6313c58b95de6a8ab412;hpb=e05a6f05e7fce66ac7560e066d995c456073d29f;p=rrq%2Fmaintain_lilo.git

diff --git a/readme/README.raid1 b/readme/README.raid1
index 62c57e7..c2e1915 100644
--- a/readme/README.raid1
+++ b/readme/README.raid1
@@ -98,7 +98,7 @@ primary partitions will be described later.
 MORE TERMINOLOGY
 ================
 
-A boot record is "accessible", if it exists on a primary parition,
+A boot record is "accessible", if it exists on a primary partition,
 which may be marked "active"; or it is a Master Boot Record (MBR),
 written to sector 0 of a drive.
 
@@ -310,7 +310,7 @@ location is acceptable, as long as they are within the same RAID
 partition which you are making bootable.
 
 LILO variations:  version 22.2 enforces the placement of the map file
-on the RAID parition.  Version 22.3 eliminates the need for the
+on the RAID partition.  Version 22.3 eliminates the need for the
 boot.b and chain.b files, and relaxes the restriction that the
 message file be on the RAID partition by copying it into the map
 file.  Likewise, any bitmap= file is copied into the map file, so it