diff options
35 files changed, 116 insertions, 116 deletions
diff --git a/docs/manual/bind.html b/docs/manual/bind.html index c9ec916a7f..cb1fa0daac 100644 --- a/docs/manual/bind.html +++ b/docs/manual/bind.html @@ -79,7 +79,7 @@ used to specify a different behavour for one or more of the addresses and ports. To implement a VirtualHost, the server must first be told to listen to the address and port to be used. Then a <VirtualHost> section should be created for a specified address -and port to set the behaviour of this virtual host. Note that if the +and port to set the behavior of this virtual host. Note that if the <VirtualHost> is set for an address and port that the server is not listening to, it cannot be accessed. diff --git a/docs/manual/bind.html.en b/docs/manual/bind.html.en index c9ec916a7f..cb1fa0daac 100644 --- a/docs/manual/bind.html.en +++ b/docs/manual/bind.html.en @@ -79,7 +79,7 @@ used to specify a different behavour for one or more of the addresses and ports. To implement a VirtualHost, the server must first be told to listen to the address and port to be used. Then a <VirtualHost> section should be created for a specified address -and port to set the behaviour of this virtual host. Note that if the +and port to set the behavior of this virtual host. Note that if the <VirtualHost> is set for an address and port that the server is not listening to, it cannot be accessed. diff --git a/docs/manual/content-negotiation.html b/docs/manual/content-negotiation.html index 35db8564b5..6c589a9efb 100644 --- a/docs/manual/content-negotiation.html +++ b/docs/manual/content-negotiation.html @@ -108,7 +108,7 @@ The full list of headers recognized is: <code>image/gif</code>, <code>text/plain</code>, or <code>text/html; level=3</code>. <dt> <code>Content-language:</code> - <dd> The language of the variant, specified as an internet standard + <dd> The language of the variant, specified as an Internet standard language code (e.g., <code>en</code> for English, <code>kr</code> for Korean, etc.). <dt> <code>Content-encoding:</code> diff --git a/docs/manual/content-negotiation.html.en b/docs/manual/content-negotiation.html.en index 35db8564b5..6c589a9efb 100644 --- a/docs/manual/content-negotiation.html.en +++ b/docs/manual/content-negotiation.html.en @@ -108,7 +108,7 @@ The full list of headers recognized is: <code>image/gif</code>, <code>text/plain</code>, or <code>text/html; level=3</code>. <dt> <code>Content-language:</code> - <dd> The language of the variant, specified as an internet standard + <dd> The language of the variant, specified as an Internet standard language code (e.g., <code>en</code> for English, <code>kr</code> for Korean, etc.). <dt> <code>Content-encoding:</code> diff --git a/docs/manual/custom-error.html b/docs/manual/custom-error.html index 0518f041cd..efc3f041e2 100644 --- a/docs/manual/custom-error.html +++ b/docs/manual/custom-error.html @@ -1,6 +1,6 @@ <HTML> <HEAD> -<TITLE>Ccustom error responses</TITLE> +<TITLE>Custom error responses</TITLE> </HEAD> <BODY> @@ -9,7 +9,7 @@ <DL> <DT>Purpose -<DD>Additional functionality. Allows webmasters to configure the response of +<DD>Additional functionality. Allows web-masters to configure the response of Apache to some error or problem.<BR> <P>Customizable responses can be defined to be activated in the event of a server detected error or problem.<BR> @@ -82,14 +82,14 @@ prior to sending a <code>SIGHUP</code> (kill -1) signal. <h2>Custom error responses and redirects</H2> <DL> <DT>Purpose -<DD>Apache's behaviour to redirected URLs has been modified so that additional +<DD>Apache's behavior to redirected URLs has been modified so that additional environment variables are available to a script/server-include.<p> -<DT>Old behaviour +<DT>Old behavior <DD>Standard CGI vars were made available to a script which has been redirected to. No indication of where the redirection came from was provided. <p> -<DT>New behaviour +<DT>New behavior <DD>A new batch of environment variables will be initialized for use by a script which has been redirected to.<BR> Each new variable will have the prefix <code>REDIRECT_</code>.<BR> diff --git a/docs/manual/custom-error.html.en b/docs/manual/custom-error.html.en index 0518f041cd..efc3f041e2 100644 --- a/docs/manual/custom-error.html.en +++ b/docs/manual/custom-error.html.en @@ -1,6 +1,6 @@ <HTML> <HEAD> -<TITLE>Ccustom error responses</TITLE> +<TITLE>Custom error responses</TITLE> </HEAD> <BODY> @@ -9,7 +9,7 @@ <DL> <DT>Purpose -<DD>Additional functionality. Allows webmasters to configure the response of +<DD>Additional functionality. Allows web-masters to configure the response of Apache to some error or problem.<BR> <P>Customizable responses can be defined to be activated in the event of a server detected error or problem.<BR> @@ -82,14 +82,14 @@ prior to sending a <code>SIGHUP</code> (kill -1) signal. <h2>Custom error responses and redirects</H2> <DL> <DT>Purpose -<DD>Apache's behaviour to redirected URLs has been modified so that additional +<DD>Apache's behavior to redirected URLs has been modified so that additional environment variables are available to a script/server-include.<p> -<DT>Old behaviour +<DT>Old behavior <DD>Standard CGI vars were made available to a script which has been redirected to. No indication of where the redirection came from was provided. <p> -<DT>New behaviour +<DT>New behavior <DD>A new batch of environment variables will be initialized for use by a script which has been redirected to.<BR> Each new variable will have the prefix <code>REDIRECT_</code>.<BR> diff --git a/docs/manual/handler.html b/docs/manual/handler.html index 594f537106..c94afd7653 100644 --- a/docs/manual/handler.html +++ b/docs/manual/handler.html @@ -14,7 +14,7 @@ performed when a file is called. Generally, files have implicit handlers, based on the file type. Normally, all files are simply served by the server, but certain file typed are "handled" -seperately. For example, you may use a type of +separately. For example, you may use a type of "application/x-httpd-cgi" to invoke CGI scripts.</p> <p>Apache 1.1 adds the additional ability to use handlers @@ -48,7 +48,7 @@ handlers in the standard distribution are as follows:</p> Get the server's status report (<a href="mod_status.html">mod_status</a>) <li><strong>type-map</strong>: - Parse as a type map file for content negotation + Parse as a type map file for content negotiation (<a href="mod_negotiation.html">mod_negotiation</a>) </ul> @@ -64,7 +64,7 @@ handlers in the standard distribution are as follows:</p> <h2><a name="addhandler">AddHandler</a></h2> -<strong>Syntax:</strong> <AddHandler <em>handler-name extention</em>><br> +<strong>Syntax:</strong> <AddHandler <em>handler-name extension</em>><br> <strong>Context:</strong> server config, virtual host, directory, .htaccess<br> <strong>Status:</strong> Base<br> <strong>Module:</strong> mod_mime @@ -122,11 +122,11 @@ make use of. Specifically, a new record has been added to the <p>If you wish to have your module engage a handler, you need only to set <code>r->handler</code> to the name of the handler at any time prior to the <code>invoke_handler</code> stage of the -request. Handlers are implemented as they were before, albiet using +request. Handlers are implemented as they were before, albeit using the handler name instead of a content type. While it is not -neccessary, the naming convention for handlers is to use a -dash-seperated word, with no slashes, so as to not invade the media -type namespace.</p> +necessary, the naming convention for handlers is to use a +dash-separated word, with no slashes, so as to not invade the media +type name-space.</p> <!--#include virtual="footer.html" --> </BODY> diff --git a/docs/manual/handler.html.en b/docs/manual/handler.html.en index 594f537106..c94afd7653 100644 --- a/docs/manual/handler.html.en +++ b/docs/manual/handler.html.en @@ -14,7 +14,7 @@ performed when a file is called. Generally, files have implicit handlers, based on the file type. Normally, all files are simply served by the server, but certain file typed are "handled" -seperately. For example, you may use a type of +separately. For example, you may use a type of "application/x-httpd-cgi" to invoke CGI scripts.</p> <p>Apache 1.1 adds the additional ability to use handlers @@ -48,7 +48,7 @@ handlers in the standard distribution are as follows:</p> Get the server's status report (<a href="mod_status.html">mod_status</a>) <li><strong>type-map</strong>: - Parse as a type map file for content negotation + Parse as a type map file for content negotiation (<a href="mod_negotiation.html">mod_negotiation</a>) </ul> @@ -64,7 +64,7 @@ handlers in the standard distribution are as follows:</p> <h2><a name="addhandler">AddHandler</a></h2> -<strong>Syntax:</strong> <AddHandler <em>handler-name extention</em>><br> +<strong>Syntax:</strong> <AddHandler <em>handler-name extension</em>><br> <strong>Context:</strong> server config, virtual host, directory, .htaccess<br> <strong>Status:</strong> Base<br> <strong>Module:</strong> mod_mime @@ -122,11 +122,11 @@ make use of. Specifically, a new record has been added to the <p>If you wish to have your module engage a handler, you need only to set <code>r->handler</code> to the name of the handler at any time prior to the <code>invoke_handler</code> stage of the -request. Handlers are implemented as they were before, albiet using +request. Handlers are implemented as they were before, albeit using the handler name instead of a content type. While it is not -neccessary, the naming convention for handlers is to use a -dash-seperated word, with no slashes, so as to not invade the media -type namespace.</p> +necessary, the naming convention for handlers is to use a +dash-separated word, with no slashes, so as to not invade the media +type name-space.</p> <!--#include virtual="footer.html" --> </BODY> diff --git a/docs/manual/invoking.html b/docs/manual/invoking.html index 6bf5225057..73c570016a 100644 --- a/docs/manual/invoking.html +++ b/docs/manual/invoking.html @@ -17,7 +17,7 @@ service is made (use the but this is not recommended. <h2>Command line options</h2> -The following options are recognised on the httpd command line: +The following options are recognized on the httpd command line: <dl> <dt><code>-d</code> <em>serverroot</em> <dd>Set the initial value for the @@ -68,7 +68,7 @@ The filename may be overridden with the <code>-f</code> command line flag. the server can provide to clients. The filename may be overridden with the <A HREF="mod/core.html#resourceconfig">ResourceConfig</A> directive. -<dt><code>conf/acces.conf</code> +<dt><code>conf/access.conf</code> <dd>Contains directives that control access to documents. The filename may be overridden with the <A HREF="mod/core.html#accessconfig">AccessConfig</A> directive. diff --git a/docs/manual/invoking.html.en b/docs/manual/invoking.html.en index 6bf5225057..73c570016a 100644 --- a/docs/manual/invoking.html.en +++ b/docs/manual/invoking.html.en @@ -17,7 +17,7 @@ service is made (use the but this is not recommended. <h2>Command line options</h2> -The following options are recognised on the httpd command line: +The following options are recognized on the httpd command line: <dl> <dt><code>-d</code> <em>serverroot</em> <dd>Set the initial value for the @@ -68,7 +68,7 @@ The filename may be overridden with the <code>-f</code> command line flag. the server can provide to clients. The filename may be overridden with the <A HREF="mod/core.html#resourceconfig">ResourceConfig</A> directive. -<dt><code>conf/acces.conf</code> +<dt><code>conf/access.conf</code> <dd>Contains directives that control access to documents. The filename may be overridden with the <A HREF="mod/core.html#accessconfig">AccessConfig</A> directive. diff --git a/docs/manual/location.html b/docs/manual/location.html index 5f2e7cacb5..b4da28da01 100644 --- a/docs/manual/location.html +++ b/docs/manual/location.html @@ -15,7 +15,7 @@ <strong>Status:</strong> core<br> <p>The <Location> directive provides for access control by -URL. It is comprable to the <a +URL. It is comparable to the <a href="../core.html#directory"><Directory></a> directive, and should be matched with a </Location> directive. Directives that apply to the URL given should be listen @@ -27,8 +27,8 @@ read.</p> <p>Note that, due to the way HTTP functions, <em>URL prefix</em> should, save for proxy requests, be of the form <code>/path/</code>, and should not include the <code>http://servername</code>. It doesn't -neccessarily have to protect a directory (it can be an individual -file, or a number of files), and can include wildcards. In a wildcard +necessarily have to protect a directory (it can be an individual +file, or a number of files), and can include wild-cards. In a wild-card string, `?' matches any single character, and `*' matches any sequences of characters. diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index 016bc0bfdf..b9e2d58044 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -214,7 +214,7 @@ It must be accompanied by <A HREF="#authname">AuthName</A> and The server comes with a built-in list of active modules. This directive clears the list. It is assumed that the list will then be -repopulated using the <A HREF="#addmodule">AddModule</A> directive.<p><hr> +re-populated using the <A HREF="#addmodule">AddModule</A> directive.<p><hr> <A name="bindaddress"><h2>BindAddress directive</h2></A> <!--%plaintext <?INDEX {\tt BindAddress} directive> --> @@ -271,7 +271,7 @@ with filenames missing the .gif extension.<p><hr> directives which will apply only to the named directory and sub-directories of that directory. Any directive which is allowed in a directory context may be used. <em>Directory</em> is either the full path to a directory, -or a wildcard string. In a wildcard string, `?' matches any single character, +or a wild-card string. In a wild-card string, `?' matches any single character, and `*' matches any sequences of characters. Example: <pre> <Directory /usr/local/httpd/htdocs> @@ -296,7 +296,7 @@ first, interspersed with the directives from the <blockquote><code> <Directory /><br> AllowOverride None<br> -</Directoy><br><br> +</Directory><br><br> <Directory /home/*><br> AllowOverride FileInfo<br> </Directory></code></blockquote> @@ -408,7 +408,7 @@ order they appear in the configuration file, after the read, but before <Location> sections.</p> <p>The <em>filename</em> argument should include a filename, or a -wildcard string, where `?' matches any single character, and `*' matches any +wild-card string, where `?' matches any single character, and `*' matches any sequences of characters. Extended regular expressions can also be used, with the addition of the <code>~</code> character. For example:</p> @@ -437,7 +437,7 @@ the directory being applied will be prefixed automatically. <strong>Status:</strong> core<p> The Group directive sets the group under which the server will answer requests. -In order to use this directive, the standalone server must be run initially +In order to use this directive, the stand-alone server must be run initially as root. <em>Unix-group</em> is one of: <dl> <dt>A group name @@ -510,7 +510,7 @@ the directives if <i>module name</i> is <b>not</b> compiled in. name of the module, at the time it was compiled. For example, <code>mod_rewrite.c</code>. -<p><IfModule> sections are nestable, which can be used to implement +<p><IfModule> sections are nest-able, which can be used to implement simple multiple-module tests. <P> <hr> @@ -592,7 +592,7 @@ then it applies to all access methods.<p><hr> 1.1 and later.<p> <p>The <Location> directive provides for access control by -URL. It is comprable to the <a +URL. It is comparable to the <a href="#directory"><Directory></a> directive, and should be matched with a </Location> directive. Directives that apply to the URL given should be listen @@ -604,8 +604,8 @@ read.</p> <p>Note that, due to the way HTTP functions, <em>URL prefix</em> should, save for proxy requests, be of the form <code>/path/</code>, and should not include the <code>http://servername</code>. It doesn't -neccessarily have to protect a directory (it can be an individual -file, or a number of files), and can include wildcards. In a wildcard +necessarily have to protect a directory (it can be an individual +file, or a number of files), and can include wild-cards. In a wild-card string, `?' matches any single character, and `*' matches any sequences of characters. @@ -746,7 +746,7 @@ return a formatted listing of the directory. <dt>MultiViews <dd> <!--%plaintext <?INDEX {\tt MultiViews} option> --> -<A HREF="content-negotiation.html">Ccontent negotiatad</A> MultiViews are +<A HREF="content-negotiation.html">Content negotiated</A> MultiViews are allowed. <dt>SymLinksIfOwnerMatch <dd> @@ -948,7 +948,7 @@ startup phase.<p> Process limits control the number of processes per user.<p> Note: If CGI processes are <b>not</b> running under userids other than the -webserver userid, this directive will limit the number of processes that the +web server userid, this directive will limit the number of processes that the server itself can create. Evidence of this situation will be indicated by <b><em>cannot fork</em></b> messages in the error_log.<p> diff --git a/docs/manual/mod/index.html b/docs/manual/mod/index.html index 95d39d0fe5..4c78cab8f2 100644 --- a/docs/manual/mod/index.html +++ b/docs/manual/mod/index.html @@ -16,7 +16,7 @@ <dt><A HREF="mod_actions.html">mod_actions</A> Apache 1.1 and later. <dd>Filetype/method-based script execution <dt><A HREF="mod_alias.html">mod_alias</A> -<dd>Aliase and redirects. +<dd>Aliases and redirects. <dt><A HREF="mod_asis.html">mod_asis</A> <dd>The .asis file handler. <dt><A HREF="mod_auth.html">mod_auth</A> @@ -70,7 +70,7 @@ mod_log_config module in Apache 1.2 and up <dt><A HREF="mod_mime.html">mod_mime</A> <dd>Determining document types. <dt><A HREF="mod_negotiation.html">mod_negotiation</A> -<dd>Content negotation. +<dd>Content negotiation. <dt><A NAME="mod_rewrite.html">mod_rewrite</a> Apache 1.2 and up <dd>Powerful URI-to-filename mapping using regular expressions <dt><A HREF="mod_proxy.html">mod_proxy</A> diff --git a/docs/manual/mod/mod_actions.html b/docs/manual/mod/mod_actions.html index a2fcf9c502..47af987ae9 100644 --- a/docs/manual/mod/mod_actions.html +++ b/docs/manual/mod/mod_actions.html @@ -29,7 +29,7 @@ process files. <A name="action"><h2>Action</h2></A> <strong>Syntax:</strong> Action <em>mime-type cgi-script</em><br> -<strong>Context:</strong> server config, virutal host, directory, .htaccess<br> +<strong>Context:</strong> server config, virtual host, directory, .htaccess<br> <strong>Override:</strong> FileInfo<br> <strong>Status:</strong> Base<br> <strong>Module:</strong> mod_actions<br> @@ -45,7 +45,7 @@ CGI PATH_INFO and PATH_TRANSLATED environment variables. <A name="script"><h2>Script</h2></A> <strong>Syntax:</strong> Script <em>method cgi-script</em><br> -<strong>Context:</strong> server config, virutal host, directory<br> +<strong>Context:</strong> server config, virtual host, directory<br> <strong>Status:</strong> Base<br> <strong>Module:</strong> mod_actions<br> <strong>Compatibility:</strong> Script is only available in Apache 1.1 diff --git a/docs/manual/mod/mod_alias.html b/docs/manual/mod/mod_alias.html index 0984bf82e1..fb0013186f 100644 --- a/docs/manual/mod/mod_alias.html +++ b/docs/manual/mod/mod_alias.html @@ -114,7 +114,7 @@ This directive makes the client know that the Redirect is permanent. <strong>Status:</strong> Base<br> <strong>Module:</strong> mod_alias<br> -The ScriptAlias directive has the same behaviour as the +The ScriptAlias directive has the same behavior as the <A HREF="#alias">Alias</A> directive, except that in addition it marks the target directory as containing CGI scripts. URLs with a (%-decoded) path beginning with <em>url-path</em> will be diff --git a/docs/manual/mod/mod_auth.html b/docs/manual/mod/mod_auth.html index edf7ba1161..4b1816a601 100644 --- a/docs/manual/mod/mod_auth.html +++ b/docs/manual/mod/mod_auth.html @@ -40,7 +40,7 @@ Note that searching large groups files is <em>very</em> inefficient; be used instead.<p> Security: make sure that the AuthGroupFile is stored outside the -document tree of the webserver; do <em>not</em> put it in the directory that +document tree of the web-server; do <em>not</em> put it in the directory that it protects. Otherwise, clients will be able to download the AuthGroupFile.<p> See also <A HREF="core.html#authname">AuthName</A>, @@ -59,14 +59,14 @@ The AuthUserFile directive sets the name of a textual file containing the list of users and passwords for user authentication. <em>Filename</em> is the absolute path to the user file.<p> Each line of the user file file contains a username followed by a colon, -followed by the crypt() encrypted password. The behaviour of multiple +followed by the crypt() encrypted password. The behavior of multiple occurrences of the same user is undefined.<p> Note that searching user groups files is inefficient; <A HREF="mod_auth_dbm.html#authdbmuserfile">AuthDBMUserFile</A> should be used instead.<p> Security: make sure that the AuthUserFile is stored outside the -document tree of the webserver; do <em>not</em> put it in the directory that +document tree of the web-server; do <em>not</em> put it in the directory that it protects. Otherwise, clients will be able to download the AuthUserFile.<p> See also <A HREF="core.html#authname">AuthName</A>, diff --git a/docs/manual/mod/mod_auth_anon.html b/docs/manual/mod/mod_auth_anon.html index 0518cfc68d..5bdd769ecf 100644 --- a/docs/manual/mod/mod_auth_anon.html +++ b/docs/manual/mod/mod_auth_anon.html @@ -67,7 +67,7 @@ Anonymous_VerifyEmail < on | off > </code></dt><dd> When set 'on', the default is 'off', the 'password' entered is checked for at least one '@' and a '.' to encourage users to enter - valid email addressses (see the above <code>Auth_LogEmail</code>. + valid email addresses (see the above <code>Auth_LogEmail</code>. </dd> <code><dt> @@ -121,7 +121,7 @@ the httpd-log file (<code>Anonymous_LogEmail</code>) </ul> <p> -Excerp of access.conf: +Excerpt of access.conf: <dl> <dt><code> Anonymous anonymous guest www test welcome<p> @@ -162,7 +162,7 @@ This version: 23 Nov 1995, 24 Feb 1996, 16 May 1996. </dd> <dt>Version 0.5<br></dt> <dd>Added 'VerifyEmail' and 'LogEmail' options. Multiple - 'anonymous' tokes allowed. more docs. Added Authorative + 'anonymous' tokens allowed. more docs. Added Authorative functionality. </dd> </dl> @@ -173,7 +173,7 @@ This version: 23 Nov 1995, 24 Feb 1996, 16 May 1996. This module was written for the <a href="http://ewse.ceo.org">European Wide Service Exchange</a> by <<a href="mailto:Dirk.vanGulik@jrc.it"><code>Dirk.vanGulik@jrc.it</code></a>>. -Feel free to contact me if you have any problems, icecreams or bugs. This +Feel free to contact me if you have any problems, ice-creams or bugs. This documentation, courtesy of Nick Himba, <a href="mailto:himba@cs.utwente.nl"> <code><himba@cs.utwente.nl></code></a>. <p> diff --git a/docs/manual/mod/mod_auth_db.html b/docs/manual/mod/mod_auth_db.html index f9d45c5212..5e72af6f1a 100644 --- a/docs/manual/mod/mod_auth_db.html +++ b/docs/manual/mod/mod_auth_db.html @@ -39,7 +39,7 @@ comma-separated list of the groups to which the users belongs. There must be no whitespace within the value, and it must never contain any colons.<p> Security: make sure that the AuthDBGroupFile is stored outside the -document tree of the webserver; do <em>not</em> put it in the directory that +document tree of the web-server; do <em>not</em> put it in the directory that it protects. Otherwise, clients will be able to download the AuthDBGroupFile unless otherwise protected.<p> @@ -58,7 +58,7 @@ AuthDBUserFile /www/userbase The key for the single DB record is the username. The value consists of <p> <blockquote><code> -Unix Crypted Password : List of Groups [ : (ignored) ] +Unix Crypt-ed Password : List of Groups [ : (ignored) ] </code></blockquote> The password section contains the Unix crypt() password as before. This is @@ -88,7 +88,7 @@ arbitrary data. The colon and the data following it will be ignored by the server.<p> Security: make sure that the AuthDBUserFile is stored outside the -document tree of the webserver; do <em>not</em> put it in the directory that +document tree of the web-server; do <em>not</em> put it in the directory that it protects. Otherwise, clients will be able to download the AuthDBUserFile.<p> diff --git a/docs/manual/mod/mod_auth_dbm.html b/docs/manual/mod/mod_auth_dbm.html index 7a58c7fec1..7c05f43843 100644 --- a/docs/manual/mod/mod_auth_dbm.html +++ b/docs/manual/mod/mod_auth_dbm.html @@ -38,7 +38,7 @@ comma-separated list of the groups to which the users belongs. There must be no whitespace within the value, and it must never contain any colons.<p> Security: make sure that the AuthDBMGroupFile is stored outside the -document tree of the webserver; do <em>not</em> put it in the directory that +document tree of the web-server; do <em>not</em> put it in the directory that it protects. Otherwise, clients will be able to download the AuthDBMGroupFile unless otherwise protected.<p> @@ -57,7 +57,7 @@ AuthDBMUserFile /www/userbase The key for the single DBM is the username. The value consists of <p> <blockquote><code> -Unix Crypted Password : List of Groups [ : (ignored) ] +Unix Crypt-ed Password : List of Groups [ : (ignored) ] </code></blockquote> The password section contains the Unix crypt() password as before. This is @@ -88,7 +88,7 @@ arbitrary data. The colon and the data following it will be ignored by the server.<p> Security: make sure that the AuthDBMUserFile is stored outside the -document tree of the webserver; do <em>not</em> put it in the directory that +document tree of the web-server; do <em>not</em> put it in the directory that it protects. Otherwise, clients will be able to download the AuthDBMUserFile.<p> diff --git a/docs/manual/mod/mod_autoindex.html b/docs/manual/mod/mod_autoindex.html index d28724c3ac..dff18a603e 100644 --- a/docs/manual/mod/mod_autoindex.html +++ b/docs/manual/mod/mod_autoindex.html @@ -55,7 +55,7 @@ first icon listed that matches the file is displayed. This sets the description to display for a file, for <A HREF="#fancyindexing">FancyIndexing</A>. <em>File</em> is a file -extension, partial filename, wildcard expression or full filename for files +extension, partial filename, wild-card expression or full filename for files to describe. <em>String</em> is enclosed in double quotes (<code>"</code>). Example: <blockquote><code>AddDescription "The planet Mars" /web/pics/mars.gif @@ -231,7 +231,7 @@ IndexIgnore README .htaccess *~ <strong>Status:</strong> Base<br> <strong>Module:</strong> mod_dir<p> -The IndexOptions directive specifies the behaviour of the directory indexing. +The IndexOptions directive specifies the behavior of the directory indexing. <em>Option</em> can be one of <dl> <dt>FancyIndexing diff --git a/docs/manual/mod/mod_cgi.html b/docs/manual/mod/mod_cgi.html index 425b7e7c6a..70a521487d 100644 --- a/docs/manual/mod/mod_cgi.html +++ b/docs/manual/mod/mod_cgi.html @@ -33,7 +33,7 @@ configuration variable. <h2>CGI Environment variables</h2> The server will set the CGI environment variables as described in the CGI -specification, with the following provisos: +specification, with the following provisons: <dl> <dt>REMOTE_HOST <dd>This will only be set if the server has not been compiled with @@ -135,7 +135,7 @@ taken relative to the server root. script logfile. Since the logfile logs a lot of information per CGI error (all request headers, all script output) it can grow to be a big file. To prevent problems due to unbounded growth, this directive can -be used to set an maximum filesize for the CGI logfile. If the file +be used to set an maximum file-size for the CGI logfile. If the file exceeds this size, no more information will be written to it. <a name="scriptlogbuffer"><h3>ScriptLogBuffer</h3></a> diff --git a/docs/manual/mod/mod_dir.html b/docs/manual/mod/mod_dir.html index d28724c3ac..dff18a603e 100644 --- a/docs/manual/mod/mod_dir.html +++ b/docs/manual/mod/mod_dir.html @@ -55,7 +55,7 @@ first icon listed that matches the file is displayed. This sets the description to display for a file, for <A HREF="#fancyindexing">FancyIndexing</A>. <em>File</em> is a file -extension, partial filename, wildcard expression or full filename for files +extension, partial filename, wild-card expression or full filename for files to describe. <em>String</em> is enclosed in double quotes (<code>"</code>). Example: <blockquote><code>AddDescription "The planet Mars" /web/pics/mars.gif @@ -231,7 +231,7 @@ IndexIgnore README .htaccess *~ <strong>Status:</strong> Base<br> <strong>Module:</strong> mod_dir<p> -The IndexOptions directive specifies the behaviour of the directory indexing. +The IndexOptions directive specifies the behavior of the directory indexing. <em>Option</em> can be one of <dl> <dt>FancyIndexing diff --git a/docs/manual/mod/mod_env.html b/docs/manual/mod/mod_env.html index 7d779af73c..7d1532547f 100644 --- a/docs/manual/mod/mod_env.html +++ b/docs/manual/mod/mod_env.html @@ -17,8 +17,8 @@ in Apache 1.1 and later. This module allows Apache's CGI and SSI environment to inherit environment variables from the shell which invoked the httpd process. -CERN webservers are able to do this, so this module is especially -useful to webadmins who wish to migrate from CERN to Apache without +CERN web-servers are able to do this, so this module is especially +useful to web-admins who wish to migrate from CERN to Apache without rewriting all their scripts <h2>Directives</h2> @@ -37,7 +37,7 @@ rewriting all their scripts <strong>Compatibility:</strong> PassEnv is only available in Apache 1.1 and later.<p> -Passes an environment variable to CGI scripts from the servers's own +Passes an environment variable to CGI scripts from the server's own environment. Example: <pre> PassEnv LD_LIBRARY_PATH diff --git a/docs/manual/mod/mod_headers.html b/docs/manual/mod/mod_headers.html index db25271583..2e976622ed 100644 --- a/docs/manual/mod/mod_headers.html +++ b/docs/manual/mod/mod_headers.html @@ -8,7 +8,7 @@ <!--#include virtual="header.html" --> <h1>Headers Module</h1> -The optional headers module allows for the customisation of HTTP +The optional headers module allows for the customization of HTTP response headers. Headers can be merged, replaced or removed. The directives described in this document are only available if Apache is compiled with <b>mod_headers.c</b>. @@ -23,8 +23,8 @@ compiled with <b>mod_headers.c</b>. <hr> <A name="header"><h2>Header</h2></A> -<strong>Sytnax:</strong> Header [ set | append | add ] <em>header</em> <em>value</em><br> -<strong>Sytnax:</strong> Header unset <em>header</em><br> +<strong>Syntax:</strong> Header [ set | append | add ] <em>header</em> <em>value</em><br> +<strong>Syntax:</strong> Header unset <em>header</em><br> <strong>Context:</strong> server config, virtual host, access.conf, .htaccess<br> <strong>Status:</strong> optional<br> <strong>Module:</strong> mod_header<p> @@ -46,7 +46,7 @@ of the following values: <li><b>add</b><br> The response header is added to the existing set of headers, even if this header already exists. This can result in two (or more) headers - having the same name. This can lead to unforseen consequences, and in + having the same name. This can lead to unforeseen consequences, and in general "append" should be used instead. <li><b>unset</b><br> diff --git a/docs/manual/mod/mod_imap.html b/docs/manual/mod/mod_imap.html index 02b346e36f..50ae2b299b 100644 --- a/docs/manual/mod/mod_imap.html +++ b/docs/manual/mod/mod_imap.html @@ -59,7 +59,7 @@ possible with previously distributed imagemap programs.<P> <p> <A name="imapmenu"><h3>ImapMenu</h3></A> -<strong>Syntax:</strong> ImapMenu <code>{none, formatted, semiformatted, +<strong>Syntax:</strong> ImapMenu <code>{none, formatted, semi-formatted, unformatted}</code><br> <Strong>Context:</strong> server config, virtual host, directory, .htaccess<br> <Strong>Override:</strong> Indexes<br> @@ -142,7 +142,7 @@ The directive is one of <code>base</code>, <code>default</code>, <code>poly</code>, <code>circle</code>, <code>rect</code>, or <code>point</code>. The value is an absolute or relative URL, or one of the special values listed below. The coordinates are -<code>x,y</code> pairs seperated by whitespace. The quoted text is +<code>x,y</code> pairs separated by whitespace. The quoted text is used as the text of the link if a imagemap menu is generated. Lines beginning with '#' are comments. @@ -153,7 +153,7 @@ in the imagemap file. <dl> <dt><code>base</code> Directive <dd>Has the effect of <code><BASE href="value"></code>. The - non-absolute URLs of the mapfile are taken relative to this value. + non-absolute URLs of the map-file are taken relative to this value. The <code>base</code> directive overrides ImapBase as set in a .htaccess file or in the server configuration files. In the absence of an ImapBase configuration directive, <code>base</code> defaults to @@ -211,7 +211,7 @@ The values for each of the directives can any of the following: <dd>Synonymous with <code>map</code>. <p> <dt><code>referer</code> - <dd>Equivalent to the URL of the refering document. + <dd>Equivalent to the URL of the referring document. Defaults to <code>http://servername/</code> if no Referer: header was present. <p> @@ -231,7 +231,7 @@ The values for each of the directives can any of the following: <dt><code>0,0 200,200</code> <dd>A coordinate consists of an <tt>x</tt> and a <tt>y</tt> value separated by a comma. The coordinates are separated from each other - by whitespace. To accomodate the way Lynx handles imagemaps, should a + by whitespace. To accommodate the way Lynx handles imagemaps, should a user select the coordinate <code>0,0</code>, it is as if no coordinate had been selected. </dl> diff --git a/docs/manual/mod/mod_include.html b/docs/manual/mod/mod_include.html index f8466ed9e9..4052baca61 100644 --- a/docs/manual/mod/mod_include.html +++ b/docs/manual/mod/mod_include.html @@ -74,7 +74,7 @@ completely. The valid attributes are: The value specifies a (%-encoded) URL relative path to the CGI script. If the path does not begin with a (/), then it is taken to be relative to the current document. The document referenced by this path is invoked -as a CGI script, even if the server would not normally recognise it as +as a CGI script, even if the server would not normally recognize it as such. However, the directory containing the script must be enabled for CGI scripts (with <A HREF="mod_alias.html#scriptalias">ScriptAlias</A> or the ExecCGI <A HREF="core.html#options">Option</A>).<p> @@ -244,7 +244,7 @@ elements are: <P> Anything that's not recognized as a variable or an operator is treated as a string. Strings can also be quoted: <I>'string'</I>. Unquoted strings can't contain whitespace (blanks and tabs) - because it is used to seperate tokens such as variables. If + because it is used to separate tokens such as variables. If multiple strings are found in a row, they are concatenated using blanks. So, diff --git a/docs/manual/mod/mod_log_config.html b/docs/manual/mod/mod_log_config.html index f381bf2867..9b3a199283 100644 --- a/docs/manual/mod/mod_log_config.html +++ b/docs/manual/mod/mod_log_config.html @@ -45,7 +45,7 @@ should be defined to log user-tracking information instead. Unless told otherwise with <tt>LogFormat</tt> the log files created by <tt>TransferLog</tt> will be in standard "Common Log Format" (CLF). The contents of each line in a CLF file are explained -below. Alternatively, the log file can be customised (and if multiple +below. Alternatively, the log file can be customized (and if multiple log files are used, each can have a different format). Custom formats are set with <code>LogFormat</code> and <code>CustomLog</code>. diff --git a/docs/manual/mod/mod_mime.html b/docs/manual/mod/mod_mime.html index 21888f7c5a..9c00f865ae 100644 --- a/docs/manual/mod/mod_mime.html +++ b/docs/manual/mod/mod_mime.html @@ -65,7 +65,7 @@ encoding, and .Z files to be marked as encoded with x-compress.<p><hr> <h2><a name="addhandler">AddHandler</a></h2> -<strong>Syntax:</strong> <AddHandler <em>handler-name extention</em>><br> +<strong>Syntax:</strong> <AddHandler <em>handler-name extension</em>><br> <strong>Context:</strong> server config, virtual host, directory, .htaccess<br> <strong>Status:</strong> Base<br> <strong>Module:</strong> mod_mime<br> diff --git a/docs/manual/mod/mod_negotiation.html b/docs/manual/mod/mod_negotiation.html index 3e19d419c3..e6b3d8dcd0 100644 --- a/docs/manual/mod/mod_negotiation.html +++ b/docs/manual/mod/mod_negotiation.html @@ -39,7 +39,7 @@ The headers allowed are: <dl> <dt>Content-Encoding: -<dd>The encoding of the file. Currently only two encodings are recognised +<dd>The encoding of the file. Currently only two encodings are recognized by http; <code>x-compress</code> for compressed files, and <code>x-gzip</code> for gzipped files. <dt>Content-Language: diff --git a/docs/manual/mod/mod_proxy.html b/docs/manual/mod/mod_proxy.html index 6d9e4ee5e6..1f01978d03 100644 --- a/docs/manual/mod/mod_proxy.html +++ b/docs/manual/mod/mod_proxy.html @@ -167,7 +167,7 @@ document, then estimate on using the formula expiry-period = time-since-last-modification * <factor> </pre> For example, if the document was last modified 10 hours ago, and -<factor> is 0.1, then the expiry period wil be set to 10*0.1 = 1 hour. +<factor> is 0.1, then the expiry period will be set to 10*0.1 = 1 hour. <p>If the expiry-period would be longer than that set by CacheMaxExpire, then the latter takes precedence. diff --git a/docs/manual/mod/mod_rewrite.html b/docs/manual/mod/mod_rewrite.html index b7c4e633a0..8061ff4065 100644 --- a/docs/manual/mod/mod_rewrite.html +++ b/docs/manual/mod/mod_rewrite.html @@ -35,7 +35,7 @@ substitution. <p> It operates on the full URLs (including the PATH_INFO part) both in per-server context (httpd.conf) and per-dir context (.htaccess) and even -can generate QUERY_STRING parts on result. The rewrittten result can lead to internal sub-processing, external request redirection or to internal proxy throughput. +can generate QUERY_STRING parts on result. The rewritten result can lead to internal sub-processing, external request redirection or to internal proxy throughput. </b> <p> @@ -280,13 +280,13 @@ RewriteMap real-to-host txt:/path/to/file/map.real-to-user <li><b>Program Format</b> <p> This is a Unix executable, not a lookup file. To create it you can use - the language of your choice, but the result has to be a runable Unix + the language of your choice, but the result has to be a run-able Unix binary (i.e. either object-code or a script with the magic cookie trick '<tt>#!/path/to/interpreter</tt>' as the first line). <p> This program gets started once at startup of the Apache servers and then communicates with the rewriting engine over its <tt>stdin</tt> and - <tt>stdout</tt> filehandles. For each map-function lookup it will + <tt>stdout</tt> file-handles. For each map-function lookup it will receive the key to lookup as a newline-terminated string on <tt>stdin</tt>. It then has to give back the looked-up value as a newline-terminated string on <tt>stdout</tt> or the four-character string @@ -359,7 +359,7 @@ it is automatically added. When a substitution occurs for a new URL, this module has to re-inject the URL into the server processing. To be able to do this it needs to know what the corresponding URL-prefix or URL-base is. By default this -prefix is the corresponding filepath itself. <b>But at most websites URLs are +prefix is the corresponding filepath itself. <b>But at most web-sites URLs are <b>NOT</b> directly related to physical filename paths, so this assumption will be usually be wrong!</b> There you have to use the <tt>RewriteBase</tt> directive to specify the correct URL-prefix. @@ -367,7 +367,7 @@ directive to specify the correct URL-prefix. <p> <table width=70% border=2 bgcolor="#c0c0e0" cellspacing=0 cellpadding=10> <tr><td> -So, if your webserver's URLs are <b>not</b> directly +So, if your web-server's URLs are <b>not</b> directly related to physical file paths, you have to use <tt>RewriteBase</tt> in every <tt>.htaccess</tt> files where you want to use <tt>RewriteRule</tt> directives. @@ -647,7 +647,7 @@ RewriteRule ...some special stuff for any of these hosts... <b>Example:</b> <blockquote> -To rewrite the Homepage of a site according to the ``<tt>User-Agent:</tt>'' +To rewrite the Home-page of a site according to the ``<tt>User-Agent:</tt>'' header of the request, you can use the following: <blockquote><pre> @@ -818,7 +818,7 @@ comma-separated list of the following flags: be handled by the Apache proxy module. If not you get an error from the proxy module. Use this flag to achieve a more powerful implementation of the <tt>mod_proxy</tt> directive <tt>ProxyPass</tt>, to map - some remote stuff into the namespace of the local server. + some remote stuff into the name-space of the local server. <p> <li>'<strong><code>last|L</code></strong>' (<b>l</b>ast rule)<br> Stop the rewriting process here and diff --git a/docs/manual/mod/mod_usertrack.html b/docs/manual/mod/mod_usertrack.html index 4c563f9d25..290c0c3f93 100644 --- a/docs/manual/mod/mod_usertrack.html +++ b/docs/manual/mod/mod_usertrack.html @@ -23,7 +23,7 @@ simplified and new directives added. Previously, the cookies module (now the user tracking module) did its own logging, using the <tt>CookieLog</tt> directive. In this release, this module does no logging at all. Instead, a configurable log -format file should be used to log user clickstreams. This is possible +format file should be used to log user click-streams. This is possible because the logging module now allows <a href="multilogs.html">multiple log files</a>. The cookie itself is logged by using the text <tt>%{cookie}n </tt> @@ -47,7 +47,7 @@ above <tt>CustomLog</tt> directive. <hr> <a name="cookieexpires"><h2>CookieEnable</h2></A> -<strong>Sytnax:</strong> CookieEnable <em>on | off</em><br> +<strong>Syntax:</strong> CookieEnable <em>on | off</em><br> <strong>Context:</strong> server config, virtual host, directory, .htaccess<br> <strong>Override:</strong> FileInfo<br> @@ -60,7 +60,7 @@ can be used to turn this behavior on or off on a per-server or per-directory basis. <a name="cookieexpires"><h2>CookieExpires</h2></A> -<strong>Sytnax:</strong> CookieExpires <em>expiry-period</em><br> +<strong>Syntax:</strong> CookieExpires <em>expiry-period</em><br> <strong>Context:</strong> server config, virtual host<br> <strong>Status:</strong> optional<br> <strong>Module:</strong> mod_usertrack<p> @@ -69,7 +69,7 @@ When used, this directive sets an expiry time on the cookie generated by the usertrack module. The <i>expiry-period</i> can be given either as a number of seconds, or in the format such as "2 weeks 3 days 7 hours". -Valid denominations are: years, months, weeks, hours, minues and +Valid denominations are: years, months, weeks, hours, minutes and seconds. diff --git a/docs/manual/process-model.html b/docs/manual/process-model.html index 15aafef810..bcf87e0516 100644 --- a/docs/manual/process-model.html +++ b/docs/manual/process-model.html @@ -10,8 +10,8 @@ We found that many people were using values for "MaxServers" either too high or too low, and were hanging themselves on it. The model we adopted is still based on long-lived minimal-forking processes, but -instead of specifying one number of persistant processes, the -webmaster specifies a maximum and minimum number of processes to be +instead of specifying one number of persistent processes, the +web-master specifies a maximum and minimum number of processes to be "spare" - every couple of seconds the parent checks the actual number of spare servers and adjusts accordingly. This should keep the number of servers concurrently running relatively low while still ensuring @@ -22,7 +22,7 @@ minimal forking. We renamed the current StartServers to MinSpareServers, created separate StartServers parameter which means what it says, and renamed MaxServers to MaxSpareServers (though the old name still works, for -NCSA 1.4 back-combatibility). The old names were generally regarded +NCSA 1.4 back-compatibility). The old names were generally regarded as too confusing. <P> diff --git a/docs/manual/suexec.html b/docs/manual/suexec.html index 8ce9a7b6f2..82a9d4a487 100644 --- a/docs/manual/suexec.html +++ b/docs/manual/suexec.html @@ -10,11 +10,11 @@ <h3>What is suEXEC?</h3> The <b>suEXEC</b> feature, introduced in Apache 1.2 provides the ability to run <b>CGI</b> programs under user ids different from the user id of the -calling webserver. Used properly, this feature can reduce considerably the +calling web-server. Used properly, this feature can reduce considerably the insecurity of allowing users to run CGI programs. At the same time, improperly configured, this facility can crash your computer, burn your house down and steal all the money from your retirement fund. <b>:-)</b> If you aren't -familar with managing setuid root programs and the security issues they +familiar with managing setuid root programs and the security issues they present, we highly recommend that you not consider using this feature.<p> <hr> @@ -26,7 +26,7 @@ is not part of the normal install/compile process.<p> <ul> <h3>Configuring the suEXEC wrapper</h3> -From the toplevel of the Apache source tree, type: <b><code>cd support [ENTER]</code></b><p> +From the top-level of the Apache source tree, type: <b><code>cd support [ENTER]</code></b><p> Edit the <code>suexec.h</code> file and change the following macros to match your local Apache installation.<p> <i>From support/suexec.h</i> @@ -47,9 +47,9 @@ local Apache installation.<p> #define LOG_EXEC "/usr/local/etc/httpd/logs/cgi.log" /* - * DOC_ROOT -- Define as the DocuemntRoot set for Apache. This + * DOC_ROOT -- Define as the DocumentRoot set for Apache. This * will be the only hierarchy (aside from UserDirs) - * that can be used for suEXEC behaviour. + * that can be used for suEXEC behavior. */ #define DOC_ROOT "/usr/local/etc/httpd/htdocs" @@ -117,7 +117,7 @@ checks before it will execute any program passed to it for execution. <li>The current working directory <b>must be a directory</b>. <li>The current working directory <b>must not be writable by <em>group</em> or <em>other</em></b>. <li>The command being executed <b>cannot be a symbolic link</b>. -<li>The command being executed <b>cannot be writeable by <em>group</em> or <em>other</em></b>. +<li>The command being executed <b>cannot be writable by <em>group</em> or <em>other</em></b>. <li>The command being executed <b>cannot be a <em>setuid</em> or <em>setgid</em> program</b>. <li>The target UID and GID <b>must be a valid user and group on this system</b>. <li>The target UID and GID to execute as, <b>must match the UID and GID of the directory</b>. @@ -133,7 +133,7 @@ have fun with it. <b>:-)</b> <h3>Using suEXEC</h3> After properly installing the <b>suexec</b> wrapper executable, you must kill and restart the Apache server. A simple <code><b>kill -1 `cat httpd.pid`</b></code> will not be enough. -Upon startup of the webserver, if Apache finds a properly configured <b>suexec</b> wrapper, +Upon startup of the web-server, if Apache finds a properly configured <b>suexec</b> wrapper, it will print the following message to the console.<p> <code>Configuring Apache for use with suexec wrapper.</code><p> diff --git a/docs/manual/suexec.html.en b/docs/manual/suexec.html.en index 8ce9a7b6f2..82a9d4a487 100644 --- a/docs/manual/suexec.html.en +++ b/docs/manual/suexec.html.en @@ -10,11 +10,11 @@ <h3>What is suEXEC?</h3> The <b>suEXEC</b> feature, introduced in Apache 1.2 provides the ability to run <b>CGI</b> programs under user ids different from the user id of the -calling webserver. Used properly, this feature can reduce considerably the +calling web-server. Used properly, this feature can reduce considerably the insecurity of allowing users to run CGI programs. At the same time, improperly configured, this facility can crash your computer, burn your house down and steal all the money from your retirement fund. <b>:-)</b> If you aren't -familar with managing setuid root programs and the security issues they +familiar with managing setuid root programs and the security issues they present, we highly recommend that you not consider using this feature.<p> <hr> @@ -26,7 +26,7 @@ is not part of the normal install/compile process.<p> <ul> <h3>Configuring the suEXEC wrapper</h3> -From the toplevel of the Apache source tree, type: <b><code>cd support [ENTER]</code></b><p> +From the top-level of the Apache source tree, type: <b><code>cd support [ENTER]</code></b><p> Edit the <code>suexec.h</code> file and change the following macros to match your local Apache installation.<p> <i>From support/suexec.h</i> @@ -47,9 +47,9 @@ local Apache installation.<p> #define LOG_EXEC "/usr/local/etc/httpd/logs/cgi.log" /* - * DOC_ROOT -- Define as the DocuemntRoot set for Apache. This + * DOC_ROOT -- Define as the DocumentRoot set for Apache. This * will be the only hierarchy (aside from UserDirs) - * that can be used for suEXEC behaviour. + * that can be used for suEXEC behavior. */ #define DOC_ROOT "/usr/local/etc/httpd/htdocs" @@ -117,7 +117,7 @@ checks before it will execute any program passed to it for execution. <li>The current working directory <b>must be a directory</b>. <li>The current working directory <b>must not be writable by <em>group</em> or <em>other</em></b>. <li>The command being executed <b>cannot be a symbolic link</b>. -<li>The command being executed <b>cannot be writeable by <em>group</em> or <em>other</em></b>. +<li>The command being executed <b>cannot be writable by <em>group</em> or <em>other</em></b>. <li>The command being executed <b>cannot be a <em>setuid</em> or <em>setgid</em> program</b>. <li>The target UID and GID <b>must be a valid user and group on this system</b>. <li>The target UID and GID to execute as, <b>must match the UID and GID of the directory</b>. @@ -133,7 +133,7 @@ have fun with it. <b>:-)</b> <h3>Using suEXEC</h3> After properly installing the <b>suexec</b> wrapper executable, you must kill and restart the Apache server. A simple <code><b>kill -1 `cat httpd.pid`</b></code> will not be enough. -Upon startup of the webserver, if Apache finds a properly configured <b>suexec</b> wrapper, +Upon startup of the web-server, if Apache finds a properly configured <b>suexec</b> wrapper, it will print the following message to the console.<p> <code>Configuring Apache for use with suexec wrapper.</code><p> |