svn commit: r1776809 - /directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext

[sm...@apache.org]

Author: smckinney
Date: Sat Dec 31 18:07:16 2016
New Revision: 1776809

URL: http://svn.apache.org/viewvc?rev=1776809&view=rev
Log:
minor cleanup

Modified:
    directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext

Modified: directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext?rev=1776809&r1=1776808&r2=1776809&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.mdtext Sat Dec 31 18:07:16 2016
@@ -35,7 +35,7 @@ So what makes the development of our new
 There are many reasons and we'll discuss them throughout this chapter.
 
 ## History
-The Apache Directory Server project was started using the **JNDI** library, but many of its **LDAP** structures were developed in-house because **JNDI** was ineffective for interacting with **LDAP** directories.  It wasn't convenient for us to use JNDI.  This means it won't be for you either.  Eventually, all of the necessary **LDAP** data structures (_Attribute_, _Entry_, _DN_, ...) were implemented again by us.
+The Apache Directory Server project was started using the **JNDI** library, but many of its **LDAP** structures were developed in-house because **JNDI** was ineffective for interacting with **LDAP** directories.  It wasn't convenient for us to use JNDI which means it won't be for you either.  Eventually, all of the necessary **LDAP** data structures (_Attribute_, _Entry_, _DN_, ...) were implemented again by us.
 
 At some point we needed to communicate with other **LDAP** servers without using the **JNDI** library, so we developed our own _LdapConnection_ class. This was the first step toward a full **Java API** specifically designed for LDAP usage on the Java platform.
 
@@ -53,6 +53,6 @@ Despite these fits and starts, a consens
 ## Result
 Our newly defined **API** fulfills all of these aspects. 
 
-We needed to ensure our **LDAP API** was made available to the masses. Because the Apache Software Foundation values community over code, this code was the result of collaboration, and our users are a necessary part of this process.  Every time a user finds and reports a bug we have the opportunity to provide a better version of this **API** for everyone who uses it.
+We needed to ensure our **LDAP API** was made available to the masses. Because the Apache Software Foundation values community over code, this code was the result of collaboration, and our users are a necessary part of this process.  Every time a user finds and reports a bug we have the opportunity to provide a better version of this **API**.
 
-In the end, we're proud to deliver a useful **API** that everyone can use, including our sub-projects like Apache Directory Server, Apache Directory Studio, and most recently Apache Fortress. 
+In the end, we're proud to deliver a powerful new Java LDAP API, that is available for everyone to use, including our sub-projects like Apache Directory Server, Apache Directory Studio and most recently -- Apache Fortress.