diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog
index 12681e842..19f85332c 100644
--- a/winsup/doc/ChangeLog
+++ b/winsup/doc/ChangeLog
@@ -1,3 +1,7 @@
+2009-05-26  Christopher Faylor  <me+cygwin@cgf.cx>
+
+	Change explicitely to explicitly throughout.
+
 2009-05-15  Corinna Vinschen  <corinna@vinschen.de>
 
 	* setup2.sgml (setup-locale-console): Disable section for now.
diff --git a/winsup/doc/cygserver.sgml b/winsup/doc/cygserver.sgml
index 006a93ed6..b78a93ac4 100644
--- a/winsup/doc/cygserver.sgml
+++ b/winsup/doc/cygserver.sgml
@@ -91,7 +91,7 @@
     Force logging to stderr.  This is the default if stderr is connected to
     a tty.  Otherwise, the default is logging to the system log.  By using
     the -e, -E, -y, -Y options (or the appropriate settings in the
-    configuration file), you can explicitely set the logging output as you
+    configuration file), you can explicitly set the logging output as you
     like, even to both, stderr and syslog.
     Configuration file option:  kern.log.stderr
   </para>
diff --git a/winsup/doc/cygwinenv.sgml b/winsup/doc/cygwinenv.sgml
index cefecf254..afd5392af 100644
--- a/winsup/doc/cygwinenv.sgml
+++ b/winsup/doc/cygwinenv.sgml
@@ -165,7 +165,7 @@ below.</para>
 <listitem>
 <para><envar>(no)binmode</envar> - This option has been removed because
 all file opens default to binary mode, unless the open mode has been specified
-explicitely in the open(2) call.
+explicitly in the open(2) call.
 </para>
 </listitem>
 
diff --git a/winsup/doc/ntsec.sgml b/winsup/doc/ntsec.sgml
index 6f8ebee0d..89006e335 100644
--- a/winsup/doc/ntsec.sgml
+++ b/winsup/doc/ntsec.sgml
@@ -641,7 +641,7 @@ Unfortunately that's too simple.  Using <command>NtCreateToken</command>
 has a few drawbacks.</para>
 
 <para>First of all, beginning with Windows Server 2003,
-the permission "Create a token object" gets explicitely removed from
+the permission "Create a token object" gets explicitly removed from
 the SYSTEM user's access token, when starting services under that
 account.  That requires us to create a new account with this specific
 permission just to run this kind of services.  But that's a minor
diff --git a/winsup/doc/pathnames.sgml b/winsup/doc/pathnames.sgml
index 313aef37b..3f7d2f451 100644
--- a/winsup/doc/pathnames.sgml
+++ b/winsup/doc/pathnames.sgml
@@ -266,7 +266,7 @@ point.  For instance this:</para>
 </screen>
 
 <para>will not make file access using the /mnt/d path prefix suddenly using
-textmode.  If you want to mount any drive explicitely in another mode than
+textmode.  If you want to mount any drive explicitly in another mode than
 the cygdrive prefix, use a distinct path prefix:</para>
 
 <screen>
@@ -501,7 +501,7 @@ case-sensitivity on the <filename>/cygdrive</filename> prefix, your shell
 might claim that it can't find Windows commands like <command>attrib</command>
 or <command>net</command>.  To ease the pain, the <filename>/cygdrive</filename>
 path is case-insensitive by default and you have to use the "posix=1" setting
-explicitely in <filename>/etc/fstab</filename> or
+explicitly in <filename>/etc/fstab</filename> or
 <filename>/etc/fstab.d/$USER</filename> to switch it to case-sensitivity,
 or you have to make sure that the native Win32 %PATH% environment variable
 is using the correct case for all paths throughout.</para>
diff --git a/winsup/doc/setup2.sgml b/winsup/doc/setup2.sgml
index ec30f5dae..a5c8f3da4 100644
--- a/winsup/doc/setup2.sgml
+++ b/winsup/doc/setup2.sgml
@@ -222,7 +222,7 @@ supports all relevant default ANSI codepages...</para>
 
 <listitem><para>
 You don't want to use the default Windows codepage as character set?
-In that case you have to specify the charset explicitely.  For instance,
+In that case you have to specify the charset explicitly.  For instance,
 assume you're from Italy and don't want to use the default Windows codepage
 1252, but the more portable ISO-8859-15 character set.  What you can do is
 to set the <envar>LANG</envar> variable in the
@@ -271,7 +271,7 @@ used for in- and output, the Windows console hasn't such a way, since it's
 not an application in its own right.</para>
 
 <para>This problem is solved in Cygwin as follows.  When the first Cygwin
-process is started in a Windows console (either explicitely from cmd.exe,
+process is started in a Windows console (either explicitly from cmd.exe,
 or implicitly by, for instance, clicking on the Cygwin desktop icon, or
 running the Cygwin.bat file), the Console character set is determined by the
 setting of the aforementioned internationalization environment variables,