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 a1e246150342dbb987fc0b36773f62b2f599abc6..339d5cf4a60e1b3cfd9a17e53b41c7660c4791d8 100644 (file)
--- 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