The semi-regular HTML cleanup of the documentation. There are

	some HTML errors (incorrect anchor nesting, primarily) coming in
	another commit.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@82065 13f79535-47bb-0310-9956-ffa450edef68

7 files changed, 38 insertions, 38 deletions

diff --git a/htdocs/manual/misc/FAQ.html b/htdocs/manual/misc/FAQ.html
index f69907fbf3..f5e9113bb7 100644
--- a/htdocs/manual/misc/FAQ.html
+++ b/htdocs/manual/misc/FAQ.html
@@ -14,7 +14,7 @@
   <!--#include virtual="header.html" -->
   <H1 ALIGN="CENTER">Apache Server Frequently Asked Questions</H1>
   <P>
-  $Revision: 1.127 $ ($Date: 1998/09/09 16:01:03 $)
+  $Revision: 1.128 $ ($Date: 1998/09/17 12:33:01 $)
   </P>
   <P>
   The latest version of this FAQ is always available from the main
@@ -418,7 +418,7 @@
     occasional users.
    </LI>
   </UL>
-  <p></P>
+  <P></P>
   <HR>
  </LI>
 
@@ -552,7 +552,7 @@
       (dbx) where</CODE>
      </DD>
     </DL>
-    <p></P>
+    <P></P>
     <P>
     (Substitute the appropriate locations for your
     <SAMP>ServerRoot</SAMP> and your <SAMP>httpd</SAMP> and
@@ -618,7 +618,7 @@
      <DD><CODE>AddHandler cgi-script .cgi</CODE>
      </DD>
     </DL>
-    <p></P>
+    <P></P>
     <P>
     The server will then recognize that all files in that location (and
     its logical descendants) that end in &quot;<SAMP>.cgi</SAMP>&quot;
@@ -630,7 +630,7 @@
     declaration that includes the <SAMP>ExecCGI</SAMP> option.
    </LI>
   </OL>
-  <p></P>
+  <P></P>
   <P>
   In some situations, you might not want to actually
   allow all files named &quot;<SAMP>*.cgi</SAMP>&quot; to be executable.
@@ -652,7 +652,7 @@
       RewriteRule   ^quux\.cgi$  -  [T=application/x-httpd-cgi]</CODE>
      </DD>
     </DL>
-    <p></P>
+    <P></P>
    </LI>
    <LI>Make sure that the directory location is covered by an
     <A HREF="../mod/core.html#options"><SAMP>Options</SAMP></A>
@@ -660,7 +660,7 @@
     <SAMP>FollowSymLinks</SAMP> option.
    </LI>
   </OL>
-  <p></P>
+  <P></P>
   <HR>
  </LI>
 
@@ -703,7 +703,7 @@
     }</CODE>
    </DD>
   </DL>
-  <p></P>
+  <P></P>
   <P>
   This is generally only necessary when you are calling external
   programs from your script that send output to stdout, or if there will
@@ -764,7 +764,7 @@
      <DD><CODE>AddHandler server-parsed .shtml</CODE>
      </DD>
     </DL>
-    <p></P>
+    <P></P>
     <P>
     This indicates that all files ending in &quot;.shtml&quot; in that
     location (or its descendants) should be parsed.  Note that using
@@ -1195,7 +1195,7 @@
     BrowserMatch JDK/1.0 force-response-1.0</CODE>
    </DD>
   </DL>
-  <p></P>
+  <P></P>
   <P>
   More information about this issue can be found in the
   <A HREF="http://www.apache.org/info/jdk-102.html"
@@ -1308,7 +1308,7 @@
     This hurts performance and should only be used as a last resort.
    </LI>
   </UL>
-  <p></P>
+  <P></P>
   <HR>
  </LI>
 
@@ -1381,7 +1381,7 @@
      <DD><CODE>EXTRA_CFLAGS=-DMAXIMUM_DNS</CODE>
      </DD>
     </DL>
-    <p></P>
+    <P></P>
     <P>
     This will cause Apache to be very paranoid about making sure a
     particular host address is <EM>really</EM> assigned to the name it
@@ -1459,7 +1459,7 @@
      <DD><CODE>AddType audio/x-midi .mid .midi .kar</CODE>
      </DD>
     </DL>
-    <p></P>
+    <P></P>
     <P>
     Note that this may break browsers that <EM>do</EM> recognize the
     <SAMP>audio/midi</SAMP> MIME type unless they're prepared to also
@@ -1600,7 +1600,7 @@
     EXTRA_LIBS=-lbind</CODE>
    </DD>
   </DL>
-  <p></P>
+  <P></P>
   <HR>
  </LI>
 
@@ -1710,7 +1710,7 @@
     satisfy any</CODE>
    </DD>
   </DL>
-  <p></P>
+  <P></P>
   <P>
   See the <A HREF="#user-authentication">user authentication</A>
   question and the <A HREF="../mod/mod_access.html">mod_access</A>
