BIND 10 trac1341, updated. 35b1914ce6ab5481ce40f584729d0949746c2219 [trac1341] spelling typo

[BIND 10 source code commits]

The branch, trac1341 has been updated
       via  35b1914ce6ab5481ce40f584729d0949746c2219 (commit)
       via  1c9f121360e6e612d02d365d70bd0843f8f93457 (commit)
       via  d142274062ed21d53f9e0b2a85531c935580013c (commit)
       via  5de9e8a440b6b4ed8c6bbce156d75b740ec4c1b5 (commit)
      from  cd4fd339a084dbfb1e2d35d5c008260de9d48572 (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 35b1914ce6ab5481ce40f584729d0949746c2219
Author: Jeremy C. Reed <jreed at ISC.org>
Date:   Fri Nov 18 11:33:45 2011 -0600

    [trac1341] spelling typo

commit 1c9f121360e6e612d02d365d70bd0843f8f93457
Author: Jeremy C. Reed <jreed at ISC.org>
Date:   Fri Nov 18 10:54:49 2011 -0600

    [trac1341] spelling typo

commit d142274062ed21d53f9e0b2a85531c935580013c
Author: Jeremy C. Reed <jreed at ISC.org>
Date:   Fri Nov 18 10:40:44 2011 -0600

    [trac1341] spelling

commit 5de9e8a440b6b4ed8c6bbce156d75b740ec4c1b5
Author: Jeremy C. Reed <jreed at ISC.org>
Date:   Fri Nov 18 10:36:57 2011 -0600

    [trac1341] add paragraph break and mention default at start of long sentence
    
    instead of at end

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

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

-----------------------------------------------------------------------
diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index 26fc86a..199f297 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -727,14 +727,17 @@ Debian and Ubuntu:
       but more importantly to ask about their own settings, and
       about other modules. The <command>b10-sockcreator</command> will
       allocate sockets for the rest of the system.
-      The <command>bind10</command> master process will also start up
+    </para>
+
+    <para>
+      In its default configuration, the <command>bind10</command>
+      master process will also start up
       <command>b10-cmdctl</command> for admins to communicate with the
       system, <command>b10-auth</command> for authoritative DNS service,
       <command>b10-stats</command> for statistics collection,
       <command>b10-xfrin</command> for inbound DNS zone transfers,
       <command>b10-xfrout</command> for outbound DNS zone transfers,
-      and <command>b10-zonemgr</command> for secondary service in the
-      default configuration.
+      and <command>b10-zonemgr</command> for secondary service.
     </para>
 
     <section id="start">
@@ -770,7 +773,7 @@ Debian and Ubuntu:
         (currently there's also one component which doesn't represent
         a process). If you didn't want to transfer out at all (your server
         is a slave only), you would just remove the corresponding component
-        from the set, like this and the process would be stopped imediatelly
+        from the set, like this and the process would be stopped immediately
         (and not started on the next startup):
       <screen>> <userinput>config del Boss/components b10-xfrout</userinput>
 > <userinput>config commit</userinput></screen>
@@ -819,9 +822,9 @@ Debian and Ubuntu:
         If it is set to "dispensable" (the default unless you set something
         else), it will get started again if it fails. If it is set to
         "needed" and it fails at startup, the whole bind10 shuts down and exits
-        with error exit code. But if it failes some time later, it is just
+        with error exit code. But if it fails some time later, it is just
         started again. If you set it to "core", you indicate that the system
-        is not useable without the component and if such component fails, the
+        is not usable without the component and if such component fails, the
         system shuts down no matter when the failure happened. This is the
         behaviour of the core components (the ones you can't turn off), but
         you can declare any other components as core as well if you wish
@@ -837,7 +840,7 @@ Debian and Ubuntu:
       <para>
         There are other parameters we didn't use in our example.
         One of them is "address". It is the address used by the component
-        on the b10-msgq message buss. The special components already know
+        on the b10-msgq message bus. The special components already know
         their address, but the usual ones don't. The address is by convention
         the thing after b10-, with the first letter capital (eg. b10-stats
         would have Stats as its address).
@@ -881,7 +884,7 @@ Debian and Ubuntu:
         to start the <command>b10-auth</command> or <command>b10-resolver</command>
         as root (until the socket creator is finished). So we need to specify
         the time when the switch from root do the given user happens and that's
-        whath the setuid component is for. The switch is done at the time the
+        what the setuid component is for. The switch is done at the time the
         setuid component would be started, if it was a process. The default
         configuration contains the setuid component with priority 5, b10-auth
         has 10 to be started before the switch and everything else is without