ITS#6609

CHANGES

@@ -14,6 +14,8 @@ OpenLDAP 2.4.24 Engineering
 	Fixed slapo-pcache to ignore undefined attrs (ITS#6600)
 	Fixed slapo-ppolicy don't update opattrs on consumers (ITS#6608)
 	Fixed slapo-syncprov to send error if consumer is newer (ITS#6606)
+	Documentation
+		admin24 guide typo fixes (ITS#6609)
 
 OpenLDAP 2.4.23 Release (2010/06/30)
 	Fixed libldap to return server's error code (ITS#6569)

doc/guide/admin/access-control.sdf

@@ -826,7 +826,7 @@ This ACL grants read permissions to authenticated users while denying others
 
 H3: Controlling rootdn access
 
-You could specify the {{rootdn}} in {{slapd.conf}}(5) or {[slapd.d}} without 
+You could specify the {{rootdn}} in {{slapd.conf}}(5) or {{slapd.d}} without 
 specifying a {{rootpw}}. Then you have to add an actual directory entry with 
 the same dn, e.g.:
 
@@ -876,7 +876,7 @@ One can then grant access to the members of this this group by adding appropriat
 >        by group.exact="cn=Administrators,dc=example,dc=com" write  
 >        by * auth
 
-Like by {[dn}} clauses, one can also use {{expand}} to expand the group name 
+Like by {{dn}} clauses, one can also use {{expand}} to expand the group name 
 based upon the regular expression matching of the target, that is, the to {{dn.regex}}). 
 For instance,
 

doc/guide/admin/appendix-common-errors.sdf

@@ -11,7 +11,7 @@ H2: Common causes of LDAP errors
 
 H3: ldap_*: Can't contact LDAP server
 
-The {[B:Can't contact LDAP server}} error is usually returned when the LDAP 
+The {{B:Can't contact LDAP server}} error is usually returned when the LDAP 
 server cannot be contacted. This may occur for many reasons:
 
 * the LDAP server is not running; this can be checked by running, for example,