@@ -2299,7 +2299,7 @@
     <P>
     If you fail to do this, then it is very likely that Apache will fail
     to build.  One of the most common errors is with <CODE>readv</CODE>,
-    <CODE>writev</CODE>, or <CODE>uio.h</CODE>.  This is <B>not</B> a
+    <CODE>writev</CODE>, or <CODE>uio.h</CODE>.  This is <STRONG>not</STRONG> a
     bug with Apache.  You will need to re-install GCC.
    <HR>
   </LI>
@@ -2324,11 +2324,11 @@
    Improvements, modifications and additions should follow these instructions.
    <P>
    In general, the first course of action is to be a member of the
-   <code>new-httpd@apache.org</code> mailing list. This indicates to the Group that
+   <CODE>new-httpd@apache.org</CODE> mailing list. This indicates to the Group that
    you are closely following the latest Apache developments. Your patch file should be
-   generated using either '<code>diff -c</code>' or '<code>diff -u</code>' against the
-   latest CVS tree. To submit your patch, send Email to <code>new-httpd@apache.org</code>
-   with a <code>Subject:</code> line that starts with <code>[PATCH]</code> and
+   generated using either '<CODE>diff -c</CODE>' or '<CODE>diff -u</CODE>' against the
+   latest CVS tree. To submit your patch, send Email to <CODE>new-httpd@apache.org</CODE>
+   with a <CODE>Subject:</CODE> line that starts with <CODE>[PATCH]</CODE> and
    includes a general description of the patch. In the body of the message, the
    patch should be clearly described and then included at the end of the message.
    If the patch-file is long, you can note a URL to the file instead of the file
diff --git a/htdocs/manual/misc/client_block_api.html b/htdocs/manual/misc/client_block_api.html
index e70a8284fc..c451d19fd9 100644
--- a/htdocs/manual/misc/client_block_api.html
+++ b/htdocs/manual/misc/client_block_api.html
@@ -61,7 +61,7 @@ accomplished while remaining backwards-compatible.</P>
     <CODE>ap_should_client_block()</CODE>.
     This will tell the module whether or not to read input. If it is 0,
     the module should assume that the input is of a non-entity type
-    (e.g. a GET request). A nonzero response indicates that the module
+    (<EM>e.g.</EM>, a GET request). A nonzero response indicates that the module
     should proceed (to step 3).
     This step also sends a 100 Continue response
     to HTTP/1.1 clients, so should not be called until the module
diff --git a/htdocs/manual/misc/compat_notes.html b/htdocs/manual/misc/compat_notes.html
index b62c204b25..25c17558e4 100644
--- a/htdocs/manual/misc/compat_notes.html
+++ b/htdocs/manual/misc/compat_notes.html
@@ -86,7 +86,7 @@ client problems</A> page.
 
 <P>
 <LI>Apache's <CODE>&lt;VirtualHost&gt;</CODE> treats all addresses as
