parted: typos

[Ralf Wildenhues]

Hello Leslie,

Here's some typos and en_UK to en_US spelling changes for the manual of
GNU parted and a couple more files I glanced over, against SVN trunk.

Cheers,
Ralf

        * doc/C/partprobe.8, doc/C/parted.8, doc/parted.texi,
        doc/API, doc/FAT: Fix some typos.

Index: doc/C/partprobe.8
===================================================================
--- doc/C/partprobe.8   (revision 805)
+++ doc/C/partprobe.8   (working copy)
@@ -28,7 +28,7 @@
 command.
 .PP
 .\" TeX users may be more comfortable with the \fB<whatever>\fP and
-.\" \fI<whatever>\fP escape sequences to invode bold face and italics, 
+.\" \fI<whatever>\fP escape sequences to invoke bold face and italics, 
 .\" respectively.
 \fBpartprobe\fP is a program that informs the operating system kernel of
 partition table changes, by requesting that the operating system re-read
Index: doc/C/parted.8
===================================================================
--- doc/C/parted.8      (revision 805)
+++ doc/C/parted.8      (working copy)
@@ -15,7 +15,7 @@
 create, destroy, resize, move and copy ext2, ext3, linux-swap, FAT, FAT32, and 
reiserfs
 partitions.  It can create, resize and move Macintosh HFS partitions, as well 
as detect jfs, 
 ntfs, ufs, and xfs partitions.  It is useful for creating space for new 
operating systems,
-reorganising disk usage, and copying data to new hard disks.
+reorganizing disk usage, and copying data to new hard disks.
 .SH OPTIONS
 .TP
 .B -h, --help
Index: doc/parted.texi
===================================================================
--- doc/parted.texi     (revision 805)
+++ doc/parted.texi     (working copy)
@@ -130,7 +130,7 @@
 be bugs in GNU Parted, so you should back up your important files before
 running Parted.
 Also note that reiserfs support relies on libreiserfs, which does not
