From: Andre Malo <nd@apache.org>
Date: Thu, 12 Dec 2002 00:04:01 +0000 (+0000)
Subject: small markup issues
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9cc70cc559f6c984cc5ea746e2eaaf94d9456dee;p=thirdparty%2Fapache%2Fhttpd.git

small markup issues


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

diff --git a/docs/manual/mod/mod_auth_digest.html.en b/docs/manual/mod/mod_auth_digest.html.en
index 396aabd52d9..5ecc263348d 100644
--- a/docs/manual/mod/mod_auth_digest.html.en
+++ b/docs/manual/mod/mod_auth_digest.html.en
@@ -126,19 +126,18 @@ authentication</td></tr>
 </table>
     <p>The <code class="directive">AuthDigestDomain</code> directive allows
     you to specify one or more URIs which are in the same protection
-    space (i.e. use the same realm and username/password info). The
-    specified URIs are prefixes, i.e. the client will assume that all
-    URIs "below" these are also protected by the same
-    username/password. The URIs may be either absolute URIs
-    (i.e. inluding a scheme, host, port, etc) or relative URIs.</p>
+    space (<em>i.e.</em> use the same realm and username/password info).
+    The specified URIs are prefixes, <em>i.e.</em> the client will assume
+    that all URIs "below" these are also protected by the same
+    username/password. The URIs may be either absolute URIs (<em>i.e.</em>
+    inluding a scheme, host, port, etc) or relative URIs.</p>
 
     <p>This directive <em>should</em> always be specified and
     contain at least the (set of) root URI(s) for this space.
     Omitting to do so will cause the client to send the
     Authorization header for <em>every request</em> sent to this
     server. Apart from increasing the size of the request, it may
-    also have a detrimental effect on performance if
-    "AuthDigestNcCheck" is on.</p>
+    also have a detrimental effect on performance if <code class="directive"><a href="#authdigestnccheck">AuthDigestNcCheck</a></code> is on.</p>
 
     <p>The URIs specified can also point to different servers, in
     which case clients (which understand this) will then share
@@ -281,7 +280,7 @@ of clients</td></tr>
     <div class="example"><p><code>
       AuthDigestShmemSize 1048576<br />
       AuthDigestShmemSize 1024K<br />
-      AuthDigestShmemSize 1M<br />
+      AuthDigestShmemSize 1M
     </code></p></div>
 
 </div>
diff --git a/docs/manual/mod/mod_auth_digest.xml b/docs/manual/mod/mod_auth_digest.xml
index 4709d94b3ca..0f25d9d953a 100644
--- a/docs/manual/mod/mod_auth_digest.xml
+++ b/docs/manual/mod/mod_auth_digest.xml
@@ -231,19 +231,19 @@ authentication</description>
 <usage>
     <p>The <directive>AuthDigestDomain</directive> directive allows
     you to specify one or more URIs which are in the same protection
-    space (i.e. use the same realm and username/password info). The
-    specified URIs are prefixes, i.e. the client will assume that all
-    URIs "below" these are also protected by the same
-    username/password. The URIs may be either absolute URIs
-    (i.e. inluding a scheme, host, port, etc) or relative URIs.</p>
+    space (<em>i.e.</em> use the same realm and username/password info).
+    The specified URIs are prefixes, <em>i.e.</em> the client will assume
+    that all URIs "below" these are also protected by the same
+    username/password. The URIs may be either absolute URIs (<em>i.e.</em>
+    inluding a scheme, host, port, etc) or relative URIs.</p>
 
     <p>This directive <em>should</em> always be specified and
     contain at least the (set of) root URI(s) for this space.
     Omitting to do so will cause the client to send the
     Authorization header for <em>every request</em> sent to this
     server. Apart from increasing the size of the request, it may
-    also have a detrimental effect on performance if
-    "AuthDigestNcCheck" is on.</p>
+    also have a detrimental effect on performance if <directive
+    module="mod_auth_digest">AuthDigestNcCheck</directive> is on.</p>
 
     <p>The URIs specified can also point to different servers, in
     which case clients (which understand this) will then share
@@ -279,7 +279,7 @@ of clients</description>
     <example>
       AuthDigestShmemSize 1048576<br />
       AuthDigestShmemSize 1024K<br />
-      AuthDigestShmemSize 1M<br />
+      AuthDigestShmemSize 1M
     </example>
 </usage>
 </directivesynopsis>