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

[sm...@apache.org]

Author: smckinney
Date: Sat Dec 31 03:15:33 2016
New Revision: 1776682

URL: http://svn.apache.org/viewvc?rev=1776682&view=rev
Log:
more clean

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=1776682&r1=1776681&r2=1776682&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 03:15:33 2016
@@ -33,7 +33,7 @@ The **LDAP** protocol provides access to
 
 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 simplifies application access 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.
+**LDAP** servers are extensible, but they all use a common protocol providing access to the data in a way that isn't tied to a particular vendor's implementation.
 
 ## Characteristics
 **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.