initialisation → initialization (hooks.xml, modules.xml, mod_crypto.xml)
Recognise → Recognize (mod_xml2enc.xml)
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@
1933830 13f79535-47bb-0310-9956-
ffa450edef68
</section>
<section id="hooking-add"><title>Add a hook registering function</title>
- <p>During initialisation, the server will call each modules hook
+ <p>During initialization, the server will call each modules hook
registering function, which is included in the module
structure:</p>
yet checks and acts upon the error.</p>
</section>
- <section id="init"><title>Initialisation Routines</title>
+ <section id="init"><title>Initialization Routines</title>
<p>These should now be renamed to better signify where they sit
in the overall process. So the name gets a small change from
<code>mmap_init</code> to <code>mmap_post_config</code>. The arguments
<directivesynopsis>
<name>CryptoIV</name>
-<description>IV (Initialisation Vector) to be used by the crypto filter</description>
+<description>IV (Initialization Vector) to be used by the crypto filter</description>
<syntax>CryptoIV value</syntax>
<default>CryptoIV none</default>
<contextlist><context>server config</context>
</contextlist>
<usage>
- <p>The <directive>CryptoIV</directive> directive allows the IV (initialisation
+ <p>The <directive>CryptoIV</directive> directive allows the IV (initialization
vector) to be specified for the particular URL space. The IV can be read from
a file, or can be set based on the <a href="../expr.html">expression parser</a>,
allowing for flexible scenarios for the setting of keys.</p>
<directivesynopsis>
<name>xml2EncAlias</name>
-<description>Recognise Aliases for encoding values</description>
+<description>Recognize Aliases for encoding values</description>
<syntax>xml2EncAlias <var>charset alias [alias ...]</var></syntax>
<contextlist><context>server config</context></contextlist>