Fix typo and be consistent in using URL instead of url

</summary>

<seealso><module>mod_rewrite</module></seealso> <seealso><a

href="../urlmapping.html">Mapping URLs to the filesystem</a></seealso>

href="../URLmapping.html">Mapping URLs to the filesystem</a></seealso>

<section id="order"><title>Order of Processing</title>

    <p>Aliases and Redirects occuring in different contexts are processed

    <p>Aliases and Redirects occurring in different contexts are processed

    like other directives according to standard <a

    href="../sections.html#mergin">merging rules</a>.  But when multiple

    Aliases or Redirects occur in the same context (for example, in the

    <p>The <directive>Alias</directive> directive allows documents to

    be stored in the local filesystem other than under the

    <directive module="core">DocumentRoot</directive>. URLs with a

    (%-decoded) path beginning with <var>url-path</var> will be mapped

    (%-decoded) path beginning with <var>URL-path</var> will be mapped

    to local files beginning with <var>directory-path</var>.  The

    <var>url-path</var> is case-sensitive, even on case-insensitive

    <var>URL-path</var> is case-sensitive, even on case-insensitive

    file systems.</p>

    <example><title>Example:</title>

    module="mod_alias">AliasMatch</directive> directive.</p>

    <p>Note that if you include a trailing / on the

    <var>url-path</var> then the server will require a trailing / in

    <var>URL-path</var> then the server will require a trailing / in

    order to expand the alias. That is, if you use</p>

    <dl><dd><code>Alias /icons/ /usr/local/apache/icons/</code></dd></dl>

    <p>then the url <code>/icons</code> will not be aliased, as it lacks

    <p>then the URL <code>/icons</code> will not be aliased, as it lacks

    that trailing /. Likewise, if you omit the slash on the

    <var>url-path</var> then you must also omit it from the

    <var>URL-path</var> then you must also omit it from the

    <var>file-path</var>.</p>

    <p>Note that you may need to specify additional <directive

    <p>The full range of <glossary ref="regex">regular expression</glossary>

    power is available.  For example,

    it is possible to construct an alias with case-insensitive

    matching of the url-path:</p>

    matching of the URL-path:</p>

    <example>

      AliasMatch (?i)^/image(.*) /ftp/pub/image$1

    in which case the scheme and hostname of the current server will

    be added.</p>

    <p>Then any request beginning with <em>URL-Path</em> will return a

    <p>Then any request beginning with <em>URL-path</em> will return a

    redirect request to the client at the location of the target

    <em>URL</em>.  Additional path information beyond the matched

    <em>URL-Path</em> will be appended to the target URL.</p>

    <em>URL-path</em> will be appended to the target URL.</p>

    <example><title>Example:</title>

      Redirect /service http://foo2.example.com/service

    <p>As for AliasMatch, the full range of <glossary ref="rexex">regular

    expression</glossary> power is available.

    For example, it is possible to construct an alias with case-insensitive

    matching of the url-path:</p>

    matching of the URL-path:</p>

    <example>

      ScriptAliasMatch (?i)^/cgi-bin(.*) /usr/local/apache/cgi-bin$1