Subject: Quick spell-check against all the documentation
Author: Matteo Cypriani <mcy@lm7.fr>
Bug-Debian: http://bugs.debian.org/395428
Bug-Debian: http://bugs.debian.org/525257
Last-Update: 2021-01-30
--- a/doc/fdmount.1
+++ b/doc/fdmount.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
@@ -258,7 +258,7 @@
 .TP
 \&\fR\&\f(CWerror\ reading\ boot/super\ block\fR\ 
 fdmount failed to read the first 1K of the disk. The disk might be
-damaged, unformatted, or it may have a format wich is unsupported by the
+damaged, unformatted, or it may have a format which is unsupported by the
 FDC or the Linux kernel.
 .TP
 \&\fR\&\f(CWunknown\ filesystem\ type\fR\ 
--- a/doc/fdmount.texi
+++ b/doc/fdmount.texi
@@ -183,7 +183,7 @@
 
 @item error reading boot/super block
 fdmount failed to read the first 1K of the disk. The disk might be
-damaged, unformatted, or it may have a format wich is unsupported by the
+damaged, unformatted, or it may have a format which is unsupported by the
 FDC or the Linux kernel.
 
 @item unknown filesystem type
--- a/doc/fdrawcmd.1
+++ b/doc/fdrawcmd.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
@@ -262,7 +262,7 @@
 enables/disables ISO formats. Odd values of
 \&\fIiso\fR
 enable these formats, whereas even values disable them. ISO formats
-don't have index headers, and thus allow to fit slightly more data on
+don't have index headers, and thus allow one to fit slightly more data on
 a disk.
 .TP
 \&\fR\&\f(CWsave\fR\ 
@@ -280,7 +280,7 @@
 chooses rate tables for various drives. Each dspec byte describes one
 drive. Bits 0 and 1 say which drive is described. Bits 2 and 3 describe
 the rate table. Only tables 0 and 2 are interesting. Both tables only
-differ in the meaning og rate 1. For table 0 (the default) rate 0 is 300
+differ in the meaning of rate 1. For table 0 (the default) rate 0 is 300
 kb/s (used for 5 1/4 DD disks), whereas for table 1 it is 2 Mbps (used
 for fast floppy tape drives). Bit 4 is the precompensation table select
 bit. It should be set to 0. Bit 5-7 should be zero as well. The
--- a/doc/fdrawcmd.texi
+++ b/doc/fdrawcmd.texi
@@ -191,7 +191,7 @@
 enables/disables ISO formats. Odd values of
 @var{iso}
 enable these formats, whereas even values disable them. ISO formats
-don't have index headers, and thus allow to fit slightly more data on
+don't have index headers, and thus allow one to fit slightly more data on
 a disk.
 
 @item save
@@ -209,7 +209,7 @@
 chooses rate tables for various drives. Each dspec byte describes one
 drive. Bits 0 and 1 say which drive is described. Bits 2 and 3 describe
 the rate table. Only tables 0 and 2 are interesting. Both tables only
-differ in the meaning og rate 1. For table 0 (the default) rate 0 is 300
+differ in the meaning of rate 1. For table 0 (the default) rate 0 is 300
 kb/s (used for 5 1/4 DD disks), whereas for table 1 it is 2 Mbps (used
 for fast floppy tape drives). Bit 4 is the precompensation table select
 bit. It should be set to 0. Bit 5-7 should be zero as well. The
--- a/doc/floppycontrol.texi
+++ b/doc/floppycontrol.texi
@@ -112,7 +112,7 @@
 is E for 3.5 ED drives, H for 3.5 HD drives, D for 3.5 DD drives, h for
 5.25 HD drives and d for 5.25 DD drives. The drive type letter
 corresponds to the oldest drive type supporting the format of this
-device node (not necessarily the type of the drive refered by this
+device node (not necessarily the type of the drive referred by this
 node.)  For the generic format nodes (/dev/fd0 et al.)  the name of
 "native format" of the drive is printed, and for the default formats, if
 a generic format has been redefined, its name becomes @code{(null)}.
@@ -142,7 +142,7 @@
 completed.
 
 @item probed_fmt
-is the the index of the autodetected format in the autodetection
+is the index of the autodetected format in the autodetection
 sequence for this drive.
 
 @item cylinder
--- a/doc/floppycontrol.1
+++ b/doc/floppycontrol.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
@@ -175,7 +175,7 @@
 is E for 3.5 ED drives, H for 3.5 HD drives, D for 3.5 DD drives, h for
 5.25 HD drives and d for 5.25 DD drives. The drive type letter
 corresponds to the oldest drive type supporting the format of this
-device node (not necessarily the type of the drive refered by this
+device node (not necessarily the type of the drive referred by this
 node.)  For the generic format nodes (/dev/fd0 et al.)  the name of
 "native format" of the drive is printed, and for the default formats, if
 a generic format has been redefined, its name becomes \fR\&\f(CW(null)\fR.
@@ -211,7 +211,7 @@
 completed.
 .TP
 \&\fR\&\f(CWprobed_fmt\fR\ 
-is the the index of the autodetected format in the autodetection
+is the index of the autodetected format in the autodetection
 sequence for this drive.
 .TP
 \&\fR\&\f(CWcylinder\fR\ 
--- a/doc/acronyms.texi
+++ b/doc/acronyms.texi
@@ -66,7 +66,7 @@
 details.
 
 @item 2M (2 Megabytes)
-2M is a high capacity format developped by Ciriaco de Celis.  The basic
+2M is a high capacity format developed by Ciriaco de Celis.  The basic
 principle is the same as MSS: mix sectors of several sizes on a same
 track, in order to minimize both slack space and header overhead.  2M is
 different from MSS in that it uses a normal 18 sector format on its
--- a/doc/autodetect.texi
+++ b/doc/autodetect.texi
@@ -54,7 +54,7 @@
 21).  The 1680KB format is identical with the default 1440KB format
 except for the number of sectors.  Thus we must read the whole track in
 order to distinguish it from the 18 sector format (@code{t} flag).
-Furthermore, the the 1680KB sector format should be detected first, as
+Furthermore, the 1680KB sector format should be detected first, as
 an 21 sector disk would also matches the standard format with its 18
 sectors.
 
@@ -89,6 +89,6 @@
 Some formats use more than 80 tracks. It is not possible for the kernel
 to autodetect the number of tracks in a reasonable time, so you have to
 use a sufficiently recent version of mtools to set the number of tracks
-according to the boot sector of the disk. Mtools 3.0 and up are ok. This
+according to the boot sector of the disk. Mtools 3.0 and up are OK. This
 doesn't obviously work with disks containing something else than a
 MS-DOS filesystem.
--- a/doc/diskd.1
+++ b/doc/diskd.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
--- a/doc/diskseekd.1
+++ b/doc/diskseekd.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
@@ -83,7 +83,7 @@
 rebooting, the BIOS seeks the drive, and by doing this, it shakes the
 dust out of the drive mechanism. \fR\&\f(CWdiskseekd\fR simulates this effect
 by seeking the drive periodically.  If it is called as \fR\&\f(CWdiskseek\fR,
-the drive is seeked only once.
+the drive is sought only once.
 .PP
 .SH Options
 .PP
@@ -101,7 +101,7 @@
 \&\fR
 .TP
 \&\fR\&\f(CW-d\ \fIdrive\fR\&\f(CW\fR\ 
-Selects the drive to seek.  By default, drive 0 (\fR\&\f(CW\(if/dev/fd0\(is\fR) is seeked.
+Selects the drive to seek.  By default, drive 0 (\fR\&\f(CW\(if/dev/fd0\(is\fR) is sought.
 .TP
 \&\fR\&\f(CW-i\ \fIinterval\fR\&\f(CW\fR\ 
 Selects the cleaning interval, in seconds.  If the interval is 0, a
--- a/doc/diskseekd.texi
+++ b/doc/diskseekd.texi
@@ -13,7 +13,7 @@
 rebooting, the BIOS seeks the drive, and by doing this, it shakes the
 dust out of the drive mechanism. @code{diskseekd} simulates this effect
 by seeking the drive periodically.  If it is called as @code{diskseek},
-the drive is seeked only once.
+the drive is sought only once.
 
 @subsection Options
 
@@ -24,7 +24,7 @@
 
 @table @code
 @item -d @var{drive}
-Selects the drive to seek.  By default, drive 0 (@file{/dev/fd0}) is seeked.
+Selects the drive to seek.  By default, drive 0 (@file{/dev/fd0}) is sought.
 
 @item -i @var{interval}
 Selects the cleaning interval, in seconds.  If the interval is 0, a
--- a/doc/driveprm.texi
+++ b/doc/driveprm.texi
@@ -1,7 +1,7 @@
 @node Drive descriptions, Extended formats, Media description, Top
 @chapter Drive descriptions
 
-Unlike earlyer version, fdutils-5.0 separates drive descriptions and
+Unlike earlier version, fdutils-5.0 separates drive descriptions and
 media description.  For more details on this separation,
 @pxref{Introduction (Mediaprm)}.  Drive descriptions are used to describe the
 hardware characteristics of a drive, such as their maximal density,
@@ -45,7 +45,7 @@
 @node Cmos code, Other parameters, Form factor, Syntax of a drive description
 @subsection Cmos code
 
-The PC Bios already knows on its own about the most common drive types.
+The PC BIOS already knows on its own about the most common drive types.
 These are named by an integer from 1 to 6, according to the following
 table.
 @example
--- a/doc/fdutils.texi
+++ b/doc/fdutils.texi
@@ -89,7 +89,7 @@
 
 @unnumbered General Introduction
 
-Fdutils is a collection of utililties for configuring and using the
+Fdutils is a collection of utilities for configuring and using the
 Linux floppy driver.  With fdutils, you can:
 
 @enumerate
--- a/doc/floppymeter.1
+++ b/doc/floppymeter.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
@@ -109,7 +109,7 @@
 The rotation speed is measured by timing the return time of a
 \&\fR\&\f(CWreadid\fR command.  In order to gain more precision, the command is
 issued many times in a row. During this phase, the number of rotations
-til the start of the test, the average time per rotation til the start,
+since the start of the test, the average time per rotation since the start,
 and a sliding average of the times of the last 30 rotations is printed,
 and updated continuously.
 .PP
@@ -174,6 +174,6 @@
 * \ \ 
 All data transfer rates (for double, high and extra density) are derived
 from a same master frequency. Thus the \fIdeviation\fR of the data
-transfer rate should be independant of the density used.
+transfer rate should be independent of the density used.
 .SH See Also
 Fdutils' texinfo doc
--- a/doc/floppymeter.texi
+++ b/doc/floppymeter.texi
@@ -31,7 +31,7 @@
 The rotation speed is measured by timing the return time of a
 @code{readid} command.  In order to gain more precision, the command is
 issued many times in a row. During this phase, the number of rotations
-til the start of the test, the average time per rotation til the start,
+since the start of the test, the average time per rotation since the start,
 and a sliding average of the times of the last 30 rotations is printed,
 and updated continuously.
 
@@ -98,5 +98,5 @@
 @item
 All data transfer rates (for double, high and extra density) are derived
 from a same master frequency. Thus the @emph{deviation} of the data
-transfer rate should be independant of the density used.
+transfer rate should be independent of the density used.
 @end itemize
--- a/doc/getfdprm.1
+++ b/doc/getfdprm.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
--- a/doc/ioctl.texi
+++ b/doc/ioctl.texi
@@ -26,7 +26,7 @@
 displays the type of a drive (name parameter). This is
 used by @code{MAKEFLOPPIES}. For the naming convention, see the description
 of the @code{MAKEFLOPPIES} script. For formats which work in several drive
-types, @code{FDGETDRVTYP} return a name which is appropriate for the oldes
+types, @code{FDGETDRVTYP} return a name which is appropriate for the oldest
 drive type which supports this format.
 @item FDSETDRVPRM
 sets various drive parameters.
--- a/doc/lilo.texi
+++ b/doc/lilo.texi
@@ -1,12 +1,12 @@
 @node Boottime configuration, Floppy ioctls, Autodetection, Top
-@chapter Configuring the floppy driver via lilo or insmod
+@chapter Configuring the floppy driver via LILO or insmod
 
 The floppy driver is configured using the @code{floppy=} options in
-lilo. These options can be typed at the boot prompt, or entered in the
-lilo configuration file.
+LILO. These options can be typed at the boot prompt, or entered in the
+LILO configuration file.
 
 Example: If your kernel is called @code{linux-2.0}, type the following
-line at the lilo boot prompt (if you have a thinkpad):
+line at the LILO boot prompt (if you have a Thinkpad):
 @example
 linux-2.0 floppy=thinkpad
 @end example
@@ -22,7 +22,7 @@
 append = "floppy=daring floppy=two_fdc"
 @end example
 
-If you give options both in the lilo config file and on the boot
+If you give options both in the LILO configuration file and on the boot
 prompt, the option strings of both places are concatenated, the boot
 prompt options coming last. That's why there are also options to
 restore the default behaviour.
@@ -90,12 +90,12 @@
 @item floppy=omnibook
 @itemx floppy=nodma
 
-Tells the floppy driver not to use Dma for data transfers.  This is
+Tells the floppy driver not to use DMA for data transfers.  This is
 needed for instance on some HP Omnibooks, which don't have a workable
 DMA channel for the floppy driver. This option is also useful if you
-frequently get "Unable to allocate DMA memory" messages.  Indeed, dma
+frequently get "Unable to allocate DMA memory" messages.  Indeed, DMA
 memory needs to be continuous in physical memory, and is thus harder to
-find, whereas non-dma buffers may be allocated in virtual memory.
+find, whereas non-DMA buffers may be allocated in virtual memory.
 However, I advise against this if you have an FDC without a FIFO (8272A
 or 82072). 82072A and later are OK. You also need at least a 486 to use
 nodma.  If you use nodma mode, I suggest you also set the FIFO threshold
@@ -121,23 +121,23 @@
 system). If this is lower, the interrupt latency should be lower too
 (faster processor). The benefit of a lower threshold is less interrupts.
 
-To tune the fifo threshold, switch on over/underrun messages using
+To tune the FIFO threshold, switch on over/underrun messages using
 @code{floppycontrol --messages}. Then access a floppy disk. If you get a
-huge amount of @code{Over/Underrun - retrying} messages, then the fifo
+huge amount of @code{Over/Underrun - retrying} messages, then the FIFO
 threshold is too low. Try with a higher value, until you only get an
-occasional Over/Underrun.  It is a good idea to compile the floppy
-driver as a module when doing this tuning. Indeed, it allows to try
-different fifo values without rebooting the machine for each test. Note
+occasional over/underrun.  It is a good idea to compile the floppy
+driver as a module when doing this tuning. Indeed, it allows one to try
+different FIFO values without rebooting the machine for each test. Note
 that you need to do @code{floppycontrol --messages} every time you
 re-insert the module.
 
-Usually, tuning the fifo threshold should not be needed, as the default
+Usually, tuning the FIFO threshold should not be needed, as the default
 (0xa) is reasonable.
 
 @item floppy=@var{drive},@var{type},cmos
-Sets the cmos type of @var{drive} to @var{type}. Additionnaly, this
+Sets the CMOS type of @var{drive} to @var{type}. Additionally, this
 drive is allowed in the bitmask. This is useful if you have more than
-two floppy drives (only two can be described in the physical cmos), or
+two floppy drives (only two can be described in the physical CMOS), or
 if your BIOS uses non-standard CMOS types. The CMOS types are:
 @table @code
 @item 0
@@ -160,7 +160,7 @@
 initially chosen to represent floppy tapes, and 6 for ED drives.  AMI
 ignored this, and used 5 for ED drives. That's why the floppy driver
 handles both) Setting the CMOS to 0 for the first two drives (default)
-makes the floppy driver read the physical cmos for those drives.
+makes the floppy driver read the physical CMOS for those drives.
 
 @item floppy=unexpected_interrupts
 Print a warning message when an unexpected interrupt is received 
@@ -178,7 +178,7 @@
 whenever the device node is reopened. Needed on some boxes where the
 disk change line is broken or unsupported.  This should be regarded as a
 stopgap measure, indeed it makes floppy operation less efficient due to
-unneeded cache flushings, and slightly more unreliable. Please verify
+unneeded cache flushing, and slightly more unreliable. Please verify
 your cable, connection and jumper settings if you have any DCL problems.
 However, some older drives, and also some Laptops are known not to have
 a DCL.
--- a/doc/location.texi
+++ b/doc/location.texi
@@ -11,7 +11,7 @@
 http://fdutils.linux.lu/fdutils-5.6.tar.gz
 @end example
 
-The FAQ included in this package is also available separetely at:
+The FAQ included in this package is also available separately at:
 @example
 http://alain.knaff.linux.lu/floppy/FAQ.html
 http://www.tux.org/pub/knaff/floppy/FAQ.html
--- a/doc/makefloppies.1
+++ b/doc/makefloppies.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
@@ -128,7 +128,7 @@
 \&\fR\&\f(CW\(iffloppy\(is\fR
 .PP
 .SH Bugs
-The Makefloppies script does not work on redefined "default" formats, If
+The MAKEFLOPPIES script does not work on redefined "default" formats, If
 you redefine default formats, you need to create the needed device nodes
 manually.
 .SH See Also
--- a/doc/README
+++ b/doc/README
@@ -24,7 +24,7 @@
  4. Access to various internal driver structures, and drive
 configuration using the floppycontrol program.
 
-Floppy ioctls: 
+Floppy ioctls:
 ==============
 
  All these ioctl's may be issued using the floppycontrol program. (See also
@@ -43,7 +43,7 @@
  6. FDGETDRVTYP displays the type of a drive (name parameter). This is
 used by MAKEFLOPPIES. For the naming convention, see the description
 of the MAKEFLOPPIES script. For formats which work in several drive
-types, FDGETDRVTYP return a name which is appropriate for the oldes
+types, FDGETDRVTYP return a name which is appropriate for the oldest
 drive type which supports this format.
  7. FDSETDRVPRM sets various drive parameters.
  8. FDGETDRVPRM reads these parameters back.
@@ -73,14 +73,14 @@
 
  Some formats use more than 80 tracks. It is not possible for the
 kernel to autodetect the number of tracks in a reasonable time, so you
-have to use a sufficiently recent version of mtools o set the number
+have to use a sufficiently recent version of mtools or set the number
 of tracks according to the boot sector of the disk. Mtools 2.5 and up
-are ok. This doesn't obviously work with disks containing something
+are OK. This doesn't obviously work with disks containing something
 else than a MSDOS filesystem.
 
  The minor device number for the floppy devices is calculated as
 follows:
-    minor_device = format_nr * 4 + 128 * fdc_nr + unit_nr 
+    minor_device = format_nr * 4 + 128 * fdc_nr + unit_nr
  (fdc_nr identifies the floppy disk controller, and unit_nr identifies
 which drive on the floppy disk controller to be used)
 
@@ -129,7 +129,7 @@
 type of the drive in which this format is used.
 
  The formats 0..8 are the standard PC formats, 9 is apparently needed
-for certain weird CompaQ computers. The remaining formats are extended
+for certain weird Compaq computers. The remaining formats are extended
 capacity formats. Some of them have been taken from Heiko Schroeder's
 fdpatches (after correcting some minor bugs). Others have been added
 by David Niemi and me (Alain Knaff). Formats 30 and 31 are
@@ -151,13 +151,13 @@
 
 Example:
    Make a device entry for a 1.74MB floppy in drive 0:
-   The format number is 19, drive 0, floppy disk controller 0 so 
-   the minor device number is 128*0+4*19+0=76. The command line to make 
+   The format number is 19, drive 0, floppy disk controller 0 so
+   the minor device number is 128*0+4*19+0=76. The command line to make
    the new device entry is:
           mknod /dev/fd0H1743 b 2 76
                    ^          ^ ^ ^
                    |          | | Minor device number
-                   |          | Major device number (always 2!)           
+                   |          | Major device number (always 2!)
                    |          Blockdevice
                    A name that you choose for the format. I
 		   recommend the names I used in floppy.c, but
@@ -195,7 +195,7 @@
 
  Although most drives support more than 80 tracks some may not, and
 repeatedly trying to read beyond track 80 might be damaging to them.
-In order to know wether your drive supports more than eighty tracks,
+In order to know whether your drive supports more than eighty tracks,
 first set the number of allowed tracks to 82.
 (using floppycontrol --tracks 82 -d <drive>)
  Then format a disks with a 82 track format (for example
@@ -218,14 +218,14 @@
  N.B. I have yet to see a 3.5" drive which doesn't support 82 tracks.
 If you have such a beast, please mail me.
 
- Configuring the floppy driver via lilo:
+ Configuring the floppy driver via LILO:
  =======================================
 
  The floppy driver is configured using the 'floppy=' option in
-lilo. This option can be typed at the boot prompt, or entered in the
-lilo configuration file.
+LILO. This option can be typed at the boot prompt, or entered in the
+LILO configuration file.
  Example: If your kernel is called linux-72, type the following line
-at the lilo boot prompt (if you have a thinkpad):
+at the LILO boot prompt (if you have a Thinkpad):
  linux-72 floppy=thinkpad
 You may also enter the following line in /etc/lilo.conf, in the description
 of linux-72:
@@ -235,7 +235,7 @@
  linux-72 floppy=daring floppy=two_fdc
  append = "floppy=daring floppy=two_fdc"
 
- If you give options both in the lilo config file and on the boot
+ If you give options both in the LILO configuration file and on the boot
 prompt, the option strings of both places are concatenated, the boot
 prompt options coming last. That's why there are also options to
 restore the default behaviour.
@@ -269,9 +269,9 @@
 	Tells the floppy driver that you don't have a Thinkpad.
 
  floppy=<drive>,<type>,cmos
-	Sets the cmos type of <drive> to <type>. Additionnaly, this drive is
+	Sets the CMOS type of <drive> to <type>. Additionally, this drive is
 	allowed in the bitmask. This is useful if you have more than two
-	floppy drives (only two can be described in the physical cmos), or if
+	floppy drives (only two can be described in the physical CMOS), or if
 	your BIOS uses non-standard CMOS types. The CMOS types are:
 		0 - unknown or not installed
 		1 - 5 1/4 DD
@@ -285,10 +285,10 @@
 	AMI ignored this, and used 5 for ED drives. That's why the floppy
 	driver handles both)
 	Setting the CMOS to 0 for the first two drives (default) makes the
-	floppy driver read the physical cmos for those drives.
+	floppy driver read the physical CMOS for those drives.
 
  floppy=unexpected_interrupts
-	Print a warning message when an unexpected interrupt is received 
+	Print a warning message when an unexpected interrupt is received
 	(default behaviour)
 
  floppy=no_unexpected_interrupts
@@ -307,7 +307,7 @@
 (error reporting, operation abortion, and read track), prints out
 drive drive types, and flushes buffers. There is a -h help option.
  This program provides examples on how to use the new ioctl's.
- 
+
  To compile this program just type make in the util directory.
 
  See also the included manpage. (in the utils directory)
@@ -315,7 +315,7 @@
  2. MAKEFLOPPIES. This shell script creates the new floppy block
 device files.  It uses the floppycontrol program to translate the
 minor device numbers into meaningful names. It also uses these names
-to decide wether to create a given block device file or not, depending
+to decide whether to create a given block device file or not, depending
 on the type of the physical drive (for instance, for a 3 1/2 drive,
 the formats corresponding to a 5 1/4 drive are not created).
  If you have more than two floppy drives, the kernel cannot find out
@@ -373,11 +373,11 @@
 
 
  *formats with bigger sectors:
-	There is only one utility which can do this: 
+	There is only one utility which can do this:
 	2m20 (by Ciriaco Garcia)
-	You can get this program from 
+	You can get this program from
 	nic.switch.ch:/mirror/msdos/diskutil/2m20.zip
-	(for other adresses, see archie)	
+	(for other addresses, see archie)
 
 	This program uses a normal format for the first track and first head
 	(18 sectors), and enhanced formats for the other tracks (up to
@@ -392,7 +392,7 @@
  ==========
 
  There are man pages for mtools (in mtools/) and the utilities (in
-utils/) included. There's also a FAQ list. It is regularily updated on
+utils/) included. There's also a FAQ list. It is regularly updated on
 http://fdutils.linux.lu/FAQ.html .  You can find alpha versions of
 fdutils on http://fdutils.linux.lu/ . (They are named fduddmm.taz,
 where dd stands for the day and mm for the month. I'll only leave
--- a/doc/makefloppies.texi
+++ b/doc/makefloppies.texi
@@ -53,6 +53,6 @@
 @end table
 
 @subsection Bugs
-The Makefloppies script does not work on redefined "default" formats, If
+The MAKEFLOPPIES script does not work on redefined "default" formats, If
 you redefine default formats, you need to create the needed device nodes
 manually.
--- a/doc/man-warning.texi
+++ b/doc/man-warning.texi
@@ -2,7 +2,7 @@
 @unnumbered Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -18,11 +18,11 @@
 @end example
 
 @item
-To generate a html copy,  run:
+To generate a HTML copy,  run:
 @example
     ./configure; make html
 @end example
-A premade html can be found at:
+A pre-made HTML can be found at:
 @file{http://www.tux.org/pub/knaff/fdutils}
 
 @item
@@ -32,6 +32,6 @@
 @end example
 @end itemize
 
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
--- a/doc/mediaprm.texi
+++ b/doc/mediaprm.texi
@@ -13,8 +13,8 @@
 
 Fdutils-5.0 introduces a new uniform format description, which is
 supported both by setfdprm and superformat.  The new format description
-is easyer to handle, because it allows to set the different parameters
-of a format description in a symbolic and position independant way,
+is easier to handle, because it allows one to set the different parameters
+of a format description in a symbolic and position independent way,
 using a series of @emph{variable=value} clauses.  Moreover, it
 automatically fills in sensible default values for unspecified
 parameters.  Thus you only need to describe those aspects of the format
@@ -142,7 +142,7 @@
 @node Legacy formats, Expert options, Selecting non-standard sector sizes, Syntax
 @subsection Legacy formats
 
-The @code{swapsides} format allows to descibe disks whose sides are
+The @code{swapsides} format allows one to describe disks whose sides are
 swapped, such as CBM1581 disks.
 
 @node Expert options,, Legacy formats, Syntax
--- a/doc/moredata.texi
+++ b/doc/moredata.texi
@@ -38,7 +38,7 @@
                           in a same track
 * Smart use of the dtr::  How to get more out of your disk by playing games
                           with the data transfer rate
-* 2M::                    Make autodetection easyer by using a readable
+* 2M::                    Make autodetection easier by using a readable
                           first track
 * XDF::                   Fast high capacity formats
 * XXDF::                  Fast formats with even higher capacity
@@ -70,7 +70,7 @@
 
 This shows that we can fit 12450 / 619 = 20 sectors per track.
 
-@strong{Usage:} These disks are bootable by Lilo, and can be read in
+@strong{Usage:} These disks are bootable by LILO, and can be read in
 MS-DOS using numerous shareware utilities such as @code{vgacopy}, or
 @code{fdformat} or many others.  Check your nearest Simtel mirror.
 
@@ -144,7 +144,7 @@
 
 @strong{Usage:} Once formatted, interleaved disks can be used in a
 similar way to disks which have simply more tracks.  They can be
-accessed using @code{vgacopy} in Dos, you can boot from them using Lilo,
+accessed using @code{vgacopy} in Dos, you can boot from them using LILO,
 and you may install any filesystem on them.
 
 
@@ -174,7 +174,7 @@
 
 The principle of sector skewing is to start each track a little bit
 later than the previous one, i.e. the first logical sector of the second
-cylinder would for exemple lie near the sixth logical sector of the
+cylinder would for example lie near the sixth logical sector of the
 first cylinder.  This is done in order to account for the time needed to
 seek the drive head from the first cylinder to the second.  Without
 skewing, the first sector would already have passed the drive head after
@@ -208,7 +208,7 @@
 
 Although most drives support more than 80 tracks, I have heard rumors
 that some do not, and repeatedly trying to read beyond track 80 might be
-damaging to them.  In order to know wether your drive supports more than
+damaging to them.  In order to know whether your drive supports more than
 eighty tracks, first set the number of allowed tracks to 82.  (using
 @code{floppycontrol --cylinders 82 -d }@var{drive})
 
@@ -314,7 +314,7 @@
 
 
 @strong{Usage:} There is no known MS-DOS utility which can read basic
-MSS disks.  Lilo is not yet able to boot from this kind of disks.
+MSS disks.  LILO is not yet able to boot from this kind of disks.
 
 @strong{Performance:} As any format with larger sectors, the performance
 for small reads and writes is worse due to the larger granularity.
@@ -352,7 +352,7 @@
 this section consists in using the faster data transfer rate intended
 for 5 1/4 disks on 3 1/2 disks, and thus boost the raw capacity per
 track of these disks.  This is possible because 300 kb/s is still low
-enough not to excede the specification of the disk surface of a double
+enough not to exceed the specification of the disk surface of a double
 density disk (which 500 kb/s would).
 
 
@@ -369,7 +369,7 @@
 
 We use the @code{QD} density selector to describe this particular DTR
 set-up, although the acronym @code{QD} is already taken to name 96tpi
-double density 5 1/4 disks.  However, as this dtr trickery is only
+double density 5 1/4 disks.  However, as this DTR trickery is only
 meaningful for 3 1/2, we hope that there will be no ambiguity.
 
 
@@ -446,8 +446,8 @@
 sized sectors and too small gaps.  XDF's sector arrangement allows it to
 read sectors alternatively from both sides, i.e. the first sector from
 side 0, the second from side 1, and the third from side 0 again.  This
-differs from the usualy formats, where first the entire side 0 is read,
-and then the entire side 1.  This technique allows to read both sides of
+differs from the usually formats, where first the entire side 0 is read,
+and then the entire side 1.  This technique allows one to read both sides of
 a disk in roughly three rotations. 
 
 The following example illustrates how this is done.  In our example we
@@ -495,7 +495,7 @@
 stop at a higher position than we started, and that we also need to
 allow some time for seeking to the next track).
 
-MSS or 2M formats of the same capacity nead at least 2 rotations per
+MSS or 2M formats of the same capacity need at least 2 rotations per
 side (i.e. 4 per track), yielding a lower throughput.
 
 @strong{Usage:} XDF disks are not bootable by LILO.  They can be
@@ -513,8 +513,8 @@
 3 1/2 ED    3840KB       102KB/s       xdfcopy -2 /dev/fd0
 @end example
 
-The options @code{-1}, @code{-2} and @code{-3} descibre one out of the
-five formats understoood by @code{xdfcopy} (3 XDF formats and 2 XDF
+The options @code{-1}, @code{-2} and @code{-3} describe one out of the
+five formats understood by @code{xdfcopy} (3 XDF formats and 2 XDF
 formats).
 
 @node XXDF,, XDF, Extended formats
--- a/doc/setfdprm.1
+++ b/doc/setfdprm.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
--- a/doc/superformat.1
+++ b/doc/superformat.1
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
@@ -102,7 +102,7 @@
 \&\fR\&\f(CWmformat\fR in order to put an MS-DOS filesystem on it. You may
 ignore this filesystem, if you don't need it.
 .PP
-Superformat allows to format 2m formats.  Be aware, however, that these
+Superformat allows one to format 2m formats.  Be aware, however, that these
 \&\fR\&\f(CW2m\fR formats were specifically designed to hold an MS-DOS
 filesystem, and that they take advantage of the fact that the MS-DOS
 filesystem uses redundant sectors on the first track (the FAT, which is
--- a/doc/utilities.texi
+++ b/doc/utilities.texi
@@ -19,7 +19,7 @@
 This shell script creates the new floppy block
 device files.  It uses the floppycontrol program to translate the
 minor device numbers into meaningful names. It also uses these names
-to decide wether to create a given block device file or not, depending
+to decide whether to create a given block device file or not, depending
 on the type of the physical drive (for instance, for a 3 1/2 drive,
 the formats corresponding to a 5 1/4 drive are not created).
 If you have more than two floppy drives, the kernel cannot find out
--- a/doc/xdfcopy.1
+++ b/doc/xdfcopy.1
@@ -1,6 +1,6 @@
 .TH xdfcopy 1 "27Jan21" fdutils-5.6
 .SH Name
-xdfcopy - Program to copy and format Xdf disks in Linux
+xdfcopy - copy and format XDF disks in Linux
 '\" t
 .de TQ
 .br
@@ -15,7 +15,7 @@
 .SH Note
 This manpage has been automatically generated from fdutils's texinfo
 documentation.  However, this process is only approximative, and some
-items, such as crossreferences, footnotes and indices are lost in this
+items, such as cross-references, footnotes and indices are lost in this
 translation process.  Indeed, these items have no appropriate
 representation in the manpage format.  Moreover, only the items specific
 to each command have been translated, and the general information about
@@ -38,7 +38,7 @@
 \&\fR
 .TP
 * \ \ 
-To generate a html copy,  run:
+To generate a HTML copy,  run:
  
 .nf
 .ft 3
@@ -49,7 +49,7 @@
 .ft R
 .lp
  
-\&\fRA premade html can be found at:
+\&\fRA pre-made HTML can be found at:
 \&\fR\&\f(CW\(ifhttp://www.tux.org/pub/knaff/fdutils\(is\fR
 .TP
 * \ \ 
@@ -66,7 +66,7 @@
  
 \&\fR
 .PP
-The texinfo doc looks most pretty when printed or as html.  Indeed, in
+The texinfo doc looks most pretty when printed or as HTML.  Indeed, in
 the info version certain examples are difficult to read due to the
 quoting conventions used in info.
 .SH Description
--- a/doc/cmdname
+++ b/doc/cmdname
@@ -9,4 +9,4 @@
 MAKEFLOPPIES - Creates the default floppy device nodes.
 setfdprm - sets user-provided floppy disk parameters
 superformat - format floppies
-xdfcopy - Program to copy and format Xdf disks in Linux
+xdfcopy - copy and format XDF disks in Linux
--- a/doc/superformat.texi
+++ b/doc/superformat.texi
@@ -24,7 +24,7 @@
 @code{mformat} in order to put an MS-DOS filesystem on it. You may
 ignore this filesystem, if you don't need it.
 
-Superformat allows to format 2m formats.  Be aware, however, that these
+Superformat allows one to format 2m formats.  Be aware, however, that these
 @code{2m} formats were specifically designed to hold an MS-DOS
 filesystem, and that they take advantage of the fact that the MS-DOS
 filesystem uses redundant sectors on the first track (the FAT, which is
--- a/doc/fd.4
+++ b/doc/fd.4
@@ -235,7 +235,7 @@
 .\"}}}
 .\"{{{  Notes
 .SH NOTES
-The various formats allow to read and write many types of disks.
+The various formats allow one to read and write many types of disks.
 However, if a floppy is formatted with a too small inter sector gap,
 performance may drop, up to needing a few seconds to access an entire
 track. To prevent this, use interleaved formats. It is not possible to