You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by nd...@apache.org on 2003/04/24 00:43:42 UTC
cvs commit: httpd-2.0/docs/manual content-negotiation.html.en content-negotiation.xml glossary.html.en glossary.xml index.html.en index.xml install.html.en install.xml logs.html.en logs.xml sections.html.en sections.xml stopping.html.de stopping.html.en stopping.xml stopping.xml.de suexec.html.en suexec.xml urlmapping.html.en urlmapping.xml
nd 2003/04/23 15:43:42
Modified: docs/manual Tag: APACHE_2_0_BRANCH
content-negotiation.html.en content-negotiation.xml
glossary.html.en glossary.xml index.html.en
index.xml install.html.en install.xml logs.html.en
logs.xml sections.html.en sections.xml
stopping.html.de stopping.html.en stopping.xml
stopping.xml.de suexec.html.en suexec.xml
urlmapping.html.en urlmapping.xml
Log:
typos, inconsistencies ...
Revision Changes Path
No revision
No revision
1.36.2.4 +4 -4 httpd-2.0/docs/manual/content-negotiation.html.en
Index: content-negotiation.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/content-negotiation.html.en,v
retrieving revision 1.36.2.3
retrieving revision 1.36.2.4
diff -u -r1.36.2.3 -r1.36.2.4
--- content-negotiation.html.en 6 Apr 2003 18:24:40 -0000 1.36.2.3
+++ content-negotiation.html.en 23 Apr 2003 22:43:40 -0000 1.36.2.4
@@ -451,9 +451,9 @@
Variant" or "Multiple Choices" response to the client. To avoid
these error messages, it is possible to configure Apache to ignore
the Accept-language in these cases and provide a document that
- does not explictly match the client's request. The <code class="directive"><a href="./mod/mod_negotiation.html#forcelanguagepriority">ForceLanguagePriority</a></code>
+ does not explicitly match the client's request. The <code class="directive"><a href="./mod/mod_negotiation.html#forcelanguagepriority">ForceLanguagePriority</a></code>
directive can be used to override one or both of these error
- messages and subsitute the servers judgement in the form of the
+ messages and substitute the servers judgement in the form of the
<code class="directive"><a href="./mod/mod_negotiation.html#languagepriority">LanguagePriority</a></code>
directive.</p>
@@ -590,8 +590,8 @@
</tr>
</table>
- <p>Looking at the table above you will notice that it is always
- possible to use the name without any extensions in an hyperlink
+ <p>Looking at the table above, you will notice that it is always
+ possible to use the name without any extensions in a hyperlink
(<em>e.g.</em>, <code>foo</code>). The advantage is that you
can hide the actual type of a document rsp. file and can change
it later, <em>e.g.</em>, from <code>html</code> to
1.1.2.5 +4 -4 httpd-2.0/docs/manual/content-negotiation.xml
Index: content-negotiation.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/content-negotiation.xml,v
retrieving revision 1.1.2.4
retrieving revision 1.1.2.5
diff -u -r1.1.2.4 -r1.1.2.5
--- content-negotiation.xml 16 Apr 2003 00:22:43 -0000 1.1.2.4
+++ content-negotiation.xml 23 Apr 2003 22:43:40 -0000 1.1.2.5
@@ -435,10 +435,10 @@
Variant" or "Multiple Choices" response to the client. To avoid
these error messages, it is possible to configure Apache to ignore
the Accept-language in these cases and provide a document that
- does not explictly match the client's request. The <directive
+ does not explicitly match the client's request. The <directive
module="mod_negotiation">ForceLanguagePriority</directive>
directive can be used to override one or both of these error
- messages and subsitute the servers judgement in the form of the
+ messages and substitute the servers judgement in the form of the
<directive module="mod_negotiation">LanguagePriority</directive>
directive.</p>
@@ -577,8 +577,8 @@
</tr>
</table>
- <p>Looking at the table above you will notice that it is always
- possible to use the name without any extensions in an hyperlink
+ <p>Looking at the table above, you will notice that it is always
+ possible to use the name without any extensions in a hyperlink
(<em>e.g.</em>, <code>foo</code>). The advantage is that you
can hide the actual type of a document rsp. file and can change
it later, <em>e.g.</em>, from <code>html</code> to
1.4.2.4 +7 -7 httpd-2.0/docs/manual/glossary.html.en
Index: glossary.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/glossary.html.en,v
retrieving revision 1.4.2.3
retrieving revision 1.4.2.4
diff -u -r1.4.2.3 -r1.4.2.4
--- glossary.html.en 9 Apr 2003 15:15:52 -0000 1.4.2.3
+++ glossary.html.en 23 Apr 2003 22:43:40 -0000 1.4.2.4
@@ -116,7 +116,7 @@
Index</a></dd>
<dt><a name="dynamicsharedobject">Dynamic Shared Object</a> <a name="dso">(DSO)</a></dt> <dd><a href="#module">Modules</a> compiled
-seperately from the Apache httpd binary that can be loaded on-demand.<br />
+separately from the Apache httpd binary that can be loaded on-demand.<br />
See: <a href="dso.html">Dynamic Shared Object Support</a></dd>
<dt><a name="environmentvariable">Environment Variable</a> <a name="env-variable">(env-variable)</a></dt>
@@ -139,7 +139,7 @@
data that is sent or received by the server. Input filters process
data sent by the client to the server, while output filters process
documents on the server before they are sent to the client. For
-examle, the <code>INCLUDES</code> output filter processes documents
+example, the <code>INCLUDES</code> output filter processes documents
for <a href="#ssi">Server Side Includes</a>.<br /> See: <a href="filter.html">Filters</a></dd>
<dt><a name="fully-qualifieddomain-name">Fully-Qualified
@@ -177,7 +177,7 @@
<dt><a name="hypertexttransferprotocol">HyperText Transfer
Protocol</a> <a name="http">(HTTP)</a></dt> <dd>The standard
transmission protocol used on the World Wide Web. Apache implements
-version 1.1 of the protocol, refered to as HTTP/1.1 and defined by <a href="http://ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</dd>
+version 1.1 of the protocol, referred to as HTTP/1.1 and defined by <a href="http://ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</dd>
<dt><a name="https">HTTPS</a></dt>
<dd>The HyperText Transport Protocol (Secure), the standard encrypted
@@ -206,7 +206,7 @@
program. Much of Apache's functionality is contained in modules that
you can choose to include or exclude. Modules that are compiled into
the Apache httpd binary are called <em>static modules</em>, while
-modules that are stored seperately and can be optionally loaded at
+modules that are stored separately and can be optionally loaded at
run-time are called <em>dynamic modules</em> or <a href="#dso">DSOs</a>. Modules that are included by default are called
<em>base modules</em>. Many modules are available for Apache that are
not distributed as part of the Apache HTTP Server <a href="#tarball">tarball</a>. These are referred to as <em>third-party
@@ -218,7 +218,7 @@
Module Magic Number is a constant defined in the Apache source code
that is associated with binary compatibility of modules. It is changed
when internal Apache structures, function calls and other significant
-parts of API change in such a way that binary compatiblity cannot be
+parts of API change in such a way that binary compatibility cannot be
guaranteed any more. On MMN change, all third party modules have to be
at least recompiled, sometimes even slightly changed in order to work
with the new version of Apache.
@@ -250,7 +250,7 @@
from the origin server each time, thereby reducing response time.<br />
See: <a href="mod/mod_proxy.html">mod_proxy</a></dd>
-<dt><a name="publickey">Public Key</a></dt> <dd>The publically
+<dt><a name="publickey">Public Key</a></dt> <dd>The publicly
available key in a <a name="publickeycryptography">Public Key
Cryptography</a> system, used to encrypt messages bound for its owner
and to decrypt signatures made by its owner.<br />
@@ -260,7 +260,7 @@
<dd>The study and application of asymmetric encryption systems, which
use one key for encryption and another for decryption. A corresponding
pair of such keys constitutes a key pair. Also called Asymmetric
-Crypography.<br /> See: <a href="ssl/">SSL/TLS Encryption</a></dd>
+Cryptography.<br /> See: <a href="ssl/">SSL/TLS Encryption</a></dd>
<dt><a name="regularexpresion">Regular Expression</a> <a name="regex">(Regex)</a></dt> <dd>A way of
describing a pattern in text - for example, "all the words that begin with the
1.3.2.4 +7 -7 httpd-2.0/docs/manual/glossary.xml
Index: glossary.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/glossary.xml,v
retrieving revision 1.3.2.3
retrieving revision 1.3.2.4
diff -u -r1.3.2.3 -r1.3.2.4
--- glossary.xml 16 Apr 2003 00:22:43 -0000 1.3.2.3
+++ glossary.xml 23 Apr 2003 22:43:40 -0000 1.3.2.4
@@ -119,7 +119,7 @@
<dt><a name="dynamicsharedobject">Dynamic Shared Object</a> <a
name="dso">(DSO)</a></dt> <dd><a href="#module">Modules</a> compiled
-seperately from the Apache httpd binary that can be loaded on-demand.<br />
+separately from the Apache httpd binary that can be loaded on-demand.<br />
See: <a href="dso.html">Dynamic Shared Object Support</a></dd>
<dt><a name="environmentvariable">Environment Variable</a> <a
@@ -143,7 +143,7 @@
data that is sent or received by the server. Input filters process
data sent by the client to the server, while output filters process
documents on the server before they are sent to the client. For
-examle, the <code>INCLUDES</code> output filter processes documents
+example, the <code>INCLUDES</code> output filter processes documents
for <a href="#ssi">Server Side Includes</a>.<br /> See: <a
href="filter.html">Filters</a></dd>
@@ -185,7 +185,7 @@
<dt><a name="hypertexttransferprotocol">HyperText Transfer
Protocol</a> <a name="http">(HTTP)</a></dt> <dd>The standard
transmission protocol used on the World Wide Web. Apache implements
-version 1.1 of the protocol, refered to as HTTP/1.1 and defined by <a
+version 1.1 of the protocol, referred to as HTTP/1.1 and defined by <a
href="http://ietf.org/rfc/rfc2616.txt">RFC 2616</a>.</dd>
<dt><a name="https">HTTPS</a></dt>
@@ -218,7 +218,7 @@
program. Much of Apache's functionality is contained in modules that
you can choose to include or exclude. Modules that are compiled into
the Apache httpd binary are called <em>static modules</em>, while
-modules that are stored seperately and can be optionally loaded at
+modules that are stored separately and can be optionally loaded at
run-time are called <em>dynamic modules</em> or <a
href="#dso">DSOs</a>. Modules that are included by default are called
<em>base modules</em>. Many modules are available for Apache that are
@@ -233,7 +233,7 @@
Module Magic Number is a constant defined in the Apache source code
that is associated with binary compatibility of modules. It is changed
when internal Apache structures, function calls and other significant
-parts of API change in such a way that binary compatiblity cannot be
+parts of API change in such a way that binary compatibility cannot be
guaranteed any more. On MMN change, all third party modules have to be
at least recompiled, sometimes even slightly changed in order to work
with the new version of Apache.
@@ -266,7 +266,7 @@
from the origin server each time, thereby reducing response time.<br />
See: <a href="mod/mod_proxy.html">mod_proxy</a></dd>
-<dt><a name="publickey">Public Key</a></dt> <dd>The publically
+<dt><a name="publickey">Public Key</a></dt> <dd>The publicly
available key in a <a name="publickeycryptography">Public Key
Cryptography</a> system, used to encrypt messages bound for its owner
and to decrypt signatures made by its owner.<br />
@@ -276,7 +276,7 @@
<dd>The study and application of asymmetric encryption systems, which
use one key for encryption and another for decryption. A corresponding
pair of such keys constitutes a key pair. Also called Asymmetric
-Crypography.<br /> See: <a href="ssl/">SSL/TLS Encryption</a></dd>
+Cryptography.<br /> See: <a href="ssl/">SSL/TLS Encryption</a></dd>
<dt><a name="regularexpresion">Regular Expression</a> <a
name="regex">(Regex)</a></dt> <dd>A way of
1.44.2.5 +1 -1 httpd-2.0/docs/manual/index.html.en
Index: index.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/index.html.en,v
retrieving revision 1.44.2.4
retrieving revision 1.44.2.5
diff -u -r1.44.2.4 -r1.44.2.5
--- index.html.en 9 Apr 2003 12:55:56 -0000 1.44.2.4
+++ index.html.en 23 Apr 2003 22:43:40 -0000 1.44.2.5
@@ -23,7 +23,7 @@
<table id="indextable"><tr><td class="col1"><div class="category"><h2><a name="release" id="release">Release Notes</a></h2>
<ul><li><a href="new_features_2_0.html">New features with Apache 2.0</a></li>
<li><a href="upgrading.html">Upgrading to 2.0 from 1.3</a></li>
-<li><a href="LICENSE">Apache License</a></li>
+<li><a href="license.html">Apache License</a></li>
</ul>
</div><div class="category"><h2><a name="manual" id="manual">Reference Manual</a></h2>
<ul><li><a href="install.html">Compiling and Installing</a></li>
1.1.2.4 +1 -1 httpd-2.0/docs/manual/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/index.xml,v
retrieving revision 1.1.2.3
retrieving revision 1.1.2.4
diff -u -r1.1.2.3 -r1.1.2.4
--- index.xml 16 Apr 2003 00:22:43 -0000 1.1.2.3
+++ index.xml 23 Apr 2003 22:43:40 -0000 1.1.2.4
@@ -10,7 +10,7 @@
<category id="release"><title>Release Notes</title>
<page href="new_features_2_0.html">New features with Apache 2.0</page>
<page href="upgrading.html">Upgrading to 2.0 from 1.3</page>
- <page href="LICENSE">Apache License</page>
+ <page href="license.html">Apache License</page>
</category>
<category id="manual"><title>Reference Manual</title>
1.56.2.6 +2 -2 httpd-2.0/docs/manual/install.html.en
Index: install.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/install.html.en,v
retrieving revision 1.56.2.5
retrieving revision 1.56.2.6
diff -u -r1.56.2.5 -r1.56.2.6
--- install.html.en 28 Feb 2003 15:03:40 -0000 1.56.2.5
+++ install.html.en 23 Apr 2003 22:43:40 -0000 1.56.2.6
@@ -518,12 +518,12 @@
<dt><code>--with-berkeley-db[=<em>path</em>]</code></dt>
<dd>If no <em>path</em> is specified, Apache will search for the
-include files and libraries in the usual search paths. An explict
+include files and libraries in the usual search paths. An explicit
<em>path</em> will cause Apache to look in
<em>path</em><code>/lib</code> and
<em>path</em><code>/include</code> for the relevant files. Finally,
the <em>path</em> may specify specific include and library paths
-seperated by a colon.</dd>
+separated by a colon.</dd>
</dl>
1.11.2.7 +2 -2 httpd-2.0/docs/manual/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/install.xml,v
retrieving revision 1.11.2.6
retrieving revision 1.11.2.7
diff -u -r1.11.2.6 -r1.11.2.7
--- install.xml 16 Apr 2003 00:22:43 -0000 1.11.2.6
+++ install.xml 23 Apr 2003 22:43:40 -0000 1.11.2.7
@@ -510,12 +510,12 @@
<dt><code>--with-berkeley-db[=<em>path</em>]</code></dt>
<dd>If no <em>path</em> is specified, Apache will search for the
-include files and libraries in the usual search paths. An explict
+include files and libraries in the usual search paths. An explicit
<em>path</em> will cause Apache to look in
<em>path</em><code>/lib</code> and
<em>path</em><code>/include</code> for the relevant files. Finally,
the <em>path</em> may specify specific include and library paths
-seperated by a colon.</dd>
+separated by a colon.</dd>
</dl>
</section>
1.18.2.4 +2 -2 httpd-2.0/docs/manual/logs.html.en
Index: logs.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/logs.html.en,v
retrieving revision 1.18.2.3
retrieving revision 1.18.2.4
diff -u -r1.18.2.3 -r1.18.2.4
--- logs.html.en 1 Jan 2003 02:01:38 -0000 1.18.2.3
+++ logs.html.en 23 Apr 2003 22:43:40 -0000 1.18.2.4
@@ -19,7 +19,7 @@
<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs-project/">Documentation</a> > <a href="./">Version 2.0</a></div><div id="page-content"><div id="preamble"><h1>Log Files</h1>
<p>In order to effectively manage a web server, it is necessary
to get feedback about the activity and performance of the
- server as well as any problems that may be occuring. The Apache
+ server as well as any problems that may be occurring. The Apache
HTTP Server provides very comprehensive and flexible logging
capabilities. This document describes how to configure its
logging capabilities, and how to understand what the logs
@@ -303,7 +303,7 @@
<div class="example"><p><code>
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-agent}i\"" combined<br />
- CustomLog log/acces_log combined
+ CustomLog log/access_log combined
</code></p></div>
<p>This format is exactly the same as the Common Log Format,
1.6.2.4 +2 -2 httpd-2.0/docs/manual/logs.xml
Index: logs.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/logs.xml,v
retrieving revision 1.6.2.3
retrieving revision 1.6.2.4
diff -u -r1.6.2.3 -r1.6.2.4
--- logs.xml 16 Apr 2003 00:22:43 -0000 1.6.2.3
+++ logs.xml 23 Apr 2003 22:43:40 -0000 1.6.2.4
@@ -9,7 +9,7 @@
<summary>
<p>In order to effectively manage a web server, it is necessary
to get feedback about the activity and performance of the
- server as well as any problems that may be occuring. The Apache
+ server as well as any problems that may be occurring. The Apache
HTTP Server provides very comprehensive and flexible logging
capabilities. This document describes how to configure its
logging capabilities, and how to understand what the logs
@@ -308,7 +308,7 @@
<example>
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\"
\"%{User-agent}i\"" combined<br />
- CustomLog log/acces_log combined
+ CustomLog log/access_log combined
</example>
<p>This format is exactly the same as the Common Log Format,
1.20.2.2 +1 -1 httpd-2.0/docs/manual/sections.html.en
Index: sections.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/sections.html.en,v
retrieving revision 1.20.2.1
retrieving revision 1.20.2.2
diff -u -r1.20.2.1 -r1.20.2.2
--- sections.html.en 11 Dec 2002 22:27:02 -0000 1.20.2.1
+++ sections.html.en 23 Apr 2003 22:43:40 -0000 1.20.2.2
@@ -196,7 +196,7 @@
matches any sequence of characters, "?" matches any single character,
and "[<em>seq</em>]" matches any character in <em>seq</em>. The "/"
character will not be matched by any wildcard; it must be specified
-explictly.</p>
+explicitly.</p>
<p>If even more flexible matching is required, each
container has a regular-expression (regex) counterpart <code class="directive"><a href="./mod/core.html#directorymatch"><DirectoryMatch></a></code>, <code class="directive"><a href="./mod/core.html#filesmatch"><FilesMatch></a></code>, and <code class="directive"><a href="./mod/core.html#locationmatch"><LocationMatch></a></code> that allow
1.3.2.3 +1 -1 httpd-2.0/docs/manual/sections.xml
Index: sections.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/sections.xml,v
retrieving revision 1.3.2.2
retrieving revision 1.3.2.3
diff -u -r1.3.2.2 -r1.3.2.3
--- sections.xml 16 Apr 2003 00:22:44 -0000 1.3.2.2
+++ sections.xml 23 Apr 2003 22:43:41 -0000 1.3.2.3
@@ -204,7 +204,7 @@
matches any sequence of characters, "?" matches any single character,
and "[<em>seq</em>]" matches any character in <em>seq</em>. The "/"
character will not be matched by any wildcard; it must be specified
-explictly.</p>
+explicitly.</p>
<p>If even more flexible matching is required, each
container has a regular-expression (regex) counterpart <directive
1.1.2.6 +3 -3 httpd-2.0/docs/manual/stopping.html.de
Index: stopping.html.de
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/stopping.html.de,v
retrieving revision 1.1.2.5
retrieving revision 1.1.2.6
diff -u -r1.1.2.5 -r1.1.2.6
--- stopping.html.de 18 Dec 2002 22:09:38 -0000 1.1.2.5
+++ stopping.html.de 23 Apr 2003 22:43:41 -0000 1.1.2.6
@@ -45,9 +45,9 @@
Elternprozess, dessen PID im <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code> steht. Das hei�t, Sie
sollten es niemals n�tig haben, einem anderen Prozess, als dem
Elternprozess, ein Signal zu senden. Es gibt drei Signale, die Sie an den
- Elternprozess senden k�nnen: <a href="#term"><code>TERM</code></a>,
- <a href="#hup"><code>HUP</code></a> und
- <a href="#graceful"><code>USR1</code></a>, die nachfolgend beschrieben
+ Elternprozess senden k�nnen: <code><a href="#term">TERM</a></code>,
+ <code><a href="#hup">HUP</a></code> und
+ <code><a href="#graceful">USR1</a></code>, die nachfolgend beschrieben
werden.</p>
<p>Um dem Elternprozess ein Signal zu senden, verwenden Sie einen
1.31.2.5 +3 -1 httpd-2.0/docs/manual/stopping.html.en
Index: stopping.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/stopping.html.en,v
retrieving revision 1.31.2.4
retrieving revision 1.31.2.5
diff -u -r1.31.2.4 -r1.31.2.5
--- stopping.html.en 18 Dec 2002 20:35:40 -0000 1.31.2.4
+++ stopping.html.en 23 Apr 2003 22:43:41 -0000 1.31.2.5
@@ -43,7 +43,9 @@
whose pid is in the <code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code>. That is to say you
shouldn't ever need to send signals to any process except the
parent. There are three signals that you can send the parent:
- <code>TERM</code>, <code>HUP</code>, and <code>USR1</code>, which
+ <code><a href="#term">TERM</a></code>,
+ <code><a href="#hup">HUP</a></code>, and
+ <code><a href="#graceful">USR1</a></code>, which
will be described in a moment.</p>
<p>To send a signal to the parent you should issue a command
1.2.2.6 +3 -1 httpd-2.0/docs/manual/stopping.xml
Index: stopping.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/stopping.xml,v
retrieving revision 1.2.2.5
retrieving revision 1.2.2.6
diff -u -r1.2.2.5 -r1.2.2.6
--- stopping.xml 16 Apr 2003 00:22:44 -0000 1.2.2.5
+++ stopping.xml 23 Apr 2003 22:43:41 -0000 1.2.2.6
@@ -30,7 +30,9 @@
module="mpm_common">PidFile</directive>. That is to say you
shouldn't ever need to send signals to any process except the
parent. There are three signals that you can send the parent:
- <code>TERM</code>, <code>HUP</code>, and <code>USR1</code>, which
+ <code><a href="#term">TERM</a></code>,
+ <code><a href="#hup">HUP</a></code>, and
+ <code><a href="#graceful">USR1</a></code>, which
will be described in a moment.</p>
<p>To send a signal to the parent you should issue a command
1.1.2.8 +3 -3 httpd-2.0/docs/manual/stopping.xml.de
Index: stopping.xml.de
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/stopping.xml.de,v
retrieving revision 1.1.2.7
retrieving revision 1.1.2.8
diff -u -r1.1.2.7 -r1.1.2.8
--- stopping.xml.de 16 Apr 2003 00:22:44 -0000 1.1.2.7
+++ stopping.xml.de 23 Apr 2003 22:43:41 -0000 1.1.2.8
@@ -32,9 +32,9 @@
module="mpm_common">PidFile</directive> steht. Das heißt, Sie
sollten es niemals nötig haben, einem anderen Prozess, als dem
Elternprozess, ein Signal zu senden. Es gibt drei Signale, die Sie an den
- Elternprozess senden können: <a href="#term"><code>TERM</code></a>,
- <a href="#hup"><code>HUP</code></a> und
- <a href="#graceful"><code>USR1</code></a>, die nachfolgend beschrieben
+ Elternprozess senden können: <code><a href="#term">TERM</a></code>,
+ <code><a href="#hup">HUP</a></code> und
+ <code><a href="#graceful">USR1</a></code>, die nachfolgend beschrieben
werden.</p>
<p>Um dem Elternprozess ein Signal zu senden, verwenden Sie einen
1.37.2.2 +2 -2 httpd-2.0/docs/manual/suexec.html.en
Index: suexec.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/suexec.html.en,v
retrieving revision 1.37.2.1
retrieving revision 1.37.2.2
diff -u -r1.37.2.1 -r1.37.2.2
--- suexec.html.en 11 Dec 2002 22:27:02 -0000 1.37.2.1
+++ suexec.html.en 23 Apr 2003 22:43:41 -0000 1.37.2.2
@@ -53,7 +53,7 @@
Apache Group and this document.</p>
<p>First, it is assumed that you are using a UNIX
- derivate operating system that is capable of
+ derivative operating system that is capable of
<strong>setuid</strong> and <strong>setgid</strong> operations.
All command examples are given in this regard. Other platforms,
if they are capable of supporting suEXEC, may differ in their
@@ -327,7 +327,7 @@
</li>
</ol>
- <p>This is the standard operation of the the
+ <p>This is the standard operation of the
suEXEC wrapper's security model. It is somewhat stringent and
can impose new limitations and guidelines for CGI/SSI design,
but it was developed carefully step-by-step with security in
1.3.2.3 +2 -2 httpd-2.0/docs/manual/suexec.xml
Index: suexec.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/suexec.xml,v
retrieving revision 1.3.2.2
retrieving revision 1.3.2.3
diff -u -r1.3.2.2 -r1.3.2.3
--- suexec.xml 16 Apr 2003 00:22:44 -0000 1.3.2.2
+++ suexec.xml 23 Apr 2003 22:43:41 -0000 1.3.2.3
@@ -31,7 +31,7 @@
Apache Group and this document.</p>
<p>First, it is assumed that you are using a UNIX
- derivate operating system that is capable of
+ derivative operating system that is capable of
<strong>setuid</strong> and <strong>setgid</strong> operations.
All command examples are given in this regard. Other platforms,
if they are capable of supporting suEXEC, may differ in their
@@ -305,7 +305,7 @@
</li>
</ol>
- <p>This is the standard operation of the the
+ <p>This is the standard operation of the
suEXEC wrapper's security model. It is somewhat stringent and
can impose new limitations and guidelines for CGI/SSI design,
but it was developed carefully step-by-step with security in
1.14.2.3 +1 -1 httpd-2.0/docs/manual/urlmapping.html.en
Index: urlmapping.html.en
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/urlmapping.html.en,v
retrieving revision 1.14.2.2
retrieving revision 1.14.2.3
diff -u -r1.14.2.2 -r1.14.2.3
--- urlmapping.html.en 27 Jan 2003 00:51:37 -0000 1.14.2.2
+++ urlmapping.html.en 23 Apr 2003 22:43:41 -0000 1.14.2.3
@@ -199,7 +199,7 @@
the server to fetch the appropriate documents, while the
<code class="directive"><a href="./mod/mod_proxy.html#proxypassreverse">ProxyPassReverse</a></code>
directive rewrites redirects originating at
-<code>internal.examle.com</code> so that they target the appropriate
+<code>internal.example.com</code> so that they target the appropriate
directory on the local server. It is important to note, however, that
links inside the documents will not be rewritten. So any absolute
links on <code>internal.example.com</code> will result in the client
1.3.2.4 +1 -1 httpd-2.0/docs/manual/urlmapping.xml
Index: urlmapping.xml
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/urlmapping.xml,v
retrieving revision 1.3.2.3
retrieving revision 1.3.2.4
diff -u -r1.3.2.3 -r1.3.2.4
--- urlmapping.xml 16 Apr 2003 00:22:44 -0000 1.3.2.3
+++ urlmapping.xml 23 Apr 2003 22:43:41 -0000 1.3.2.4
@@ -212,7 +212,7 @@
the server to fetch the appropriate documents, while the
<directive module="mod_proxy">ProxyPassReverse</directive>
directive rewrites redirects originating at
-<code>internal.examle.com</code> so that they target the appropriate
+<code>internal.example.com</code> so that they target the appropriate
directory on the local server. It is important to note, however, that
links inside the documents will not be rewritten. So any absolute
links on <code>internal.example.com</code> will result in the client