Another pass at the normalisation of the HTML tags. Some

	corrections coming up.


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

1 files changed, 9 insertions, 9 deletions

diff --git a/docs/manual/invoking.html b/docs/manual/invoking.html
index d718c2f89c..1eff24f2d1 100644
--- a/docs/manual/invoking.html
+++ b/docs/manual/invoking.html
@@ -13,9 +13,9 @@
  ALINK="#FF0000"
 >
 <!--#include virtual="header.html" -->
-<h1 ALIGN="CENTER">Starting Apache</H1>
+<H1 ALIGN="CENTER">Starting Apache</H1>
 
-<h2>Invoking Apache</h2>
+<H2>Invoking Apache</H2>
 The <CODE>httpd</CODE> program is usually run as a daemon which executes
 continuously, handling requests.  It is possible to invoke Apache by
 the Internet daemon <CODE>inetd</CODE> each time a connection to the HTTP
@@ -23,7 +23,7 @@ service is made (use the
 <A HREF="mod/core.html#servertype">ServerType</A> directive)
 but this is not recommended.
 
-<h2>Command line options</h2>
+<H2>Command line options</H2>
 The following options are recognized on the httpd command line:
 <DL>
 <DT><CODE>-d</CODE> <EM>serverroot</EM>
@@ -63,7 +63,7 @@ places where the directive is valid. (New in Apache 1.2)
 <DD>Print a list of the httpd options, and then exit.
 </DL>
 
-<h2>Configuration files</h2>
+<H2>Configuration files</H2>
 The server will read three files for configuration directives. Any directive
 may appear in any of these files. The the names of these files are taken
 to be relative to the server root; this is set by the
@@ -92,15 +92,15 @@ The server also reads a file containing mime document types; the filename
 is set by the <A HREF="mod/mod_mime.html#typesconfig">TypesConfig</A> directive,
 and is <CODE>conf/mime.types</CODE> by default.
 
-<h2>Log files</h2>
-<h3>security warning</h3>
+<H2>Log files</H2>
+<H3>security warning</H3>
 Anyone who can write to the directory where Apache is writing a
 log file can almost certainly gain access to the uid that the server is
 started as, which is normally root.  Do <EM>NOT</EM> give people write
 access to the directory the logs are stored in without being aware of
 the consequences; see the <A HREF="misc/security_tips.html">security tips</A>
 document for details.
-<h3>pid file</h3>
+<H3>pid file</H3>
 On daemon startup, it saves the process id of the parent httpd process to
 the file <CODE>logs/httpd.pid</CODE>. This filename can be changed with the
 <A HREF="mod/core.html#pidfile">PidFile</A> directive. The process-id is for
@@ -112,13 +112,13 @@ see the <A HREF="stopping.html">Stopping and Restarting</A> page.
 If the process dies (or is killed) abnormally, then it will be necessary to
 kill the children httpd processes.
 
-<h3>Error log</h3>
+<H3>Error log</H3>
 The server will log error messages to a log file, <CODE>logs/error_log</CODE>
 by default. The filename can be set using the
 <A HREF="mod/core.html#errorlog">ErrorLog</A> directive; different error logs can
 be set for different <A HREF="mod/core.html#virtualhost">virtual hosts</A>.
 
-<h3>Transfer log</h3>
+<H3>Transfer log</H3>
 The server will typically log each request to a transfer file,
 <CODE>logs/access_log</CODE> by default. The filename can be set using a
 <A HREF="mod/mod_log_config.html#transferlog">TransferLog</A> directive; different