-    "optional" (i.e. the server should continue booting if it can't
+    "optional" (<EM>i.e.</EM>, the server should continue booting if it can't
     resolve the address).  Whereas in NCSA the default is to fail
     booting unless an added <CODE>optional</CODE> keyword is included.
 
diff --git a/htdocs/manual/misc/descriptors.html b/htdocs/manual/misc/descriptors.html
index 5841e10e1e..dadb7cc78d 100644
--- a/htdocs/manual/misc/descriptors.html
+++ b/htdocs/manual/misc/descriptors.html
@@ -26,7 +26,7 @@ network socket that it listens on, plus a handful of others.  Libraries
 that Apache uses may also require descriptors.  Normal programs don't
 open up many descriptors at all, and so there are some latent problems
 that you may experience should you start running Apache with many
-descriptors (i.e. with many virtual hosts).
+descriptors (<EM>i.e.</EM>, with many virtual hosts).
 
 <P>The operating system enforces a limit on the number of descriptors
 that a program can have open at a time.  There are typically three limits
diff --git a/htdocs/manual/misc/known_client_problems.html b/htdocs/manual/misc/known_client_problems.html
index db80d6e750..aee18cf9c3 100644
--- a/htdocs/manual/misc/known_client_problems.html
+++ b/htdocs/manual/misc/known_client_problems.html
@@ -245,19 +245,19 @@ BrowserMatch "Java1\.2beta[23]" nokeepalive
 is usually not a good idea; ideally it gets fixed, new betas or a final release
 comes out, and no one uses the broken old software anymore.  In theory.
 
-<h3><a name="content-type-persistence"><code>Content-Type</code> change
-is not noticed after reload</a></h3>
+<H3><A NAME="content-type-persistence"><CODE>Content-Type</CODE> change
+is not noticed after reload</A></H3>
 
-<p>Navigator (all versions?) will cache the <code>content-type</code>
+<P>Navigator (all versions?) will cache the <CODE>content-type</CODE>
 for an object "forever".  Using reload or shift-reload will not cause
-Navigator to notice a <code>content-type</code> change.  The only
+Navigator to notice a <CODE>content-type</CODE> change.  The only
 work-around is for the user to flush their caches (memory and disk).  By
-way of an example, some folks may be using an old <code>mime.types</code>
-file which does not map <code>.htm</code> to <code>text/html</code>,
-in this case Apache will default to sending <code>text/plain</code>.
-If the user requests the page and it is served as <code>text/plain</code>.
+way of an example, some folks may be using an old <CODE>mime.types</CODE>
+file which does not map <CODE>.htm</CODE> to <CODE>text/html</CODE>,
+in this case Apache will default to sending <CODE>text/plain</CODE>.
+If the user requests the page and it is served as <CODE>text/plain</CODE>.
 After the admin fixes the server, the user will have to flush their caches
-before the object will be shown with the correct <code>text/html</code>
+before the object will be shown with the correct <CODE>text/html</CODE>
 type.
 
 <!--#include virtual="footer.html" -->
diff --git a/htdocs/manual/misc/perf-dec.html b/htdocs/manual/misc/perf-dec.html
index 32245e0fbc..61e6314a70 100644
--- a/htdocs/manual/misc/perf-dec.html
+++ b/htdocs/manual/misc/perf-dec.html
@@ -211,7 +211,7 @@ TUNING
 
         tcp_keepinit            This is the amount of time a partially
                                 established connection will sit on the listen
-                                queue before timing out (e.g. if a client
+                                queue before timing out (<EM>e.g.</EM>, if a client
                                 sends a SYN but never answers our SYN/ACK).
                                 Partially established connections tie up slots
                                 on the listen queue.  If the queue starts to
diff --git a/htdocs/manual/misc/perf-tuning.html b/htdocs/manual/misc/perf-tuning.html
index 8e6178bd03..9ab35a0340 100644
--- a/htdocs/manual/misc/perf-tuning.html
+++ b/htdocs/manual/misc/perf-tuning.html
@@ -359,7 +359,7 @@ mutex.  Unfortunately SysV-style semaphores have some bad side-effects.
 One is that it's possible Apache will die without cleaning up the semaphore
 (see the <CODE>ipcs(8)</CODE> man page).  The other is that the semaphore
 API allows for a denial of service attack by any CGIs running under the
-same uid as the webserver (i.e. all CGIs unless you use something
+same uid as the webserver (<EM>i.e.</EM>, all CGIs unless you use something
 like suexec or cgiwrapper).  For these reasons this method is not used
 on any architecture except IRIX (where the previous two are prohibitively
 expensive on most IRIX boxes).
@@ -447,13 +447,13 @@ timeout, but it doesn't prohibit it.  On systems without the timeout,
 Apache 1.2 induces many sockets stuck forever in the FIN_WAIT_2 state.
 In many cases this can be avoided by simply upgrading to the latest
 TCP/IP patches supplied by the vendor, in cases where the vendor has
-never released patches (i.e.  SunOS4 -- although folks with a source
+never released patches (<EM>i.e.</EM>,  SunOS4 -- although folks with a source
 license can patch it themselves) we have decided to disable this feature.
 
 <P>There are two ways of accomplishing this.  One is the
 socket option <CODE>SO_LINGER</CODE>.  But as fate would have it,
 this has never been implemented properly in most TCP/IP stacks.  Even
-on those stacks with a proper implementation (i.e. Linux 2.0.31) this
+on those stacks with a proper implementation (<EM>i.e.</EM>, Linux 2.0.31) this
 method proves to be more expensive (cputime) than the next solution.
 
 <P>For the most part, Apache implements this in a function called
@@ -610,7 +610,7 @@ connection.  If the connection was a keep-alive connection and the request
 being serviced was not the first request then the browser will quietly
 reissue the request on a new connection.  It has to do this because the
 server is always free to close a keep-alive connection in between requests
-(i.e. due to a timeout or because of a maximum number of requests).
+(<EM>i.e.</EM>, due to a timeout or because of a maximum number of requests).
 But, if the connection is closed before the first response has been
 received the typical browser will display a "document contains no data"
 dialogue (or a broken image icon).  This is done on the assumption that
@@ -750,7 +750,7 @@ can be deferred by defining <CODE>BUFFERED_LOGS</CODE>.  In this case
 up to <CODE>PIPE_BUF</CODE> bytes (a POSIX defined constant) of log entries
 are buffered before writing.  At no time does it split a log entry
 across a <CODE>PIPE_BUF</CODE> boundary because those writes may not
-be atomic.  (i.e. entries from multiple children could become mixed together).
+be atomic.  (<EM>i.e.</EM>, entries from multiple children could become mixed together).
 The code does it best to flush this buffer when a child dies.
 
 <P>The lingering close code causes four system calls: