</section>
<section><title>Other sorts of resources -- cleanup functions</title>
- <p>More text goes here. Describe the the cleanup primitives in terms of
+ <p>More text goes here. Describe the cleanup primitives in terms of
which the file stuff is implemented; also, <code>spawn_process</code>.</p>
<p>Pool cleanups live until <code>clear_pool()</code> is called:
<summary>
<p>Apache 2.0 uses <a href="http://www.doxygen.org/">Doxygen</a> to
- document the APIs and global variables in the the code. This will explain
+ document the APIs and global variables in the code. This will explain
the basics of how to document using Doxygen.</p>
</summary>
directive explicitly to <code>Off</code> allows group authorization
to be passed on to lower level modules (as defined in the
<code>modules.c</code> file) if there is no group found
- for the the supplied userID. If there are any groups
+ for the supplied userID. If there are any groups
specified, the usual checks will be applied and a failure will
give an Authentication Required reply.</p>
<p>The status code and message are the usual HTTP things
(e.g. <code>200</code> and <code>OK</code>). The response header names are
encoded the same way the request header names are. See header_encoding above
- for details about how the the codes are distinguished from the strings.<br />
+ for details about how the codes are distinguished from the strings.<br />
The codes for common headers are:</p>
<table>
<tr><td>Name</td><td>Code value</td></tr>
<title>Third Party Modules</title>
<p>Many third-party modules designed for version 2.0 will work
- unchanged with the the Apache HTTP Server version 2.2. But all
+ unchanged with the Apache HTTP Server version 2.2. But all
modules must be recompiled before being loaded.</p>
</section>