[deployment-guide/comm-rel: 708/727] (multiple): fix BZ#640169: 'the the' instances

Tue Oct 19 13:25:20 UTC 2010

commit 9fe8dbae7f39080c55b0c2664b7f9058403dc22c
Author: Douglas Silas <dhensley at redhat.com>
Date:   Tue Oct 5 12:52:18 2010 +0200

    (multiple): fix BZ#640169: 'the the' instances

 .../Lightweight_Directory_Access_Protocol_LDAP.xml |    4 ++--
 en-US/Network_Configuration.xml                    |    2 +-
 en-US/Printer_Configuration.xml                    |    2 +-
 en-US/Yum.xml                                      |    2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)
---

diff --git a/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml b/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
index f05e185..e0926ea 100644
--- a/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
+++ b/en-US/Lightweight_Directory_Access_Protocol_LDAP.xml
@@ -196,7 +196,7 @@
             </entry>
             <entry>
               <para>
-                A package containing <systemitem class="resource">mod_authz_ldap</systemitem>, the LDAP authorization module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. Note that the <systemitem class="resource">mod_ssl</systemitem> module is required when using the <systemitem class="resource">mod_authz_ldap</systemitem> module. 
+                A package containing <systemitem class="resource">mod_authz_ldap</systemitem>, the LDAP authorization module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. Note that the <systemitem class="resource">mod_ssl</systemitem> module is required when using the <systemitem class="resource">mod_authz_ldap</systemitem> module.
               </para>
             </entry>
           </row>
@@ -739,7 +739,7 @@ group: files ldap</screen>
     <section id="s2-ldap-pamd">
       <title>PAM and LDAP</title>
       <para>
-        To have standard PAM-enabled applications use LDAP for authentication, run the <application>Authentication Configuration Tool</application> (<command>system-config-authentication</command>) and select <guilabel>Enable LDAP Support</guilabel> under the the <guilabel>Authentication</guilabel> tab. For more information about configuring PAM, refer to the <citetitle pubwork="chapter">Pluggable Authentication Modules (PAM)</citetitle> chapter of the &MAJOROSVER; <citetitle>Security Guide</citetitle> and the PAM man pages.
+        To have standard PAM-enabled applications use LDAP for authentication, run the <application>Authentication Configuration Tool</application> (<command>system-config-authentication</command>) and select <guilabel>Enable LDAP Support</guilabel> under the <guilabel>Authentication</guilabel> tab. For more information about configuring PAM, refer to the <citetitle pubwork="chapter">Pluggable Authentication Modules (PAM)</citetitle> chapter of the &MAJOROSVER; <citetitle>Security Guide</citetitle> and the PAM man pages.
       </para>
     </section>
     <section id="s2-ldap-migrate">
diff --git a/en-US/Network_Configuration.xml b/en-US/Network_Configuration.xml
index 62efa1f..9b69636 100644
--- a/en-US/Network_Configuration.xml
+++ b/en-US/Network_Configuration.xml
@@ -1013,7 +1013,7 @@ NetworkManager (pid  1527) is running...
         id="sec-Configuring_TLS_Transport_Level_Security_Settings">
         <title>Configuring TLS (Transport Level Security) Settings</title>
         <para>With Transport Level Security, the client and server mutually authenticate using the TLS protocol. The server demonstrates that it holds a digital certificate, the client proves its own identity using its client-side certificate, and key information is exchanged. Once authentication is complete, the TLS tunnel is no longer used. Instead, the client and server use the exchanged keys to encrypt data using AES, TKIP or WEP.</para>
-        <para>The fact that certificates must be distributed to all clients who want to authenticate means that the the EAP-TLS authentication method is very strong, but also more complicated to set up. Using TLS security requires the overhead of a public key infrastructure (PKI) to manage certificates. The benefit to TLS security is that a compromised password does not allow access to the (W)LAN: an intruder must also have access to the authenticating client's private key.</para>
+        <para>The fact that certificates must be distributed to all clients who want to authenticate means that the EAP-TLS authentication method is very strong, but also more complicated to set up. Using TLS security requires the overhead of a public key infrastructure (PKI) to manage certificates. The benefit to TLS security is that a compromised password does not allow access to the (W)LAN: an intruder must also have access to the authenticating client's private key.</para>
         <variablelist>
           <varlistentry>
             <term>
