diff options
| -rw-r--r-- | docs/manual/mod/mod_alias.html | 6 | ||||
| -rw-r--r-- | docs/manual/mod/mod_example.html | 2 | ||||
| -rw-r--r-- | docs/manual/mod/mod_imap.html | 2 | ||||
| -rw-r--r-- | docs/manual/mod/mod_isapi.html | 2 | ||||
| -rw-r--r-- | docs/manual/mod/mod_speling.html | 4 | ||||
| -rw-r--r-- | docs/manual/platform/perf-hp.html | 2 | ||||
| -rw-r--r-- | docs/manual/sections.html | 2 | ||||
| -rw-r--r-- | docs/manual/sections.html.en | 2 | ||||
| -rw-r--r-- | docs/manual/vhosts/details.html | 2 | ||||
| -rw-r--r-- | docs/manual/vhosts/examples.html | 4 |
10 files changed, 14 insertions, 14 deletions
diff --git a/docs/manual/mod/mod_alias.html b/docs/manual/mod/mod_alias.html index cb66b64798..82b025fbaf 100644 --- a/docs/manual/mod/mod_alias.html +++ b/docs/manual/mod/mod_alias.html @@ -76,7 +76,7 @@ See also <A HREF="#scriptalias">ScriptAlias</A>. <strong>Compatibility:</strong> Available in Apache 1.3 and later </P> -<p>This directive is equivilent to <a href="#alias">Alias</a>, but +<p>This directive is equivalent to <a href="#alias">Alias</a>, but makes use of standard regular expressions, instead of simple prefix matching. The supplied regular expression is matched against the URL, and if it matches, the server will substitute any parenthesized @@ -162,7 +162,7 @@ the function <code>send_error_response</code> in http_protocol.c). <strong>Compatibility:</strong> Available in Apache 1.3 and later </P> -<p>This directive is equivilent to <a href="#alias">Redirect</a>, but +<p>This directive is equivalent to <a href="#alias">Redirect</a>, but makes use of standard regular expressions, instead of simple prefix matching. The supplied regular expression is matched against the URL, and if it matches, the server will substitute any parenthesized @@ -241,7 +241,7 @@ run the script /web/cgi-bin/foo. <strong>Compatibility:</strong> Available in Apache 1.3 and later </P> -<p>This directive is equivilent to <a href="#scriptalias">ScriptAlias</a>, but +<p>This directive is equivalent to <a href="#scriptalias">ScriptAlias</a>, but makes use of standard regular expressions, instead of simple prefix matching. The supplied regular expression is matched against the URL, and if it matches, the server will substitute any parenthesized diff --git a/docs/manual/mod/mod_example.html b/docs/manual/mod/mod_example.html index 3501fcb8a6..26004e37c0 100644 --- a/docs/manual/mod/mod_example.html +++ b/docs/manual/mod/mod_example.html @@ -32,7 +32,7 @@ </P> <P> The main file is <CODE>mod_example.c</CODE>, which illustrates all - the different callback mechanisms and call syntaces. By no means does + the different callback mechanisms and call syntaxes. By no means does an add-on module need to include routines for all of the callbacks - quite the contrary! </P> diff --git a/docs/manual/mod/mod_imap.html b/docs/manual/mod/mod_imap.html index 40bac8da80..08ca89a18c 100644 --- a/docs/manual/mod/mod_imap.html +++ b/docs/manual/mod/mod_imap.html @@ -272,7 +272,7 @@ rect mailto:nate@tripod.com 100,150 200,0 "Bugs?" <br> <h2>Referencing your mapfile</h2> <blockquote><code> -<A HREF="/maps/imagmap1.map"> <br> +<A HREF="/maps/imagemap1.map"> <br> <IMG ISMAP SRC="/images/imagemap1.gif"> <br> </A> </code></blockquote><p> diff --git a/docs/manual/mod/mod_isapi.html b/docs/manual/mod/mod_isapi.html index 5fde08c1a7..e3d87e8c71 100644 --- a/docs/manual/mod/mod_isapi.html +++ b/docs/manual/mod/mod_isapi.html @@ -47,7 +47,7 @@ <p>Apache's ISAPI implementation conforms to all of the ISAPI 2.0 specification, except for the "Microsoft-specific" extensions dealing - with ascynchronous I/O. Apache's I/O model does not allow asynchronous + with asynchronous I/O. Apache's I/O model does not allow asynchronous reading and writing in a manner that the ISAPI could access. If an ISA tries to access async I/O, a message will be place in the error log, to help with debugging. diff --git a/docs/manual/mod/mod_speling.html b/docs/manual/mod/mod_speling.html index ce47d523dc..3ece21704c 100644 --- a/docs/manual/mod/mod_speling.html +++ b/docs/manual/mod/mod_speling.html @@ -16,7 +16,7 @@ <P> This module is contained in the <code>mod_speling.c</code> file, and is <strong>not</strong> compiled in by default. - It attemps to correct misspellings of + It attempts to correct misspellings of URLs that users might have entered, by ignoring capitalization and by allowing up to one misspelling.<br> This catches the majority of misspelled requests. An automatic @@ -76,7 +76,7 @@ correction will have an impact on the server's performance when many spelling corrections have to be performed at the same time. <LI>the document trees should not contain sensitive files which could - be matched inadvertedly, by a spelling "correction". + be matched inadvertently, by a spelling "correction". <LI>the module is unable to correct misspelled user names (as in <code>http://my.host/~apahce/</code>), just file names or directory names. diff --git a/docs/manual/platform/perf-hp.html b/docs/manual/platform/perf-hp.html index 0bf286747d..23ab1c250a 100644 --- a/docs/manual/platform/perf-hp.html +++ b/docs/manual/platform/perf-hp.html @@ -74,7 +74,7 @@ ftp://ftp.cup.hp.com/dist/networking/misc/listenq</A>. If folks are running Apache on a PA-8000 based system, they should consider "chatr'ing" the Apache executable to have a large page size. This would be "chatr +pi L <binary>." The GID of the running executable -must have MLOCK priviledges. Setprivgrp(1m) should be consulted for +must have MLOCK privileges. Setprivgrp(1m) should be consulted for assigning MLOCK. The change can be validated by running Glance and examining the memory regions of the server(s) to make sure that they show a non-trivial fraction of the text segment being locked. diff --git a/docs/manual/sections.html b/docs/manual/sections.html index 9a29051e59..6951e7cdbe 100644 --- a/docs/manual/sections.html +++ b/docs/manual/sections.html @@ -117,7 +117,7 @@ But a notable exception is: </ul> Note also that modifying .htaccess parsing during Location doesn't do -anything because .htaccess parsing has already occured. +anything because .htaccess parsing has already occurred. <p> diff --git a/docs/manual/sections.html.en b/docs/manual/sections.html.en index 9a29051e59..6951e7cdbe 100644 --- a/docs/manual/sections.html.en +++ b/docs/manual/sections.html.en @@ -117,7 +117,7 @@ But a notable exception is: </ul> Note also that modifying .htaccess parsing during Location doesn't do -anything because .htaccess parsing has already occured. +anything because .htaccess parsing has already occurred. <p> diff --git a/docs/manual/vhosts/details.html b/docs/manual/vhosts/details.html index 0e992170c3..e64973edd7 100644 --- a/docs/manual/vhosts/details.html +++ b/docs/manual/vhosts/details.html @@ -299,7 +299,7 @@ taken to be a proxy request. <li>A <code>_default_</code> vhost catches a request only if there is no other vhost with a matching IP address <em>and</em> a matching port - number for the request. The request is only catched if the port number + number for the request. The request is only caught if the port number to which the client sent the request matches the port number of your <code>_default_</code> vhost which is your standard <code>Port</code> by default. A wildcard port can be specified (i.e. diff --git a/docs/manual/vhosts/examples.html b/docs/manual/vhosts/examples.html index c537f06dbb..fbf159ecaf 100644 --- a/docs/manual/vhosts/examples.html +++ b/docs/manual/vhosts/examples.html @@ -91,7 +91,7 @@ ... </VirtualHost> </pre> - The main server can never catch a request, because all IP address + The main server can never catch a request, because all IP addresses of our machine are in use for IP-based virtual hosts (only <samp>localhost</samp> requests can hit the main server). </blockquote> @@ -134,7 +134,7 @@ </Directory> </VirtualHost> </pre> - The main server can never catch a request, because all IP addresss + The main server can never catch a request, because all IP addresses (apart from <samp>localhost</samp>) of our machine are in use for IP-based virtual hosts. The web server can only be reached on the first address through port 80 and the proxy only on the second address through port 8080. |