Manpage typos

doc/man/man1/ldapsearch.1

@@ -128,7 +128,7 @@ makes control critical.
 .BI \-S \ attribute
 Sort the entries returned based on \fIattribute\fP. The default is not
 to sort entries returned.  If \fIattribute\fP is a zero-length string (""),
-the entries are sorted by the components of their Distingished Name.  See
+the entries are sorted by the components of their Distinguished Name.  See
 .BR ldap_sort (3)
 for more details. Note that
 .B ldapsearch

doc/man/man3/lber-types.3

@@ -88,7 +88,7 @@ points to
 .B bv_len
 octets.
 .B bv_val
-is not necessarly terminated by a NUL (zero) octet.
+is not necessarily terminated by a NUL (zero) octet.
 .BR ber_bvfree ()
 frees a BerValue, pointed to by \fIbv\fP, returned from this API.  If \fIbv\fP
 is NULL, the routine does nothing.

doc/man/man3/ldap.3

@@ -60,9 +60,9 @@ Errors can be interpreted by calling
 .BR ldap_err2string (3).
 .SH LDAP versions
 This library supports version 3 of the Lightweight Directory Access
-Protocol (LDAPv3) as defined in RFC 3377.  It also supports a varient
+Protocol (LDAPv3) as defined in RFC 3377.  It also supports a variant
 of version 2 of LDAP as defined by U-Mich LDAP and, to some degree,
-RFC 1777.  Version 2 (all varients) should be viewed as obsolete.
+RFC 1777.  Version 2 (all variants) should be viewed as obsolete.
 Version 3 should be used instead.
 .LP
 For backwards compatibility reasons, the library defaults to version 2.

doc/man/man3/ldap_get_dn.3

@@ -184,7 +184,7 @@ is used to turn a DN as returned by
 .BR ldap_get_dn (3)
 into a more user-friendly form, stripping off all type names.  See
 "Using the Directory to Achieve User Friendly Naming" (RFC 1781)
-for more details on the UFN format.  Due to the ambigious nature
+for more details on the UFN format.  Due to the ambiguous nature
 of the format, it is generally only used for display purposes.
 The space for the UFN returned is obtained dynamically and the user
 is responsible for freeing it via a call to

doc/man/man3/ldap_result.3

@@ -62,13 +62,13 @@ the responses of a search operation.
 .LP
 A search response is made up of zero or
 more search entries, zero or more search references, and zero or
-more extended parital responses followed by a search result.  If
+more extended partial responses followed by a search result.  If
 \fIall\fP is set to 0, search entries will be returned one at a
 time as they come in, via separate calls to
 .BR ldap_result() .
 If it's set to 1, the search
 response will only be returned in its entirety, i.e., after all entries,
-all references, all extended parital responses, and the final search
+all references, all extended partial responses, and the final search
 result have been received.
 .LP
 Upon success, the type of the result received is returned and the

doc/man/man3/ldap_schema.3

@@ -119,7 +119,7 @@ int code;
 These routines are used to parse schema definitions in the syntax
 defined in RFC 2252 into structs and handle these structs.  These
 routines handle four kinds of definitions: syntaxes, matching rules,
-attribute types and objectclasses.  For each definition kind, four
+attribute types and object classes.  For each definition kind, four
 routines are provided.
 .LP
 .B ldap_str2xxx()

doc/man/man3/ldap_search.3

@@ -56,7 +56,7 @@ the message id of the operation it initiated.
 \fIScope\fP is the scope of the search and should be one of LDAP_SCOPE_BASE,
 to search the object itself,
 LDAP_SCOPE_ONELEVEL, to search the object's immediate children,
-or LDAP_SCOPE_SUBTREE, to search the object and all its descendents.
+or LDAP_SCOPE_SUBTREE, to search the object and all its descendants.
 .LP
 \fIFilter\fP is a string
 representation of the filter to apply in the search.  Simple filters

doc/man/man5/ldap.conf.5

@@ -55,7 +55,8 @@ The different configuration options are:
 Specifies the URI(s) of an LDAP server(s) to which the
 .I LDAP 
 library should connect.  The URI scheme may be either
-.BR ldap or
+.B ldap
+or
 .B ldaps 
 which refer to LDAP over TCP and LDAP over SSL (TLS) respectively.
 Each server's name can be specified as a
@@ -260,7 +261,7 @@ is immediately terminated. This is the default setting.
 .TP
 .B TLS_CRLCHECK <level>
 Specifies if the Certificate Revocation List (CRL) of the CA should be 
-used to verify if the server certicates have not been revoked. This
+used to verify if the server certificates have not been revoked. This
 requires
 .B TLS_CACERTDIR
 parameter to be set.

doc/man/man5/ldif.5

@@ -38,7 +38,7 @@ or tab, e.g.,
 .ft
 .fi
 .LP
-Lines beginning with a sharpe sign ('#') are ignored.
+Lines beginning with a sharp sign ('#') are ignored.
 .LP
 Multiple attribute values are specified on separate lines, e.g.,
 .LP

doc/man/man5/slapd-ldap.5

