From: Daniel Gruno <humbedooh@apache.org>
Date: Thu, 9 Aug 2012 07:23:50 +0000 (+0000)
Subject: typo fixes
X-Git-Tag: 2.2.23~68
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=8acce95b0234448ef597bc4bab45cc776b15da45;p=thirdparty%2Fapache%2Fhttpd.git

typo fixes

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1371056 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/content-negotiation.xml b/docs/manual/content-negotiation.xml
index 99fd780ccf3..93288f09f67 100644
--- a/docs/manual/content-negotiation.xml
+++ b/docs/manual/content-negotiation.xml
@@ -180,7 +180,7 @@
     represents.</p>
 
     <p>The full list of headers recognized is available in the <a
-    href="mod/mod_negotiation.html#typemaps">mod_negotation
+    href="mod/mod_negotiation.html#typemaps">mod_negotiation
     typemap</a> documentation.</p>
 </section>
 
diff --git a/docs/manual/install.xml b/docs/manual/install.xml
index 95c0db2b294..c8e1cd0f364 100644
--- a/docs/manual/install.xml
+++ b/docs/manual/install.xml
@@ -379,7 +379,7 @@
     major releases (for example, from 1.3 to 2.0 or from 2.0 to 2.2),
     there will likely be major differences in the compile-time and
     run-time configuration that will require manual adjustments.  All
-    modules will also need to be upgraded to accomodate changes in the
+    modules will also need to be upgraded to accommodate changes in the
     module API.</p>
 
     <p>Upgrading from one minor version to the next (for example, from
diff --git a/docs/manual/mod/mod_cache.xml b/docs/manual/mod/mod_cache.xml
index de02d3866a8..5bbfb35ab38 100644
--- a/docs/manual/mod/mod_cache.xml
+++ b/docs/manual/mod/mod_cache.xml
@@ -133,7 +133,7 @@
   becomes stale, and the time the stale entity is fully refreshed. On a busy
   server, a significant number of requests might arrive during this time, and
   cause a <strong>thundering herd</strong> of requests to strike the backend
-  suddenly and unpredicably.</p>
+  suddenly and unpredictably.</p>
   <p>To keep the thundering herd at bay, the <directive>CacheLock</directive>
   directive can be used to define a directory in which locks are created for
   URLs <strong>in flight</strong>. The lock is used as a <strong>hint</strong>
diff --git a/docs/manual/mod/mod_mem_cache.xml b/docs/manual/mod/mod_mem_cache.xml
index 34886309e4a..b84ea4e5821 100644
--- a/docs/manual/mod/mod_mem_cache.xml
+++ b/docs/manual/mod/mod_mem_cache.xml
@@ -46,7 +46,7 @@
     should be the preferred choice. This is explained further in the <a
     href="../caching.html#inmemory">Caching Guide</a>.  In particular,
     this module's cache is <em>per-process</em>, which can be partially
-    mitigated by configuring threaded MPMS to use fewer child processes
+    mitigated by configuring threaded MPMs to use fewer child processes
     via configuration of larger values for <directive 
     module="mpm_common">ThreadsPerChild</directive>.  This module's cache is 
     also limited to storing a single variant (see HTTP Vary: header) of each