* nt/README.W32: Fix typos.

2 files changed, 24 insertions, 22 deletions

diff --git a/admin/ChangeLog b/admin/ChangeLog
index cbc244bd78c..7422d12fb81 100644
--- a/admin/ChangeLog
+++ b/admin/ChangeLog
@@ -1,13 +1,16 @@
+2009-02-24  Juanma Barranquero  <lekktu@gmail.com>
+
+        * nt/README.W32: Fix typos.
+
 2009-02-23  Jason Rumney  <jasonr@gnu.org>
 
         * nt/README-ftp-server: Update for 23.0.91
 
-        * nt/README.W32: Remove ever expanding versions of
-        Windows. Shorten FAQ URL.  Remove mention of obsolete lock
-        directory.  Windows distribution now bin and barebin only.  Add
-        note about SVG support.  Remove old tar and gzip problem
-        workarounds.  Use new (22.x) -Q option.  Report all bugs through
-        bug tracker.
+        * nt/README.W32: Remove ever expanding versions of Windows.
+        Shorten FAQ URL.  Remove mention of obsolete lock directory.
+        Windows distribution now bin and barebin only.  Add note about
+        SVG support.  Remove old tar and gzip problem workarounds.
+        Use new (22.x) -Q option.  Report all bugs through bug tracker.
 
         * nt/README-UNDUMP.W32: Modify for barebin distribution, as
         undumped distribution no longer exists.
diff --git a/admin/nt/README.W32 b/admin/nt/README.W32
index d21959ced19..3c9b5bda87c 100644
--- a/admin/nt/README.W32
+++ b/admin/nt/README.W32
@@ -71,7 +71,7 @@ See the end of the file for license conditions.
 
   Emacs comes with the following executable files in the bin directory.
 
-  + emacs.exe - The main Emacs executable. As this is designed to run
+  + emacs.exe - The main Emacs executable.  As this is designed to run
     as both a text-mode application (emacs -nw) and as a GUI application,
     it will pop up a command prompt window if run directly from Explorer.
 
@@ -79,7 +79,7 @@ See the end of the file for license conditions.
     without popping up a command prompt window.
 
   + emacsclient.exe - A command-line client program that can
-    communicate with a running Emacs process. See the `Emacs Server'
+    communicate with a running Emacs process.  See the `Emacs Server'
     node of the Emacs manual.
 
   + emacsclientw.exe - A version of emacsclient that does not open
@@ -92,7 +92,7 @@ See the end of the file for license conditions.
     the native shells in various versions of Windows.
 
   + ctags.exe, etags.exe - Tools for generating tag files.  See the
-  `Tags' node of the Emacs manual.
+    `Tags' node of the Emacs manual.
 
   + ebrowse.exe - A tool for generating C++ browse information.  See the
     `Ebrowse' manual.
@@ -113,19 +113,19 @@ See the end of the file for license conditions.
 
   Emacs has built in support for XBM and PPM/PGM/PBM images, and the
   libXpm library is bundled, providing XPM support (required for color
-  toolbar icons and splash screen). Source for libXpm should be available
-  on the same place as you got this binary distribution from. The version
+  toolbar icons and splash screen).  Source for libXpm should be available
+  on the same place as you got this binary distribution from.  The version
   of libXpm bundled with this version of Emacs is 3.5.7, based on x.org's
   libXpm library from X11R7.3.
 
   Emacs can also support some other image formats with appropriate
-  libraries. These libraries are all available as part of GTK, or from
-  gnuwin32.sourceforge.net. Emacs will find them if the directory they
+  libraries.  These libraries are all available as part of GTK, or from
+  gnuwin32.sourceforge.net.  Emacs will find them if the directory they
   are installed in is on the PATH.
 
       PNG: requires the PNG reference library 1.2 or later, which will
       be named libpng13d.dll, libpng13.dll, libpng12d.dll, libpng12.dll
-      or libpng.dll. LibPNG requires zlib, which should come from the same
+      or libpng.dll.  LibPNG requires zlib, which should come from the same
       source as you got libpng.
 
       JPEG: requires the Independant JPEG Group's libjpeg 6b or later,
@@ -137,10 +137,10 @@ See the end of the file for license conditions.
       GIF: requires libungif or giflib 4.1 or later, which will be
       called giflib4.dll, libungif4.dll or libungif.dll.
 
-   In addition, Emacs can be compiled to support SVG. This precompiled
+   In addition, Emacs can be compiled to support SVG.  This precompiled
    distribution has not been compiled that way, since the SVG library
    or one or more of its extensive dependencies appear to be
-   unreliable under Windows. See nt/INSTALL in the src distribution if
+   unreliable under Windows.  See nt/INSTALL in the src distribution if
    you wish to compile Emacs with SVG support.
 
 * Uninstalling Emacs
@@ -195,7 +195,7 @@ See the end of the file for license conditions.
 * Further information
 
   If you have access to the World Wide Web, I would recommend pointing
-  your favorite web browser to following the document (if you haven't
+  your favorite web browser to the following document (if you haven't
   already):
 
         http://www.gnu.org/software/emacs/windows/
@@ -217,7 +217,7 @@ See the end of the file for license conditions.
 
   Another valuable source of information and help which should not be
   overlooked is the various Usenet news groups dedicated to Emacs.
-  These are particuarly good for help with general issues which aren't
+  These are particularly good for help with general issues which aren't
   specific to the Windows port of Emacs.  The main news groups to use
   for seeking help are:
 
@@ -241,10 +241,9 @@ See the end of the file for license conditions.
   reporting facility to report it (from the menu; Help -> Send Bug Report).
   If you have not yet configured Emacs for mail, then when you press
   C-c C-c to send the report, it will ask you to paste the text of the
-  report into your mail client.  If the bug is related to
-  subprocesses, also specify which shell you are using (e.g., include
-  the values of `shell-file-name' and `shell-explicit-file-name' in
-  your message).
+  report into your mail client.  If the bug is related to subprocesses,
+  also specify which shell you are using (e.g., include the values of
+  `shell-file-name' and `explicit-shell-file-name' in your message).
 
   Enjoy!