@@ -294,7 +294,7 @@ in conjunction with Proxy Authorization.
 .B rebind-as-user {NO|yes}
 If this option is given, the client's bind credentials are remembered
 for rebinds when chasing referrals.  Useful when
-\fBchase-referrals\fP is set to \fByes\P, useless otherwise.
+\fBchase-referrals\fP is set to \fByes\fP, useless otherwise.
 
 .TP
 .B chase-referrals {YES|no}
@@ -317,7 +317,7 @@ enable if the remote server supports absolute filters
 (see \fIdraft-zeilenga-ldap-t-f\fP for details).
 If set to
 .BR discover ,
-support is detected by reading the remote server's rootDSE.
+support is detected by reading the remote server's root DSE.
 
 .SH BACKWARD COMPATIBILITY
 The LDAP backend has been heavily reworked between releases 2.2 and 2.3;
@@ -360,7 +360,7 @@ and may be dismissed in the future.
 .B idassert-authcDN "<administrative DN for proxyAuthz purposes>"
 DN which is used to propagate the client's identity to the target
 by means of the proxyAuthz control when the client does not
-belong to the DIT fragment that is being proxyied by back-ldap.
+belong to the DIT fragment that is being proxied by back-ldap.
 This directive is obsoleted by
 .BR idassert-bind ,
 and may be dismissed in the future.

doc/man/man5/slapd-ldbm.5

@@ -53,7 +53,7 @@ Flush dirty database buffers to disk every
 seconds.
 Implies
 .B dbnosync
-(ie. indvidual updates are no longer written to disk).
+(ie. individual updates are no longer written to disk).
 It attempts to avoid syncs during periods of peak activity by waiting
 .B <delayinterval>
 seconds if the server is busy, repeating this delay up to

doc/man/man5/slapd-ldif.5

@@ -48,6 +48,6 @@ default slapd configuration file
 .SH SEE ALSO
 .BR slapd.conf (5),
 .BR slapd (8),
-.BR LDIF (5).
+.BR ldif (5).
 .SH AUTHOR
 Eric Stokes

doc/man/man5/slapd-meta.5

@@ -135,7 +135,7 @@ Multiple URIs may be defined in a single argument.  The URIs must
 be separated by TABs (e.g. '\\t'; commas or spaces, unlike back-ldap,
 will not work,
 because they are legal in the <naming context>, and we don't want to use
-URL-encoded <namimg context>s), and the additional URIs must have
+URL-encoded <naming context>s), and the additional URIs must have
 no <naming context> part.  This causes the underlying library
 to contact the first server of the list that responds.
 .RE
@@ -191,12 +191,12 @@ enable if the remote server supports absolute filters
 (see \fIdraft-zeilenga-ldap-t-f\fP for details).
 If set to
 .BR discover ,
-support is detected by reading the remote server's rootDSE.
+support is detected by reading the remote server's root DSE.
 
 .TP
 .B onerr {CONTINUE|stop}
 This directive allows to select the behavior in case an error is returned
-by one targe during a search. 
+by one target during a search.
 The default, \fBcontinue\fP, consists in continuing the operation, 
 trying to return as much data as possible.
 If this statement is set to \fBstop\fP, the search is terminated as soon 
@@ -405,7 +405,7 @@ of flags.
 The underlying concept is to build a lightweight rewrite module
 for the slapd server (initially dedicated to the LDAP backend).
 .SH Passes
-An incoming string is matched agains a set of rules.
+An incoming string is matched against a set of rules.
 Rules are made of a regex match pattern, a substitution pattern
 and a set of actions, described by a set of flags.
 In case of match a string rewriting is performed according to the
@@ -415,7 +415,7 @@ The actions, if any, are finally performed.
 The substitution pattern allows map resolution of substrings.
 A map is a generic object that maps a substitution pattern to a value.
 The flags are divided in "Pattern matching Flags" and "Action Flags";
-the former alter the regex match pattern behaviorm while the latter
+the former alter the regex match pattern behavior while the latter
 alter the action that is taken after substitution.
 .SH "Pattern Matching Flags"
 .TP
@@ -527,7 +527,7 @@ operation structure which can be dereferenced later; operator
 assigns a variable in the rewrite context scope; operator
 .B &&
 assigns a variable that scopes the entire session, e.g. its value
-can be derefenced later by other rewrite contexts
+can be dereferenced later by other rewrite contexts
 .TP
 .B *
 variable dereferencing; <name> must refer to a variable that is
@@ -619,7 +619,7 @@ altering too much the configuration file).
 <Context name> is the name that identifies the context, i.e. the name
 used by the application to refer to the set of rules it contains.
 It is used also to reference sub contexts in string rewriting.
-A context may aliase another one.
+A context may alias another one.
 In this case the alias context contains no rule, and any reference to
 it will result in accessing the aliased one.
 .TP

doc/man/man5/slapd-perl.5

@@ -58,7 +58,7 @@ It arguments are as follows:
   * object reference
   * base DN
   * scope
-  * alias deferencing policy
+  * alias dereferencing policy
   * size limit
   * time limit
   * filter string
