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

[sm...@apache.org]

Author: smckinney
Date: Sat Dec 31 00:42:34 2016
New Revision: 1776668

URL: http://svn.apache.org/viewvc?rev=1776668&view=rev
Log:
mroe

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

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=1776668&r1=1776667&r2=1776668&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 00:42:34 2016
@@ -38,11 +38,11 @@ An **LDAP** client must first connect to
 ## 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.
 
-Each entry is associated with a location within it's corresponding **D**irectory **I**nformation **T**ree, and we use what's called 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, and all entries beneath it are collectively known as its **DIT**.
 
 ## Programming 
 
-**LDAP** is a part of the **IT** landscape and so it's unavoidable that we must deal with it. **LDAP** servers are used to manage authentication, authorizations, demographic info and more. It's very likely that you will have to write some code to access data over **LDAP**, and existing **API**s aren't quite up to the task. This **LDAP API** has been designed to simplify usage.
+**LDAP** is a part of the **IT** landscape and so it's necessary to learn how to deal with it. **LDAP** servers are used to manage authentications, authorizations, demographic information about users and more. It's very likely that you will have to write some code to access data with **LDAP** at some point, and existing **API**s aren't quite up to the task. This **LDAP API** has been designed to simplify usage and ensure proper interaction with the server.
 
 ## Going further