Fix docs typos.

Submitted by: Rodent of Unusual Size <coar@decus.org>
Reviewed by: Marc Slemko

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

diff --git a/docs/manual/mod/mod_auth.html b/docs/manual/mod/mod_auth.html
index ac44fd6103542c910a4e0e4ae957ce55351c29d2..6d40ade4cd9f6a3ce04558dabd10fc097da0a817 100644 (file)
--- a/docs/manual/mod/mod_auth.html
+++ b/docs/manual/mod/mod_auth.html
@@ -85,7 +85,7 @@ See also <A HREF="core.html#authname">AuthName</A>,
 Setting the AuthAuthoritative directive explicitly to <b>'off'</b>
 allows for both authentification and authorization to be passed on to
 lower level modules (as defined in the <code>Configuration</code> and
-<code>modules.c</code> file if there is <b>no userID</b> or
+<code>modules.c</code> files) if there is <b>no userID</b> or
 <b>rule</b> matching the supplied userID. If there is a userID and/or
 rule specified; the usual password and access checks will be applied
 and a failure will give an Authorization Required reply.

diff --git a/docs/manual/mod/mod_auth_db.html b/docs/manual/mod/mod_auth_db.html
index c2566c17859455956640e4415f88e6fc600e8b61..6bd64171e757cf84a8fa7947b7699acc8646e279 100644 (file)
--- a/docs/manual/mod/mod_auth_db.html
+++ b/docs/manual/mod/mod_auth_db.html
@@ -118,7 +118,7 @@ Setting the AuthDBAuthoritative directive explicitly to <b>'off'</b> allows for
 So if a userID appears in the database of more than one module; or if a valid require directive applies to more than one module; then the first module will verify the credentials; and no access is passed on; regardless of the AuthAuthoritative setting.
 <p>
 A common use for this is in conjection with one of the basic auth modules; such
-as <a href="mod_auth.c"><code>mod_auth.c</code></a>. Whereas this DB module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file.
+as <a href="mod_auth.html"><code>mod_auth.c</code></a>. Whereas this DB module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file.
 <p>
 <b>Default:</b> By default; control is not passed on; and an unkown userID or rule will result in an Authorization Required reply. Not setting it thus keeps the system secure; and forces an NSCA compliant behaviour.
 <p>

diff --git a/docs/manual/mod/mod_auth_dbm.html b/docs/manual/mod/mod_auth_dbm.html
index 201df5e7d2a5a5a07f59d74a97a3a3a6fabc4374..486c0c1522f1a42655de6551055048aa00427ae4 100644 (file)
--- a/docs/manual/mod/mod_auth_dbm.html
+++ b/docs/manual/mod/mod_auth_dbm.html
@@ -119,7 +119,7 @@ Setting the AuthDBMAuthoritative directive explicitly to <b>'off'</b> allows for
 So if a userID appears in the database of more than one module; or if a valid require directive applies to more than one module; then the first module will verify the credentials; and no access is passed on; regardless of the AuthAuthoritative setting.
 <p>
 A common use for this is in conjection with one of the basic auth modules; such
-as <a href="mod_auth.c"><code>mod_auth.c</code></a>. Whereas this DBM module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file.
+as <a href="mod_auth.html"><code>mod_auth.c</code></a>. Whereas this DBM module supplies the bulk of the user credential checking; a few (administrator) related accesses fall through to a lower level with a well protected .htpasswd file.
 <p>
 <b>Default:</b> By default; control is not passed on; and an unkown userID or rule will result in an Authorization Required reply. Not setting it thus keeps the system secure; and forces an NSCA compliant behaviour.
 <p>