Fix typo in docs

(miscomception ->misconception)

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1367778 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/howto/htaccess.html.en b/docs/manual/howto/htaccess.html.en
index fe50153787625da082792aed21f715d2c11c2210..7ff6e93d30512558b6e2f45d86d148d297ec11db 100644 (file)
--- a/docs/manual/howto/htaccess.html.en
+++ b/docs/manual/howto/htaccess.html.en
@@ -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>

diff --git a/docs/manual/howto/htaccess.xml b/docs/manual/howto/htaccess.xml
index 30ca856f10a1b9d0f138b734f4eef5a9a35817f7..5c8ddb9871f848cd982965a6696770a3a23440de 100644 (file)
--- a/docs/manual/howto/htaccess.xml
+++ b/docs/manual/howto/htaccess.xml
@@ -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