[deployment-guide/comm-rel: 690/727] Modified the chapter introduction.

[Jaromir Hradilek]

commit 263913bc7f7b842a3fd20392bb17f4e49a8af1ea
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Wed Sep 29 12:36:17 2010 +0200

    Modified the chapter introduction.

 .../Lightweight_Directory_Access_Protocol_LDAP.xml |   11 ++++++++---
 1 files changed, 8 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml b/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
index 10490cb..88fcfaf 100644
--- a/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
+++ b/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
@@ -4,20 +4,25 @@
 <chapter id="ch-Lightweight_Directory_Access_Protocol_LDAP">
   <title>Lightweight Directory Access Protocol (LDAP)</title>
   <para>
-    The <firstterm>Lightweight Directory Access Protocol</firstterm> (<firstterm>LDAP</firstterm>) is a set of open protocols used to access centrally stored information over a network. It is based on the <firstterm>X.500</firstterm> standard for directory sharing, but is less complex and resource-intensive. For this reason, LDAP is sometimes referred to as "<firstterm>X.500 Lite</firstterm>." The X.500 standard is a directory that contains hierarchical and categorized information, which could include information such as names, addresses, and phone numbers.
+    <systemitem class="protocol">LDAP</systemitem> (Lightweight Directory Access Protocol) is a set of open protocols used to access centrally stored information over a network. It is based on the <systemitem class="protocol">X.500</systemitem> standard for directory sharing, but is less complex and resource-intensive. For this reason, LDAP is sometimes referred to as <quote>X.500 Lite</quote>.
   </para>
   <para>
-    Like X.500, LDAP organizes information in a hierarchal manner using directories. These directories can store a variety of information and can even be used in a manner similar to the Network Information Service (NIS), enabling anyone to access their account from any machine on the LDAP enabled network.
+    Like X.500, LDAP organizes information in a hierarchal manner using directories. These directories can store a variety of information such as names, addresses, or phone numbers, and can even be used in a manner similar to the <firstterm>Network Information Service</firstterm> (<acronym>NIS</acronym>), enabling anyone to access their account from any machine on the LDAP enabled network.
   </para>
   <para>
-    In many cases, LDAP is used as a virtual phone directory, allowing users to easily access contact information for other users. But LDAP is more flexible than a traditional phone directory, as it is capable of referring a querent to other LDAP servers throughout the world, providing an ad-hoc global repository of information. Currently, however, LDAP is more commonly used within individual organizations, like universities, government departments, and private companies.
+    LDAP is commonly used as a virtual phone directory, allowing users to easily access contact information for other users. Additionally, it can refer a user to another LDAP servers throughout the world, and thus provide an ad-hoc global repository of information. However, it is most frequently used within individual organizations such as universities, government departments, and private companies.
   </para>
   <para>
+    This chapter cover the installation and configuration of <application>OpenLDAP 2.4</application>, an open source implementation of the LDAPv2 and LDAPv3 protocols.
+  </para>
+  <!--
+  <para>
     LDAP is a client/server system. The server can use a variety of databases to store a directory, each optimized for quick and copious read operations. When an LDAP client application connects to an LDAP server, it can either query a directory or attempt to modify it. In the event of a query, the server either answers the query locally, or it can refer the querent to an LDAP server which does have the answer. If the client application is attempting to modify information within an LDAP directory, the server verifies that the user has permission to make the change and then adds or updates the information.
   </para>
   <para>
     This chapter refers to the configuration and use of OpenLDAP 2.0, an open source implementation of the LDAPv2 and LDAPv3 protocols.
   </para>
+  -->
   <section id="s1-ldap-adv">
     <title>Why Use LDAP?</title>
     <para>