BIND 10 trac1911, updated. 8f1b5c8b84d5931780efb944902e15ade928c8c3 [1911] Clarify text about incoming zone transfers

[BIND 10 source code commits]

The branch, trac1911 has been updated
       via  8f1b5c8b84d5931780efb944902e15ade928c8c3 (commit)
      from  443984932800121af1562154aa93af410be90599 (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 8f1b5c8b84d5931780efb944902e15ade928c8c3
Author: Mukund Sivaraman <muks at isc.org>
Date:   Mon May 14 08:28:34 2012 +0530

    [1911] Clarify text about incoming zone transfers

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

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

-----------------------------------------------------------------------
diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index f7ff35c..5751797 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -1790,12 +1790,12 @@ what if a NOTIFY is sent?
       <title>Incoming Transfers with In-memory Datasource</title>
 
       <para>
-        In the case of an incoming zone which is served by an in-memory
-        datasource with an SQLite3 backend, the zone is first stored in
-        the corresponding backend file. Then,
-        <command>b10-auth</command> is automatically sent a
-        <varname>loadzone</varname> command to reload the corresponding
-        zone into memory from the backend file.
+        In the case of an incoming zone transfer, the received zone is
+        first stored in the corresponding BIND 10 data source file. In
+        case the secondary zone is served by an in-memory datasource
+        with an SQLite3 backend, <command>b10-auth</command> is
+        automatically sent a <varname>loadzone</varname> command to
+        reload the corresponding zone into memory from the backend file.
       </para>
     </section>