doc/guide/admin/{backends,monitoringslapd}.sdf: typos

doc/guide/admin/backends.sdf

@@ -54,7 +54,7 @@ the whole of the {{slapd-ldap(5)}} options.
 For example, the {{SECT: Translucent Proxy}}, which retrieves entries from a 
 remote LDAP server that can be partially overridden by the defined database, has
 only four specific {{translucent-}} directives, but can be configured using any 
-of the normal {{slapd-ldap(5)}} options. See {[slapo-translucent(5)}} for details.
+of the normal {{slapd-ldap(5)}} options. See {{slapo-translucent(5)}} for details.
 
 Other {{SECT: Overlays}} allow you to tag directives in front of a normal 
 {{slapd-ldap(5)}} directive. For example, the {{slapo-chain(5)}} overlay does 

doc/guide/admin/monitoringslapd.sdf

@@ -20,7 +20,7 @@ returns objects in response to search requests in the {{cn=Monitor}}
 subtree.  Each object contains information about a particular aspect
 of the server.  The information is held in a combination of user
 applications and operational attributes.   This information can be
-access with {{ldapsearch(1)}}, with any general-purpose LDAP browser,
+accessed with {{ldapsearch(1)}}, with any general-purpose LDAP browser,
 or with specialized monitoring tools.  The {{SECT:Accessing Monitoring
 Information}} section provides a brief tutorial on how to use
 {{ldapsearch}}(1) to access monitoring information, while the

doc/guide/admin/security.sdf

@@ -290,7 +290,7 @@ Note: This is not the same as using a SASL mechanism to
 authenticate the LDAP session.
 
 Pass-Through authentication works only with plaintext passwords, as 
-used in the "simple bind" and "SASL PLAIN" authentication mechanisms.}}
+used in the "simple bind" and "SASL PLAIN" authentication mechanisms.
 
 Pass-Through authentication is selective: it only affects users whose
 {{userPassword}} attribute has a value marked with the "{SASL}"