svn commit: r1776670 - in /directory/site/trunk/content/api/user-guide: 1-introduction.mdtext 1.2-ldap-in-a-few-words.mdtext

[sm...@apache.org]

Author: smckinney
Date: Sat Dec 31 01:00:34 2016
New Revision: 1776670

URL: http://svn.apache.org/viewvc?rev=1776670&view=rev
Log:
corrections

Modified:
    directory/site/trunk/content/api/user-guide/1-introduction.mdtext
    directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext

Modified: directory/site/trunk/content/api/user-guide/1-introduction.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/1-introduction.mdtext?rev=1776670&r1=1776669&r2=1776670&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/1-introduction.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/1-introduction.mdtext Sat Dec 31 01:00:34 2016
@@ -24,12 +24,12 @@ Notice: Licensed to the Apache Software
 
 This User Guide teaches developers how to use the Apache LDAP API. Throughout these documents, we have interspersed descriptions of features with snippets of code.  These code samples are used by our integration tests as well.
 
-Hopefully there's enough here to get you started -- quickly.  If you fee4l like improving this document or have questions / suggestions, please post to the Apache Directory LDAP API mailing list.  All code and doc contributions are welcomed!
+Hopefully there's enough here to get you started -- quickly.  If you feel like improving this document or have questions / suggestions, please post to the Apache Directory LDAP API mailing list.  All code and doc contributions are welcomed!
 
 ## Contents
 
 *  [1.1 - Java and LDAP](1.1-java-and-ldap.html)
 *  [1.2 - LDAP in a few words](1.2-ldap-in-a-few-words.html)
-*  [1.3 - The Apache LDAP API rational](1.3-apache-ldap-api-rational.html)
+*  [1.3 - The Apache LDAP API rationale](1.3-apache-ldap-api-rational.html)
 *  [1.4 - Preparation to code](1.4-preparation-to-code.html)
 

Modified: directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext?rev=1776670&r1=1776669&r2=1776670&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.mdtext Sat Dec 31 01:00:34 2016
@@ -29,16 +29,16 @@ Notice: Licensed to the Apache Software
 We'll use the term **LDAP** to represent the protocol and **LDAP** server to represent the server that implements it.
 
 ## Features
-An **LDAP** server provides access to entries stored in a backend database. It provides a mechanism for fast searching and retrieval of entries. Its data structure is hierarchical, and uses a schema to manage the definition of the entry's data formats.
+The **LDAP** protocol provides access to entries stored in a **LDAP Server's** database. It provides the mechanism for fast searching and retrieval of entries. Its data structures are hierarchical, and uses a schema to manage the definition of a particular entry's data formats.
 
 An **LDAP** client must first connect to a server and disconnect when finished. Some operations may be performed on the data itself, e.g. searches, modifications and deletions, along with a few others.
 
-**LDAP** servers are extensible, but they all use a common protocol which makes it easy for users to request to interact with them. This API is an example of what **LDAP** is good at: fast data access across servers.
+**LDAP** servers are extensible, but they all use a common protocol which makes it easy for users to request to interact with them, in a way that isn't tied to a particular vendor's implementation. This API is an example of what **LDAP** is good at: fast data access across servers of all types.
 
 ## Characteristics
-**LDAP** servers are fast for retrievals, having been designed specifically for this purpose. But modifications are costly. These characteristics must be understood when writing applications that use an **LDAP** server for data storage.
+**LDAP** servers are fast for retrievals, having been designed specifically for this purpose. But modifications can be costly. These characteristics must be understood when writing applications that use an **LDAP** server for data storage.
 
-Each entry is associated with a location within its corresponding **D**irectory **I**nformation **T**ree, and we use what is known as a **D**istinguished **N**ame (or **Dn**) to describe this address. The base entry is known as the suffix, and all entries beneath it are collectively known as its **DIT**.
+Each entry is associated with a location within its corresponding **D**irectory **I**nformation **T**ree, and we use what is known as a **D**istinguished **N**ame (or **Dn**) to describe this address. The base entry is known as the suffix, it along with all entries beneath it are collectively known as the **DIT**.
 
 ## Programming