@@ -161,7 +161,7 @@ filter in the search request), rather than search results to be
 returned directly to the client.
 .SH EXAMPLE
 There is an example Perl module `SampleLDAP' in the slapd/back-perl/
-direcetory in the OpenLDAP source tree.
+directory in the OpenLDAP source tree.
 .SH ACCESS CONTROL
 The
 .B passwd

doc/man/man5/slapd-sql.5

@@ -105,7 +105,7 @@ Do not use the subtree condition when the searchBase is the database
 suffix, and the scope is subtree; rather collect all entries.
 
 .RE
-.SH STAMEMENT CONFIGURATION
+.SH STATEMENT CONFIGURATION
 These options specify SQL query templates for loading schema mapping
 metainformation, adding and deleting entries to ldap_entries, etc.
 All these and subtree_cond should have the given default values.
@@ -250,7 +250,7 @@ or double quotes.
 .B has_ldapinfo_dn_ru { NO | yes }
 Explicitly inform the backend whether the dn_ru column
 (DN in reverse uppercased form) is present in table \fIldap_entries\fP.
-Overrides automatic check (this is required, ofr instance,
+Overrides automatic check (this is required, for instance,
 by PostgreSQL/unixODBC).
 This is \fIexperimental\fP and may change in future releases.
 
@@ -642,7 +642,7 @@ to existing RDBMS storages that need to be published in LDAP form.
 .LP
 The \fBhasSubordintes\fP operational attribute is honored by back-sql
 in search results and in compare operations; it is partially honored
-also in filtering.  Owing to design limitations, a (braindead?) filter
+also in filtering.  Owing to design limitations, a (brain-dead?) filter
 of the form
 \fB(!(hasSubordinates=TRUE))\fP
 will give no results instead of returning all the leaf entries, because

doc/man/man5/slapd.access.5

@@ -853,7 +853,7 @@ The
 .B modify
 operation requires 
 .B write (=w)
-privileges on the attibutes being modified.
+privileges on the attributes being modified.
 .LP
 The
 .B modrdn
@@ -950,7 +950,7 @@ in
 and
 .B <who>
 clauses, to avoid possible incorrect specifications of the access rules 
-as well as for performance (avoid unrequired regex matching when an exact
+as well as for performance (avoid unnecessary regex matching when an exact
 match suffices) reasons.
 .LP
 An administrator might create a rule of the form:

doc/man/man5/slapd.conf.5

@@ -944,7 +944,7 @@ setting must be chosen to enable SASL EXTERNAL authentication.
 .TP
 .B TLSCRLCheck <level>
 Specifies if the Certificate Revocation List (CRL) of the CA should be 
-used to verify if the client certicates have not been revoked. This
+used to verify if the client certificates have not been revoked. This
 requires
 .B TLSCACertificatePath
 parameter to be set.
@@ -1155,13 +1155,13 @@ The
 .BR unchecked
 specifier sets a limit on the number of candidates a search request is allowed
 to examine.
-The rationale behind it is that searches for non-properly indicized
+The rationale behind it is that searches for non-properly indexed
 attributes may result in large sets of candidates, which must be 
 examined by
 .BR slapd (8)
 to determine whether they match the search filter or not.
 The
-.B unckeched
+.B unchecked
 limit provides a means to drop such operations before they are even 
 started.
 If the selected candidates exceed the 

doc/man/man5/slapd.plugin.5

@@ -106,7 +106,7 @@ its value also affects the plugin search path.
 In general the search path is made of colon-separated paths; usually
 the user-defined path is searched first; then the value of the
 \fILTDL_LIBRARY_PATH\fP environment variable, if defined, is used;
-finally, the systemi-specific dynamic load path is attempted (e.g. on
+finally, the system-specific dynamic load path is attempted (e.g. on
 Linux the value of the environment variable \fILD_LIBRARY_PATH\fP).
 Please carefully read the documentation of ltdl because its behavior 
 is very platform dependent.

doc/man/man5/slapo-accesslog.5

@@ -120,7 +120,7 @@ class is as follows:
 .RE
 .P
 Note that all of the OIDs used in the logging schema currently reside
-under the OpenLDAP Experimental branch. It is anticipated that thay
+under the OpenLDAP Experimental branch. It is anticipated that they
 will migrate to a Standard branch in the future.
 
 An overview of the attributes follows:
@@ -164,7 +164,8 @@ session by a Bind request (if any) but may be altered in various
 circumstances.
 
 The
-.BR reqControls and
+.B reqControls
+and
 .B reqRespControls
 attributes carry any controls sent by the client on the request and returned
 by the server in the response, respectively. The attribute values are just

doc/man/man5/slapo-chain.5

@@ -34,7 +34,7 @@ database or to other stacked overlays.
 .LP
 There are no chain overlay specific directives; however, directives 
 related to the \fIldap\fP database that is implicitly instantiated 
-by the overlay may assume a special meaning when used in conjuction 
+by the overlay may assume a special meaning when used in conjunction
 with this overlay.  They are described in
 .BR slapd-ldap (5).
 .TP