You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rj...@apache.org on 2012/07/31 23:01:02 UTC

svn commit: r1367779 - in /httpd/httpd/branches/2.4.x: ./ docs/manual/howto/htaccess.html.en docs/manual/howto/htaccess.xml

Author: rjung
Date: Tue Jul 31 21:01:02 2012
New Revision: 1367779

URL: http://svn.apache.org/viewvc?rev=1367779&view=rev
Log:
Fix typo in docs
(miscomception ->misconception)

Backport of r1367778 from trunk.

Modified:
    httpd/httpd/branches/2.4.x/   (props changed)
    httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.html.en
    httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.xml

Propchange: httpd/httpd/branches/2.4.x/
------------------------------------------------------------------------------
  Merged /httpd/httpd/trunk:r1367778

Modified: httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.html.en?rev=1367779&r1=1367778&r2=1367779&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.html.en (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.html.en Tue Jul 31 21:01:02 2012
@@ -110,7 +110,7 @@ changes on a per-directory basis.</p>
     you don't have access to the main server configuration file. There is,
     for example, a common misconception that user authentication should
     always be done in <code>.htaccess</code> files, and, in more recent years,
-    another miscomception that <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> directives
+    another misconception that <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> directives
     must go in <code>.htaccess</code> files. This is simply not the
     case. You can put user authentication configurations in the main server
     configuration, and this is, in fact, the preferred way to do
@@ -441,4 +441,4 @@ if (typeof(prettyPrint) !== 'undefined')
     prettyPrint();
 }
 //--><!]]></script>
-</body></html>
\ No newline at end of file
+</body></html>

Modified: httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.xml?rev=1367779&r1=1367778&r2=1367779&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/howto/htaccess.xml Tue Jul 31 21:01:02 2012
@@ -128,7 +128,7 @@ changes on a per-directory basis.</p>
     you don't have access to the main server configuration file. There is,
     for example, a common misconception that user authentication should
     always be done in <code>.htaccess</code> files, and, in more recent years,
-    another miscomception that <module>mod_rewrite</module> directives
+    another misconception that <module>mod_rewrite</module> directives
     must go in <code>.htaccess</code> files. This is simply not the
     case. You can put user authentication configurations in the main server
     configuration, and this is, in fact, the preferred way to do