From 35907494b627fa67f29f56b468dda8e2dbc0b14b Mon Sep 17 00:00:00 2001
From: Chris Darroch <chrisd@apache.org>
Date: Tue, 25 Mar 2008 19:25:42 +0000
Subject: [PATCH] Fix minor typos and capitalizations.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@640952 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/howto/auth.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/manual/howto/auth.xml b/docs/manual/howto/auth.xml
index 24546f09cd..11eb5bd772 100644
--- a/docs/manual/howto/auth.xml
+++ b/docs/manual/howto/auth.xml
@@ -391,7 +391,7 @@ person in</title>
     authentication or authorization method. In fact any number of the 
     providers can be mixed and matched to provide you with exactly the 
     scheme that meets your needs. In the following example, both the 
-    file and ldap based authentication providers are being used.</p>
+    file and LDAP based authentication providers are being used.</p>
 
     <example>
     &lt;Directory /www/docs/private&gt;<br />
@@ -405,17 +405,17 @@ person in</title>
     </example>
 
     <p>In this example the file provider will attempt to authenticate
-    the user first. If it is unable to authenticate the user, the ldap
+    the user first. If it is unable to authenticate the user, the LDAP
     provider will be called. This allows the scope of authentication
     to be broadened if your organization implements more than
     one type of authentication store. Other authentication and authorization
     scenarios may include mixing one type of authentication with a
     different type of authorization. For example, authenticating against
-    a password file yet authorizing against and ldap directory.</p>
+    a password file yet authorizing against an LDAP directory.</p>
 
     <p>Just as multiple authentication providers can be implemented, multiple
     authorization methods can also be used. In this example both file group
-    authorization as well as ldap group authorization is being used.</p>
+    authorization as well as LDAP group authorization is being used.</p>
 
     <example>
     &lt;Directory /www/docs/private&gt;<br />
@@ -471,7 +471,7 @@ person in</title>
 
         <example>
           # if ((user == "John") ||<br />
-          # &nbsp;&nbsp; ((Group == "admin")<br />
+          # &nbsp;&nbsp; ((Group == "admins")<br />
           # &nbsp; &nbsp; &amp;&amp; (ldap-group &lt;ldap-object&gt; contains auth'ed_user)<br />
           # &nbsp; &nbsp; &amp;&amp; ((ldap-attribute dept == "sales")<br />
           # &nbsp; &nbsp; &nbsp; &nbsp; || (file-group contains auth'ed_user))))<br />
@@ -503,7 +503,7 @@ person in</title>
         </example>
 
         <p>By default all <directive module="mod_authz_core">Require</directive> 
-        directives are handled through and OR operation. In other words, if 
+        directives are handled through an OR operation. In other words, if 
         any of the specified authorization methods succeed, then authorization 
         is granted. By enclosing a set of 
         <directive module="mod_authz_core">Require</directive> directives within
-- 
2.40.0