-fulfil the aforementioned requirement.  The same holds for any external
+fulfill the aforementioned requirement.  The same holds for any external
 tools like @kbd{ntfsresize}.
 
 The GNU Parted homepage is @uref{http://www.gnu.org/software/parted}.  The
@@ -190,7 +190,7 @@
 option for @command{configure}.
 
 @item GNU gettext (or compatible software) for compilation, if
-internationalisation support is desired.
+internationalization support is desired.
 
        @uref{ftp://ftp.gnu.org/gnu/gettext}
 
@@ -860,7 +860,7 @@
 Rescue a lost partition that used to be located approximately between
 @var{start} and @var{end}.  If such a partition is found, Parted will
 ask you if you want to create a partition for it.  This is useful if you
-accidently deleted a partition with parted's rm command, for example.
+accidentally deleted a partition with parted's rm command, for example.
 
 Example:
 
@@ -951,7 +951,7 @@
 
 @deffn Command rm @var{number}
 
-Removes the partition with number @var{number}.  If you accidently delete
+Removes the partition with number @var{number}.  If you accidentally delete
 a partition with this command, use mkpart (@emph{not} mkpartfs) to
 recover it.  Also, you can use the gpart program (@pxref{Related information})
 to recover damaged disk labels.
@@ -1116,7 +1116,7 @@
 wrote that satisfies constraints from both the operation, the
 filesystem being worked on, the disk label, other partitions and so
 on.  Use the sector unit ``s'' to specify exact locations (if they
-do not satisfy all onstraints, Parted will ask you for the nearest 
+do not satisfy all constraints, Parted will ask you for the nearest 
 solution).  Note that negative numbers count back from the end of
 the disk, with ``-1s'' pointing to the end of the disk.  
 
@@ -1179,7 +1179,7 @@
 
 @item @kbd{COPYING} - the GNU General Public License, the terms under which 
GNU Parted may be distributed.
 
address@hidden @kbd{COPYING.DOC} - the GNU Free Documentation Licence, the term 
under
address@hidden @kbd{COPYING.DOC} - the GNU Free Documentation License, the term 
under
 which Parted's documentation may be distributed.
 
 @item @kbd{INSTALL} --- how to compile and install Parted, and most other free
@@ -1206,7 +1206,7 @@
 
 Initial Texinfo formatting by Richard M. Kreuter, 2002.
 
-Maintainance by Andrew Clausen from 2002 to 2005 and by Leslie P. Polzer
+Maintenance by Andrew Clausen from 2002 to 2005 and by Leslie P. Polzer
 from July 2005 onwards.
 
 This manual is distributed under the GNU Free Documentation License,
Index: doc/API
===================================================================
--- doc/API     (revision 805)
+++ doc/API     (working copy)
@@ -39,7 +39,7 @@
 --------
 
 1      Introduction
-2      Initialising libparted
+2      Initializing libparted
 3      PedDevice
 4      PedDisk, PedDiskType
 5      PedGeometry
@@ -59,7 +59,7 @@
 the filesystems on them.
 
 The main motivation for separating the back-end into a separate library was
-to encourage different GNU/Linux distributions to encorporate their own
+to encourage different GNU/Linux distributions to incorporate their own
 customized front-end into the install process.
 
 This documents the API -- not the implementation details of libparted.
@@ -92,7 +92,7 @@
 FILE SYSTEM            any data that resides on a partition.  For the purposes
                        for GNU Parted, this includes swap devices.
 
-GEOMETRY               a description of a continuous region on a disk.  eg,
+GEOMETRY               a description of a continuous region on a disk, e.g.,
                        partitions have a geometry.
 
 HIDDEN PARTITION       a partition that is hidden from MS operating systems.
@@ -120,7 +120,7 @@
 --------------
 libparted has a fairly object-oriented design.  The most important objects are:
 
-PedArchitecture                describes support for an "archicture", which is 
sort
+PedArchitecture                describes support for an "architecture", which 
is sort
                        of like "operating system", but could also be,
                        for example, another libparted environment, EVMS, etc.
 PedConstraint          a constraint on the geometry of a partition
@@ -128,7 +128,7 @@
 PedDisk                        a device + partition table
 PedFileSystem          a filesystem, associated with a PedGeometry, NOT a
                        PedPartition.
-PedGeometry            a continious region on a device
+PedGeometry            a continuous region on a device
 PedPartition           a partition (basically PedGeometry plus some attributes)
 PedTimer               a timer keeps track of progress and time
 
@@ -141,14 +141,14 @@
 calls to libparted's API.
 
 -------------------------------------------------------------------------------
-2      INITIALISING LIBPARTED
+2      INITIALIZING LIBPARTED
 -------------------------------------------------------------------------------
 
 Headers for libparted can be included with:
 
 #include <parted/parted.h>
 
-Parted automatically initialises itself via an __attribute__ ((constructor))
+Parted automatically initializes itself via an __attribute__ ((constructor))
 function.
 
 However, you might want to set the exception handler with
@@ -228,7 +228,7 @@
 For example, logical partitions on msdos disk labels usually have a constraint
 with offset = 63 and grain_size = 16065 (Long story!).  An important
 (and non-obvious!) property of alignment restrictions is they are closed
-under intersection,  i.e. if you take two constraints, like (offset, 
grain_size)
+under intersection, i.e., if you take two constraints, like (offset, 
grain_size)
 = (63, 16065) and (0, 4), then either:
   * there are no valid solutions
   * all solutions can be expressed in the form of (offset + X * grain_size)
@@ -238,7 +238,7 @@
 containing proofs above ped_alignment_intersect() in libparted/natmath.c
 
 The restrictions on the location of the start and end are in the form of 
-PedGeometry objects -- continous regions in which the start and end must lie.
+PedGeometry objects -- continuous regions in which the start and end must lie.
 Obviously, these restrictions are also closed under intersection.
 
 The other restriction -- the minimum size -- is also closed under intersection.
Index: doc/FAT
===================================================================
--- doc/FAT     (revision 805)
+++ doc/FAT     (working copy)
@@ -59,7 +59,7 @@
 different programs, documentation from about 20 different sources and testing.
 There are many cases where documentation for FAT from various sources
 (including Microsoft) are misleading, or just plain wrong.  For us,
-documentation is correct if it matches the behaviour of Microsoft's
+documentation is correct if it matches the behavior of Microsoft's
 implementation.
 
 
@@ -112,7 +112,7 @@
 - whether it's FAT12, FAT16 or FAT32, how big it is, etc.  It also contains
 the boot loader for the operating system, if there is an operating system
 on the file system.  It is always the first thing to appear in the filesystem
-- i.e. it's found at sector 0.
+- i.e., it's found at sector 0.
 
 A word of warning: while the values inside the boot sector will always be
 consistent with the file system, many of these values are not read by
@@ -193,7 +193,7 @@
 
 
        __u8    system_id[8];   /* 03: system name */
-This contains the name of the program or operatings system that created the
+This contains the name of the program or operating system that created the
 file system.  For FAT32, it seems you must have "MSWIN4.1" here.
 If this is "MSDMF3.2" (afaik only the "MSDMF" is checked") the partition
 can't be written under Windows 9x, Windows NT and Windows 2000.  This is
@@ -214,7 +214,7 @@
 
 
        __u16   reserved;       /* 0e: reserved sectors */
-The number of sectors before the file allocation tables begin.  i.e. The
+The number of sectors before the file allocation tables begin, i.e., the
 number of the first sector of the first file allocation table.
 
 
@@ -225,7 +225,7 @@
        __u16   dir_entries;    /* 11: number of root directory entries */
 The size of the root directory (FAT12 and FAT16 only), in "directory entries"
 (32 bytes).  The root directory is immediately after the FATs (FAT12 and
-FAT16 only).  The first cluster (i.e. cluster number 2) starts immediately
+FAT16 only).  The first cluster (i.e., cluster number 2) starts immediately
 after the root directory (or after the FATs for FAT32).
 
 
@@ -256,7 +256,7 @@
 
        __u32   hidden;         /* 1c: hidden sectors (partition start) */
 On a hard disk, this should be the number of sectors from the start of the
-head (in terms of BIOS geometry) to the start of the partition.  i.e. the
+head (in terms of BIOS geometry) to the start of the partition, i.e., the
 S in the CHS partition start.
 
 
@@ -316,7 +316,7 @@
 
 
         __u16   backup_sector;  /* 32: */
-The number of the backup of the boot sector (i.e. this sector).
+The number of the backup of the boot sector (i.e., this sector).
 
 
         __u16   drive_num;      /* 40: */
@@ -518,7 +518,7 @@
 
 File allocation table (FAT) is a strange name, come to think of it.  Perhaps it
 should be called cluster allocation table, or something (?).  Essentially,
-it is used to represent file chains (i.e. linked lists) for files and
+it is used to represent file chains (i.e., linked lists) for files and
 directories.  There are usually two FATs (one is a backup, and should be
 identical). 
 
@@ -528,9 +528,9 @@
 The first byte of each FAT must match the "media" field in the boot sector.
 The rest of the first 2 entries are filled with 0xff.
 
-All remaining entries - from 2 onwards - correspond to a cluster.  i.e.
+All remaining entries - from 2 onwards - correspond to a cluster, i.e.,
 the second entry corresponds to cluster 2.  Clusters are numbered from 2 
onwards
-(i.e. there is no cluster 1).
+(i.e., there is no cluster 1).
 
 The number in each entry gives the number of the cluster that occurs next in
 the file chain (linked list).  However, there are a few magic numbers:
@@ -615,7 +615,7 @@
 
 
         __u8            is_upper_case_name;
-A Microsoft cludge: create a file with 8.3 name BUT containing small letters
+A Microsoft kludge: create a file with 8.3 name BUT containing small letters
 (like ReadMe.Txt) which is treated as an LFN (long file name) and occupies
 three directory entries.  Now when you rename this file to all uppercase
 README.TXT,- under Windows NT 4 the then superfluous LFN-VFAT entries are
@@ -675,7 +675,7 @@
 boot sector), so that the clusters that are common to the old and new
 partition can be preserved.
   * re-number clusters.  e.g. if you chop out some clusters from the beginning
-(i.e. move the start forward), then the first cluster (i.e. number 2) will
+(i.e., move the start forward), then the first cluster (i.e., number 2) will
 be refer to a different cluster on the disk.  The directory tree and FATs must
 be updated to reflect this.
   * create a new boot sector (and the info sector and backup boot sector for