Typos

INSTALL

@@ -12,12 +12,12 @@ The build instructions of the WATCOM build are generic and generated
 automatically. They assume that the main Makefile would be called
 'Makefile'.  This isn't the case for AdPlug's WATCOM build! AdPlug's
 WATCOM Makefile is called 'Makefile.wat'. Thus, you have to give the
-commandline option '/f Makefile.wat' every time you run a 'wmake'
+command-line option '/f Makefile.wat' every time you run a 'wmake'
 command. For example, to install AdPlug, call wmake like this:
 
 wmake /f Makefile.wat install
 
-Do this similary with any other 'wmake' target.
+Do this similarly with any other 'wmake' target.
 
 Appendix to 'INSTALL.unix':
 ---------------------------

INSTALL.dos

@@ -6,13 +6,13 @@ These instructions assume that Watcom is the default compiler of this software
 package. If this software supports additional compilers, aside from Watcom, it
 is very likely that this build system is not the default. In this case, it may
 well be possible that some files have different names than assumed in these
-instructions. Please consult the software ditribution's documentation for more
+instructions. Please consult the software distribution's documentation for more
 information on this topic.
 
 Configuration
 -------------
 Before you can compile anything, create a file called CONFIG.MIF in the
-distribution's base directory. It is best to copy the template below out of
+distribution's base directory. It is best to copy the template below from
 this file and modify it to fit your setup.
 
 In most cases, you just want to change the installation target directories
@@ -54,7 +54,7 @@ CONFIG.MIF file:
 debug = yes
 
 This will recompile all source files with source-level debugging enabled and
-instructs the linker to include debugging information. Be careful with the
+instruct the linker to include debugging information. Be careful with the
 SYSTEM setting in your CONFIG.MIF file, though. Only some extenders are
 supported by the Watcom debugger. Some distributions may have defined a
 non-compatible extender by default, which you must override by specifying

INSTALL.unix

@@ -11,8 +11,8 @@ Basic Installation
 ==================
 
 Briefly, the shell commands `./configure; make; make install' should
-configure, build, and install this package.  The following
-more-detailed instructions are generic; see the `README' file for
+configure, build, and install this package.  The following,
+more detailed instructions are generic; see the `README' file for
 instructions specific to this package.
 
    The `configure' shell script attempts to guess correct values for
@@ -86,7 +86,7 @@ Compiling For Multiple Architectures
 ====================================
 
 You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
+same time by placing the object files for each architecture in their
 own directory.  To do this, you can use GNU `make'.  `cd' to the
 directory where you want the object files and executables to go and run
 the `configure' script.  `configure' automatically checks for the
@@ -111,7 +111,7 @@ pass the option `--exec-prefix=PREFIX' to `configure', the package uses
 PREFIX as the prefix for installing programs and libraries.
 Documentation and other data files still use the regular prefix.
 
-   In addition, if you use an unusual directory layout you can give
+   In addition, if you use an unusual directory layout, you can give
 options like `--bindir=DIR' to specify different values for particular
 kinds of files.  Run `configure --help' for a list of the directories
 you can set and what kinds of files go in them.
@@ -160,7 +160,7 @@ need to know the machine type.
 use the option `--target=TYPE' to select the type of system they will
 produce code for.
 
-   If you want to _use_ a cross compiler, that generates code for a
+   If you want to _use_ a cross compiler that generates code for a
 platform different from the build platform, you should specify the
 "host" platform (i.e., that on which the generated programs will
 eventually be run) with `--host=TYPE'.
@@ -226,7 +226,7 @@ an Autoconf bug.  Until the bug is fixed you can use this workaround:
      messages will still be shown).
 
 `--srcdir=DIR'
-     Look for the package's source code in directory DIR.  Usually
+     Look for the package's source code in directory DIR.  Usually,
      `configure' can determine that directory automatically.
 
 `configure' also accepts some other, not widely useful, options.  Run

INSTALL.win32

@@ -2,7 +2,7 @@ Configuration
 -------------
 Before you can compile anything, create a file called 'config.bat' in the
 source subdirectory ('src', that is). It's best to copy the template below
-out of this file and modify it to fit your setup.
+from this file and modify it to fit your setup.
 
 In most cases, you just want to change the installation target directories
 "bindir", "includedir" and "libdir" to your standard binary, header and
@@ -22,7 +22,7 @@ the directory names, using the appropriate listboxes.
 Setup
 -----
 Start MSVC and create a new workspace. Then load the project file
-libbinio.dsp from the source subdirecotry into it and you're finished.
+libbinio.dsp from the source subdirectory into it and you're finished.
 
 config.bat Template
 -------------------