ITS#1271 typos

doc/guide/admin/install.sdf

@@ -180,7 +180,7 @@ environment variables.
 
 >	[[env] settings] ./configure [options]
 
-As an example, let's assume that we want install OpenLDAP with
+As an example, let's assume that we want to install OpenLDAP with
 LDBM backend and TCP wrapper support.  By default, LDBM
 is enabled and TCP wrappers is not.  So, we just need to specify
 {{EX:--with-wrappers}} to include TCP wrapper support:
@@ -240,7 +240,7 @@ by your configuration.
 
 H2: Installing the Software
 
-One you have successfully tested the software, you are ready to install it.
+Once you have successfully tested the software, you are ready to install it.
 You will need to have write permission
 to the installation directories you specified when you ran configure.
 By default OpenLDAP is installed in {{F:/usr/local}}.  If you changed this

doc/guide/admin/intro.sdf

@@ -131,7 +131,7 @@ be useful to you.
 
 {{How is the information protected from unauthorized access?}} Some
 directory services provide no protection, allowing anyone to see
-the information. LDAP provides a mechanisms for a client to
+the information. LDAP provides a mechanism for a client to
 authenticate, or prove its identity to a directory server, paving
 the way for rich access control to protect the information the
 server contains.  LDAP also supports privacy and integrity security

doc/guide/admin/quickstart.sdf

@@ -14,8 +14,8 @@ other materials provided with the distribution (e.g. the {{F:INSTALL}}
 document) or on the OpenLDAP web site (in particular, the
 OpenLDAP Software FAQ).
 
-If you intend to run OpenLDAP seriously, you should review the all
-of this document before attempt to install the software.
+If you intend to run OpenLDAP seriously, you should review all
+of this document before attempting to install the software.
 
 Note: This quick start guide does not use strong authentication
 nor any integrity or confidential protection services.  These

doc/guide/admin/schema.sdf

@@ -134,7 +134,7 @@ a few letters to localize the changes to your organization.
 The smaller the organization, the longer your prefix should
 be.
 
-In the examples below, we have choosen a short prefix '{{EX:my}}'
+In the examples below, we have chosen a short prefix '{{EX:my}}'
 (to save space).  Such a short prefix would only be suitable for
 a very large, global organization.  For a small, local organization,
 we recommend something like '{{EX:deFirm}}' (German company) or