From: Christophe Jaillet <jailletc36@apache.org>
Date: Fri, 24 Aug 2018 19:49:59 +0000 (+0000)
Subject: Fix an example (/foo vs /foo/bar)
X-Git-Tag: 2.4.35~61
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=a0c8e15b0f86e1df1f6736dfa7ff4d13973dac40;p=apache

Fix an example (/foo vs /foo/bar)

Synch with trunk and improve alignment in examples.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1838946 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/sections.xml b/docs/manual/sections.xml
index a1e2461503..339d5cf4a6 100644
--- a/docs/manual/sections.xml
+++ b/docs/manual/sections.xml
@@ -247,7 +247,7 @@ certain sections or directives are evaluated. For
 are mapped vice-versa:</p>
 <highlight language="config">
 Alias "/foo/bar" "/srv/www/uncommon/bar"
-Alias "/foo" "/srv/www/common/foo"
+Alias "/foo"     "/srv/www/common/foo"
 </highlight>
 <p>The same is true for the <directive module="mod_proxy">ProxyPass</directive>
 directives:</p>
@@ -490,7 +490,7 @@ are interpreted, it is important to understand how this works.</p>
         <li>Apart from <directive type="section"
         module="core">Directory</directive>, within each group the sections are
         processed in the order they appear in the configuration files.
-        For example, a request for <em>/foo</em> will match
+        For example, a request for <em>/foo/bar</em> will match
         <code>&lt;Location "/foo/bar"&gt;</code> and 
         <code>&lt;Location "/foo"&gt;</code> (group 4 in this case):
         both sections will be evaluated