BIND 10 jreed-docs-2, updated. 810c79d6d9b8efbc12ec8e1ad727cf002f2dedc6 [jreed-docs-2] reformat some long lines (no content change)

[BIND 10 source code commits]

The branch, jreed-docs-2 has been updated
       via  810c79d6d9b8efbc12ec8e1ad727cf002f2dedc6 (commit)
       via  c74d3b7f393f3934bae22fc9d3a4a49e2211aadb (commit)
      from  f14bc0502c3c4d2ffd609b110771ca1fa752b68e (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 810c79d6d9b8efbc12ec8e1ad727cf002f2dedc6
Author: Jeremy C. Reed <jreed at ISC.org>
Date:   Tue Aug 16 07:35:13 2011 -0500

    [jreed-docs-2] reformat some long lines (no content change)

commit c74d3b7f393f3934bae22fc9d3a4a49e2211aadb
Author: Jeremy C. Reed <jreed at ISC.org>
Date:   Tue Aug 16 07:33:45 2011 -0500

    [jreed-docs-2] fix typo

-----------------------------------------------------------------------

Summary of changes:
 doc/guide/bind10-guide.xml |   19 ++++++++++---------
 1 files changed, 10 insertions(+), 9 deletions(-)

-----------------------------------------------------------------------
diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index 59914cf..87c6ac1 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -547,7 +547,7 @@ Debian and Ubuntu:
           <varlistentry>
             <term>--prefix</term>
             <listitem>
-              <simpara>Define the the installation location (the
+              <simpara>Define the installation location (the
                 default is <filename>/usr/local/</filename>).
               </simpara>
             </listitem>
@@ -1599,14 +1599,15 @@ then change those defaults with config set Resolver/forward_addresses[0]/address
         <varlistentry>
         <term>error 111 opening TCP socket to 127.0.0.1(53)</term>
         <listitem><para>
-            A brief description of the cause of the problem.  Within this text,
-            information relating to the condition that caused the message to
-            be logged will be included.  In this example, error number 111
-            (an operating system-specific error number) was encountered when
-            trying to open a TCP connection to port 53 on the local system
-            (address 127.0.0.1).  The next step would be to find out the reason
-            for the failure by consulting your system's documentation to
-            identify what error number 111 means.
+	   A brief description of the cause of the problem.
+	   Within this text, information relating to the condition
+	   that caused the message to be logged will be included.
+	   In this example, error number 111 (an operating
+	   system-specific error number) was encountered when trying
+	   to open a TCP connection to port 53 on the local system
+	   (address 127.0.0.1).  The next step would be to find
+	   out the reason for the failure by consulting your system's
+	   documentation to identify what error number 111 means.
         </para></listitem>
         </varlistentry>
         </variablelist>