BIND 10 trac1376, updated. ddf219d781a40764999bd8b19c80f607c2783b57 [1376] Correct typos and change some phrasing of a message description

[BIND 10 source code commits]

The branch, trac1376 has been updated
       via  ddf219d781a40764999bd8b19c80f607c2783b57 (commit)
      from  170936d47b2e9ad3d5c3ceabf86026fca9795150 (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 ddf219d781a40764999bd8b19c80f607c2783b57
Author: Stephen Morris <stephen at isc.org>
Date:   Fri Nov 18 14:02:12 2011 +0000

    [1376] Correct typos and change some phrasing of a message description

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

Summary of changes:
 src/lib/python/isc/xfrin/libxfrin_messages.mes |   16 +++++++---------
 1 files changed, 7 insertions(+), 9 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/lib/python/isc/xfrin/libxfrin_messages.mes b/src/lib/python/isc/xfrin/libxfrin_messages.mes
index 0591f70..203e31f 100644
--- a/src/lib/python/isc/xfrin/libxfrin_messages.mes
+++ b/src/lib/python/isc/xfrin/libxfrin_messages.mes
@@ -21,13 +21,11 @@ same RRset. But the TTLs of these don't match each other. As we combine them
 together, the later one get's overwritten to the earlier one in the sequence.
 
 % LIBXFRIN_NO_JOURNAL disabled journaling for updates to %1 on %2
-A Diff object was attempted to be created with enabling journaing, but
-the underlying data source didn't support journaling (while still
-allowing updates).  So the resulting Diff object will continue handle
-updates by disabling journaing.  At a higher level this means that the
-updates will be applied to the zone but subsequent IXFR requests will
-result in a full zone transfer (i.e., an AXFR-style IXFR).  Unless the
+An attempt was made to create a Diff object with journaling enabled, but
+the underlying data source didn't support journaling (while still allowing
+updates) and so the created object has it disabled.  At a higher level this
+means that the updates will be applied to the zone but subsequent IXFR requests
+will result in a full zone transfer (i.e., an AXFR-style IXFR).  Unless the
 overhead of the full transfer is an issue this message can be ignored;
-otherwise you may want to check why the journaling wasn't allowed on
-the data source and either fix the issue or use a different type of
-data source.
+otherwise you may want to check why the journaling wasn't allowed on the
+data source and either fix the issue or use a different type of data source.