coar 97/08/13 18:24:51
Modified: htdocs/manual/mod core.html
Log:
Some typos and other cleanup from Martin the doc-walloper.
(.htaccess changes reverted to generic htaccess after some
discussion.)
Submitted by: Martin Kraemer <[EMAIL PROTECTED]>
Reviewed by: Paul Sutton, Marc Slemko, Ken Coar
Revision Changes Path
1.71 +12 -12 apachen/htdocs/manual/mod/core.html
Index: core.html
===================================================================
RCS file: /export/home/cvs/apachen/htdocs/manual/mod/core.html,v
retrieving revision 1.70
retrieving revision 1.71
diff -u -r1.70 -r1.71
--- core.html 1997/08/06 20:21:16 1.70
+++ core.html 1997/08/14 01:24:49 1.71
@@ -457,7 +457,7 @@
<h2><A name="errordocument">ErrorDocument directive</A></h2>
<!--%plaintext <?INDEX {\tt ErrorDocument} directive> -->
<strong>Syntax:</strong> ErrorDocument <em>error-code document</em><br>
-<strong>Context</strong> server config, virtual host, directory,
.htaccess<br>
+<strong>Context:</strong> server config, virtual host, directory,
.htaccess<br>
<strong>Status:</strong> core<br>
<strong>Override:</strong> FileInfo<br>
<strong>Compatibility:</strong> The directory and .htaccess contexts
@@ -527,7 +527,7 @@
<h2><A name="files"><Files> directive</A></h2>
<strong>Syntax:</strong> <Files <em>filename</em>>
... </Files><br>
-<strong>Context:</strong> server config, virtual host, htaccess<br>
+<strong>Context:</strong> server config, virtual host, .htaccess<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> only available in Apache
1.2 and above.<p>
@@ -554,7 +554,7 @@
</pre>
would match most common Internet graphics formats. In Apache 1.3 and
-later, <a href="#filesmatch"><FilesMatch></a> is perferred,
+later, <a href="#filesmatch"><FilesMatch></a> is preferred,
however.
<p>Note that unlike <a
@@ -571,7 +571,7 @@
<h2><A name="filesmatch"><FilesMatch></A></h2>
<strong>Syntax:</strong> <FilesMatch <em>regex</em>>
... </Files><br>
-<strong>Context:</strong> server config, virtual host, htaccess<br>
+<strong>Context:</strong> server config, virtual host, .htaccess<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> only available in Apache
1.3 and above.<p>
@@ -745,7 +745,7 @@
<p><strong>Apache 1.2 and later</strong>: Set to "On" to enable
persistent connections, "Off" to disable. See also the <a
-href="#maxkeepaliverequests">MaxKeepAliveRequests</a> directive.</p>
+href="#maxkeepaliverequests">MaxKeepAliveRequests</a> directive.</p><hr>
<h2><a name="keepalivetimeout">KeepAliveTimeout directive</a></h2>
<strong>Syntax:</strong> KeepAliveTimeout <em>seconds</em><br>
@@ -794,7 +794,7 @@
The maximum length of the queue of pending connections. Generally no
tuning is needed or desired, however on some systems it is desirable
to increase this when under a TCP SYN flood attack. See
-the backlog parameter to the <code>listen(2)</code> system call.
+the backlog parameter to the <code>listen(2)</code> system call.</p><hr>
<h2><A name="limit"><Limit> directive</A></h2>
<!--%plaintext <?INDEX {\tt Limit} section directive> -->
@@ -854,7 +854,7 @@
<p>would match URLs that contained the substring "/extra/data" or
"/special/data". However, in Apache 1.3 and above, use of <a
-href="#locationmatch"><LocationMatch></a> is perferred.</p>
+href="#locationmatch"><LocationMatch></a> is preferred.</p>
<p>The <code>Location</code> functionality is especially useful when
combined with the <code><a
@@ -933,7 +933,7 @@
allowed per connection when <a href="#keepalive">KeepAlive</a> is
on. If it is set to "<code>0</code>", unlimited requests will be
allowed. We recommend that this setting be kept to a high value for
-maximum server performance.
+maximum server performance.</p><hr>
<h2><A name="maxrequestsperchild">MaxRequestsPerChild directive</A></h2>
<!--%plaintext <?INDEX {\tt MaxRequestsPerChild} directive> -->
@@ -1215,7 +1215,7 @@
<H2><A name="rlimit">RLimitCPU</A> <A NAME="rlimitcpu">directive</A></H2>
<!--%plaintext <?INDEX {\tt RLimitCPU} directive> -->
<strong>Syntax:</strong> RLimitCPU <em># or 'max'</em> <em>[# or
'max']</em><br>
-<strong>Default:</strong> <code>Unset uses operating system
defaults</code><br>
+<strong>Default:</strong> <e>Unset; uses operating system defaults</e><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> RLimitCPU is only available in Apache 1.2
and later<p>
@@ -1234,7 +1234,7 @@
<h2><A name="rlimitmem">RLimitMEM directive</A></h2>
<!--%plaintext <?INDEX {\tt RLimitMEM} directive> -->
<strong>Syntax:</strong> RLimitMEM <em># or 'max'</em> <em>[# or
'max']</em><br>
-<strong>Default:</strong> <code>Unset uses operating system
defaults</code><br>
+<strong>Default:</strong> <e>Unset; uses operating system defaults</e><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> RLimitMEM is only available in Apache 1.2
and later<p>
@@ -1253,7 +1253,7 @@
<h2><A name="rlimitnproc">RLimitNPROC directive</A></h2>
<!--%plaintext <?INDEX {\tt RLimitNPROC} directive> -->
<strong>Syntax:</strong> RLimitNPROC <em># or 'max'</em> <em>[# or
'max']</em><br>
-<strong>Default:</strong> <code>Unset uses operating system
defaults</code><br>
+<strong>Default:</strong> <e>Unset; uses operating system defaults</e><br>
<strong>Context:</strong> server config, virtual host<br>
<strong>Status:</strong> core<br>
<strong>Compatibility:</strong> RLimitNPROC is only available in Apache 1.2
and later<p>
@@ -1589,7 +1589,7 @@
</VirtualHost>
</code></blockquote>
-Each VirtualHost must correspond to a different IP address or a
+Each VirtualHost must correspond to a different IP address, different port
number or a
different host name for the server, in the latter case the server
machine must be configured to accept IP packets for multiple
addresses. (If the machine does not have multiple network interfaces,
