ITS#5076

doc/man/man5/slapd-relay.5

@@ -57,7 +57,7 @@ real naming context.
 Moreover, since
 .B back-relay
 bypasses the real database frontend operations by short-circuiting
-operations thru the internal backend API, the original database
+operations through the internal backend API, the original database
 access rules do not apply but in selected cases, i.e. when the
 backend itself applies access control.
 As a consequence, the instances of the relay database must provide

doc/man/man5/slapd-sql.5

@@ -418,7 +418,7 @@ If we wanted to service LDAP requests with filters like
 .fi
 .LP
 (note how the telephoneNumber match is expanded in multiple wildcards
-to account for interspersed ininfluential chars like spaces, dashes
+to account for interspersed influential chars like spaces, dashes
 and so; this occurs by design because telephoneNumber is defined after 
 a specially recognized syntax).
 So, if we had information about what tables contain values for each
@@ -654,7 +654,7 @@ A directoryString value of the form "__First___Last_"
 (where underscores mean spaces, ASCII 0x20 char) corresponds
 to its prettified counterpart "First_Last"; this is not currently
 honored by back-sql if non-prettified data is written via RDBMS;
-when non-prettified data is written thru back-sql, the prettified 
+when non-prettified data is written through back-sql, the prettified 
 values are actually used instead.
 
 .LP

doc/man/man5/slapo-dynlist.5

@@ -58,7 +58,7 @@ data.
 
 The value
 .B <URL-ad>
-is the name of the attributeDescription that cointains the URI that is 
+is the name of the attributeDescription that contains the URI that is 
 expanded by the overlay; if none is present, no expansion occurs.
 If the intersection of the attributes requested by the search operation 
 (or the asserted attribute for compares) and the attributes listed 

doc/man/man5/slapo-rwm.5

@@ -73,7 +73,7 @@ a portion that is DN-valued), like nameAndOptionalUID,
 whose values are currently not rewritten.
 .LP
 If the foreign type of an attribute mapping is not defined on the local 
-server, it might be desireable to have the attribute values normalized after
+server, it might be desirable to have the attribute values normalized after
 the mapping process. Not normalizing the values can lead to wrong results, 
 when the
 .B rwm

doc/man/man5/slapo-unique.5

@@ -82,7 +82,7 @@ starts with an e.
 It is possible to assert uniqueness upon all non-operational
 attributes except those listed by prepending the keyword
 .B ignore
-If not configured, all non-operational (eg, system) attributes must be
+If not configured, all non-operational (e.g., system) attributes must be
 unique. Note that the
 .B attributes
 list of an

doc/man/man8/slapd.8

@@ -253,7 +253,7 @@ registers at SLP DAs with the three SLP attributes tree, server-type and server-
 that have the values given above.
 This allows to specifically query the SLP DAs for LDAP servers holding the
 .I production
-tree in case multiple trees are availabe.
+tree in case multiple trees are available.
 .RE
 .SH EXAMPLES
 To start