Added partition type codes; new verification check.
diff --git a/fixparts.8 b/fixparts.8
index 0359bc4..a36f1a1 100644
--- a/fixparts.8
+++ b/fixparts.8
@@ -39,13 +39,13 @@
Additional features include the ability to change partition type codes or
boot/active flags, to delete partitions, and to recompute CHS values. With
the possible exception of recomputing CHS values, these secondary features
-are better performed with \fBfdisk\fR, because \fBfixpart\fR's design means
+are better performed with \fBfdisk\fR, because \fBfixparts\fR' design means
that it's likely to alter partition numbering even when such changes are
not requested.
-The \fBfixpart\fR program employs a user interface similar to that of
-Linux's \fBfdisk\fR, but \fBfixpart\fR is much more specialized. Most
-importantly, you can't create new partitions with \fBfixpart\fR, although
+The \fBfixparts\fR program employs a user interface similar to that of
+Linux's \fBfdisk\fR, but \fBfixparts\fR is much more specialized. Most
+importantly, you can't create new partitions with \fBfixparts\fR, although
you can change primary/logical assignment.
In the MBR scheme, partitions come in three varieties:
@@ -64,10 +64,10 @@
.TP
.B logical
A disk can contain an arbitrary number of logical partitions
-(\fBfixpart\fR, however, imposes a limit of 124 logical partitions). All
+(\fBfixparts\fR, however, imposes a limit of 124 logical partitions). All
the logical partitions reside inside a single extended partition, and are
defined using a linked-list data structure. This fact means that every
-logical partition be preceded by at least one sector of unallocated space
+logical partition must be preceded by at least one sector of unallocated space
to hold its defining data structure (an Extended Boot Record, or EBR).
.PP
@@ -81,7 +81,7 @@
partition within an extended partition (which is just a specific type of
primary partition).
-Unlike most disk utilities, \fBfixpart\fR's user interface ignores extended
+Unlike most disk utilities, \fBfixparts\fR' user interface ignores extended
partitions. Internally, the program discards the information on the
original extended partition and, when you tell it to save its changes, it
generates a new extended partition to contain the then-defined logical
@@ -89,19 +89,19 @@
tool performs require generating a fresh extended partition, so keeping the
original in the user interface would only be a complication.
-Another unusual feature of \fBfixpart\fR's user interface is that partition
+Another unusual feature of \fBfixparts\fR' user interface is that partition
numbers do not necessarily correlate with primary/logical status. In most
utilities, partitions 1\-4 correspond to primary partitions, whereas
-partitions 5 and up are logical partitions. In \fBfixpart\fR, any partition
+partitions 5 and up are logical partitions. In \fBfixparts\fR, any partition
number may be assigned primary or logical status, so long as the rules for
layout described earlier are obeyed. When the partition table is saved,
partitions will be assigned appropriately and then tools such as the Linux
kernel and \fBfdisk\fR will give them conventional numbers.
-When it first starts, \fBfixpart\fR performs a scan for GPT data. If the
-disk looks like a conventional GPT disk, \fBfixpart\fR refuses to run. If
+When it first starts, \fBfixparts\fR performs a scan for GPT data. If the
+disk looks like a conventional GPT disk, \fBfixparts\fR refuses to run. If
the disk appears to be a conventional MBR disk but GPT signatures are
-present in the GPT primary or secondary header areas, \fBfixpart\fR
+present in the GPT primary or secondary header areas, \fBfixparts\fR
offers to delete this extraneous data. If you tell it to do so, the program
immediately wipes the GPT header or headers. (If only one header was found,
only that one header will be erased, to minimize the risk of damaging a
@@ -109,7 +109,7 @@
headers.)
With the exception of optionally erasing leftover GPT data when it first
-starts, \fBfixpart\fR keeps all changes in memory until the user writes
+starts, \fBfixparts\fR keeps all changes in memory until the user writes
changes with the \fBw\fR command. Thus, you can adjust your partitions in
the user interface and abort those changes by typing \fBq\fR to quit
without saving changes.
@@ -147,7 +147,7 @@
.TP
.B o
Omit a partition. Once omitted, the partition will still appear in the
-\fBfixpart\fR partition list, but it will be flagged as omitted. You can
+\fBfixparts\fR partition list, but it will be flagged as omitted. You can
subsequently convert it to primary or logical form with the \fBr\fR or
\fBl\fR commands, respectively. When you save your changes with \fBw\fR,
though, the partition will be lost.