You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by hu...@apache.org on 2012/08/09 09:06:30 UTC

svn commit: r1371054 - /httpd/httpd/branches/2.2.x/docs/manual/mod/mod_mime.xml

Author: humbedooh
Date: Thu Aug  9 07:06:30 2012
New Revision: 1371054

URL: http://svn.apache.org/viewvc?rev=1371054&view=rev
Log:
typo fixes

Modified:
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_mime.xml

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_mime.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_mime.xml?rev=1371054&r1=1371053&r2=1371054&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_mime.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_mime.xml Thu Aug  9 07:06:30 2012
@@ -571,7 +571,7 @@ a matching file with MultiViews</descrip
 
     <p>The <code>NegotiatedOnly</code> option provides that every extension
     following the base name must correlate to a recognized
-    <module>mod_mime</module> extension for content negotation, <em>e.g.</em>
+    <module>mod_mime</module> extension for content negotiation, <em>e.g.</em>
     Charset, Content-Type, Language, or Encoding.  This is the strictest
     implementation with the fewest unexpected side effects, and is the
     default behavior.</p>
@@ -588,7 +588,7 @@ a matching file with MultiViews</descrip
 
     <p>You may finally allow <code>Any</code> extensions to match, even if
     <module>mod_mime</module> doesn't recognize the extension. This was the
-    behavior in Apache 1.3, and can cause unpredicatable results, such as
+    behavior in Apache 1.3, and can cause unpredictable results, such as
     serving .old or .bak files the webmaster never expected to be served.</p>
 
     <p>For example, the following configuration will allow handlers