break lines in <example>

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

diff --git a/docs/manual/howto/auth.xml b/docs/manual/howto/auth.xml
index 8814fb48018e55a96f4705674c992afe6b8cbdf0..39054ec1a94fc46c969059fcd0e6a5d07f32c28c 100644 (file)
--- a/docs/manual/howto/auth.xml
+++ b/docs/manual/howto/auth.xml
@@ -39,7 +39,7 @@ authorization process.  You will usually need to choose at least one
 module from each group.</p>
 
 <ul>
-  <li>Authentication type (see the 
+  <li>Authentication type (see the
       <directive module="core">AuthType</directive> directive)
     <ul>
       <li><module>mod_auth_basic</module></li>
@@ -57,7 +57,7 @@ module from each group.</p>
       <li><module>mod_authnz_ldap</module></li>
     </ul>
   </li>
-  <li>Authorization (see the 
+  <li>Authorization (see the
       <directive module="core">Require</directive> directive)
     <ul>
       <li><module>mod_authnz_ldap</module></li>
@@ -153,7 +153,7 @@ module from each group.</p>
     came with Apache. This will be located in the <code>bin</code> directory
     of wherever you installed Apache. If you have installed Apache from
     a third-party package, it may be in your execution path.</p>
-    
+
     <p>To create the file, type:</p>
 
     <example>
@@ -261,24 +261,24 @@ that several criteria may be considered when trying to decide if a particular us
 will be granted admission. Satisfy can take as an argument one of two options - <code>all</code>
 or <code>any</code>. By default, it is assumed that the value is <code>all</code>. This means that if several
 criteria are specified, then all of them must be met in order for someone to get in.
-However, if set to <code>any</code>, then several criteria may be specified, but if 
+However, if set to <code>any</code>, then several criteria may be specified, but if
 the user satisfies any of these, then they will be granted entrance.</p>
 
-<p>An example of this is using access control to assure that, although a resource 
+<p>An example of this is using access control to assure that, although a resource
 is password protected from outside your network, all hosts inside the network
 will be given unauthenticated access to the resource. This would be accomplished
 by using the Satisfy directive, as shown below.</p>
 
 <example>
-&lt;Directory /usr/local/apache/htdocs/sekrit&gt;
-  AuthType Basic
-  AuthName intranet
-  AuthUserFile /www/passwd/users
-  AuthGroupFile /www/passwd/groups
-  Require group customers
-  Order allow,deny
-  Allow from internal.com
-  Satisfy any
+&lt;Directory /usr/local/apache/htdocs/sekrit&gt;<br />
+  AuthType Basic<br />
+  AuthName intranet<br />
+  AuthUserFile /www/passwd/users<br />
+  AuthGroupFile /www/passwd/groups<br />
+  Require group customers<br />
+  Order allow,deny<br />
+  Allow from internal.com<br />
+  Satisfy any<br />
 &lt;/Directory&gt;
 </example>
 
@@ -408,11 +408,11 @@ person in</title>
     contain some more information about how this all works.
     <module>mod_authn_alias</module> can also help in simplifying certain
     authentication configurations.</p>
-    
+
     <p>The various ciphers supported by Apache for authentication data are
     explained in <a href="../misc/password_encryptions.html">Password
     Encryptions</a>.</p>
-    
+
     <p>And you may want to look at the <a href="access.html">Access
     Control</a> howto, which discusses a number of related topics.</p>