docs: Fix typo in the idmap_ad manpage.

Karolin
(cherry picked from commit b876e1336bed52e0823e0e88381d223bd6aa95e4)
(cherry picked from commit 611ac35a694930693d2f773d15e59be138261a8e)

diff --git a/docs-xml/manpages-3/idmap_ad.8.xml b/docs-xml/manpages-3/idmap_ad.8.xml
index 766eb85090257a4d0f1f7e10a4e3c303f61befcf..d104c3ea89eea826d509a9b7d31b35ca1c4f2037 100644 (file)
--- a/docs-xml/manpages-3/idmap_ad.8.xml
+++ b/docs-xml/manpages-3/idmap_ad.8.xml
@@ -23,8 +23,8 @@
        extensions. This module implements only the "idmap"
        API, and is READONLY. Mappings must be provided in advance
        by the administrator by adding the posixAccount/posixGroup
-       classess and relative attribute/value pairs to the users and
-       groups objects in AD</para>
+       classes and relative attribute/value pairs to the user and
+       group objects in the AD.</para>
 </refsynopsisdiv>
 
 <refsect1>
@@ -34,7 +34,7 @@
                <varlistentry>
                <term>range = low - high</term>
                <listitem><para>
-                       Defines the available matching uid and gid range for which the
+                       Defines the available matching UID and GID range for which the
                        backend is authoritative. Note that the range acts as a filter.
                        If specified any UID or GID stored in AD that fall outside the
                        range is ignored and the corresponding map is discarded.
@@ -47,7 +47,7 @@
                <listitem><para>
                        Defines the schema that idmap_ad should use when querying
                        Active Directory regarding user and group information.
-                       This can either the RFC2307 schema support included
+                       This can be either the RFC2307 schema support included
                        in Windows 2003 R2 or the Service for Unix (SFU) schema.
                </para></listitem>
                </varlistentry>