fix xml

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@930742 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/sections.xml b/docs/manual/sections.xml
index 3ef6a1c2566745443d0b8b44feaef9f079fe1578..df2dde4730ae31a9ec53e507223c0c9a2aed7135 100644 (file)
--- a/docs/manual/sections.xml
+++ b/docs/manual/sections.xml
@@ -237,23 +237,23 @@ SetHandler server-status<br />
 </section>
 
 <section id="overlapping-webspace"><title>Overlapping Webspace</title>
-In order to have two overlapping URLs one has to consider the order in which
+<p>In order to have two overlapping URLs one has to consider the order in which
 certain sections or directives are evaluated. For
-<directive type="section" module="core">Location</directive> this would be:
+<directive type="section" module="core">Location</directive> this would be:</p>
 <example>
 &lt;Location /foo&gt;<br />
 &lt;/Location&gt;<br />
 &lt;Location /foo/bar&gt;<br />
 &lt;/Location>
 </example>
-<directive type="section" module="core">Alias</directive>es on the other hand,
-are mapped vice-versa:
+<p><directive type="section" module="core">Alias</directive>es on the other hand,
+are mapped vice-versa:</p>
 <example>
 Alias /foo/bar /srv/www/uncommon/bar<br />
 Alias /foo /srv/www/common/foo<br />
 </example>
-The same is true for the <directive module="mod_proxy">ProxyPass</directive>
-directives:
+<p>The same is true for the <directive module="mod_proxy">ProxyPass</directive>
+directives:</p>
 <example>
 ProxyPass /special-area http://special.example.com smax=5 max=10
 ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On

diff --git a/docs/manual/sections.xml.fr b/docs/manual/sections.xml.fr
index 9374de5472371cb3a4a527107398f40d1bfc2f5f..64d499b3ea1c7eb5003e6d0f656c8e8dad37c01a 100644 (file)
--- a/docs/manual/sections.xml.fr
+++ b/docs/manual/sections.xml.fr
@@ -255,24 +255,24 @@ SetHandler server-status<br />
 </section>
 
 <section id="overlapping-webspace"><title>Espace web imbriqu&eacute;</title>
-Pour contr&ocirc;ler deux URLs imbriqu&eacute;es, on doit tenir compte de l'ordre
+<p>Pour contr&ocirc;ler deux URLs imbriqu&eacute;es, on doit tenir compte de l'ordre
 dans lequel certaines sections ou directives sont &eacute;valu&eacute;es. Pour
 <directive type="section" module="core">Location</directive>, on doit
-avoir :
+avoir :</p>
 <example>
 &lt;Location /foo&gt;<br />
 &lt;/Location&gt;<br />
 &lt;Location /foo/bar&gt;<br />
 &lt;/Location>
 </example>
-Les directives <directive type="section"
-module="core">Alias</directive>, quant &agrave; elles, sont &eacute;valu&eacute;es vice-versa :
+<p>Les directives <directive type="section"
+module="core">Alias</directive>, quant &agrave; elles, sont &eacute;valu&eacute;es vice-versa :</p>
 <example>
 Alias /foo/bar /srv/www/uncommon/bar<br />
 Alias /foo /srv/www/common/foo<br />
 </example>
-Ceci est aussi vrai pour les directives <directive
-module="mod_proxy">ProxyPass</directive> :
+<p>Ceci est aussi vrai pour les directives <directive
+module="mod_proxy">ProxyPass</directive> :</p>
 <example>
 ProxyPass /special-area http://special.example.com smax=5 max=10
 ProxyPass / balancer://mycluster/ stickysession=JSESSIONID|jsessionid nofailover=On