diff --git a/en-US/Printer_Configuration.xml b/en-US/Printer_Configuration.xml
index d7f14bf..f972a63 100644
--- a/en-US/Printer_Configuration.xml
+++ b/en-US/Printer_Configuration.xml
@@ -502,7 +502,7 @@
       <primary>printer configuration</primary>
       <secondary>managing print jobs</secondary>
     </indexterm>
-    <para>When you send a print job to the printer daemon, such as printing a text file from <application>Emacs</application> or printing an image from <application>The GIMP</application>, the print job is added to the print spool queue. The print spool queue is a list of print jobs that have been sent to the printer and information about each print request, such as the status of the request, the the job number, and more.</para>
+    <para>When you send a print job to the printer daemon, such as printing a text file from <application>Emacs</application> or printing an image from <application>The GIMP</application>, the print job is added to the print spool queue. The print spool queue is a list of print jobs that have been sent to the printer and information about each print request, such as the status of the request, the job number, and more.</para>
     <para>During the printing process, the Printer Status icon appears in the <application>Notification Area</application> on the panel. To check the status of a print job, double click the Printer Status, which displays a window similar to <xref
         linkend="fig-gnome-print-manager-list"/>.</para>
     <figure
diff --git a/en-US/Yum.xml b/en-US/Yum.xml
index f795778..eb32ada 100644
--- a/en-US/Yum.xml
+++ b/en-US/Yum.xml
@@ -1058,7 +1058,7 @@ enabled=1
         <secondary>plugins</secondary>
         <tertiary>yum-presto</tertiary>
       </indexterm>
-      <para>The <application>presto</application> plugin adds support to <application>Yum</application> for downloading <firstterm>delta RPM</firstterm> packages, during updates, from repositories which have <application>presto</application> metadata enabled. Delta RPMs contain only the differences between the version of the the package installed on the client requesting the RPM package and the updated version in the repository. Downloading a delta RPM is much quicker than downloading the entire updated package, and can speed up updates considerably. Once the delta RPMs are downloaded, they must be rebuilt (the difference applied to the currently-installed package to create the full updated package) on the installing machine, which takes CPU time. Using delta RPMs is therefore a tradeoff between time-to-download, which depends on the network connection, and time-to-rebuild, which is CPU-bound. Using the <application>presto</application> plugin is recommended for fast machine
 s and systems with slower network connections, while slower machines on very fast connections <emphasis>may</emphasis> benefit more from downloading normal RPM packages, i.e. by disabling <application>presto</application>. The <application>presto</application> plugin is enabled by default.</para>
+      <para>The <application>presto</application> plugin adds support to <application>Yum</application> for downloading <firstterm>delta RPM</firstterm> packages, during updates, from repositories which have <application>presto</application> metadata enabled. Delta RPMs contain only the differences between the version of the package installed on the client requesting the RPM package and the updated version in the repository. Downloading a delta RPM is much quicker than downloading the entire updated package, and can speed up updates considerably. Once the delta RPMs are downloaded, they must be rebuilt (the difference applied to the currently-installed package to create the full updated package) on the installing machine, which takes CPU time. Using delta RPMs is therefore a tradeoff between time-to-download, which depends on the network connection, and time-to-rebuild, which is CPU-bound. Using the <application>presto</application> plugin is recommended for fast machines an
 d systems with slower network connections, while slower machines on very fast connections <emphasis>may</emphasis> benefit more from downloading normal RPM packages, i.e. by disabling <application>presto</application>. The <application>presto</application> plugin is enabled by default.</para>
       <bridgehead
         id="bh-protect-packages_yum-plugin-protect-packages">protect-packages (yum-plugin-protect-packages)</bridgehead>
       <indexterm>
