BIND 10 trac2862, updated. 478d2eda7aca5a6e7f4a0e017192854f100641b5 [2862] Update message descriptions to make them more readable, add punctuation, etc.

[BIND 10 source code commits]

The branch, trac2862 has been updated
       via  478d2eda7aca5a6e7f4a0e017192854f100641b5 (commit)
      from  d8183b83d92016696106a6665fde369fa7d49779 (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 478d2eda7aca5a6e7f4a0e017192854f100641b5
Author: Mukund Sivaraman <muks at isc.org>
Date:   Fri Jul 26 16:42:45 2013 +0530

    [2862] Update message descriptions to make them more readable, add punctuation, etc.

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

Summary of changes:
 src/bin/auth/auth_messages.mes |   28 +++++++++++++++-------------
 1 file changed, 15 insertions(+), 13 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/bin/auth/auth_messages.mes b/src/bin/auth/auth_messages.mes
index b21fb50..e5b655a 100644
--- a/src/bin/auth/auth_messages.mes
+++ b/src/bin/auth/auth_messages.mes
@@ -146,26 +146,28 @@ The thread for maintaining data source clients has finished reconfiguring
 the data source clients, and is now running with the new configuration.
 
 % AUTH_DATASRC_CLIENTS_BUILDER_SEGMENT_BAD_CLASS invalid RRclass %1 at segment update
-A memory segment update message was sent to the authoritative server. But the
-class contained there is no valid class. This means the system is in
-inconsistent state and the authoritative server aborts to minimise the problem
-This is likely a bug in the code.
+A memory segment update message was sent to the authoritative
+server. But the class contained there is invalid. This means that the
+system is in an inconsistent state and the authoritative server aborts
+to minimize the problem. This is likely caused by a bug in the code.
 
 % AUTH_DATASRC_CLIENTS_BUILDER_SEGMENT_ERROR error updating the memory segment: %1
-The authoritative server tried to update the memory segment. But the update
+The authoritative server tried to update the memory segment, but the update
 failed. The authoritative server aborts to avoid system inconsistency. This is
-likely a bug in the code.
+likely caused by a bug in the code.
 
 % AUTH_DATASRC_CLIENTS_BUILDER_SEGMENT_NO_DATASRC there's no data source named %2 in class %1
-The authoritative server was asked to update the memory segment of the given
-data source. The authoritative server aborts as this means the system is in
-inconsistent state. This is likely a bug in the code.
+The authoritative server was asked to update the memory segment of the
+given data source, but no data source by that name was found. The
+authoritative server aborts because this indicates that the system is in
+an inconsistent state. This is likely caused by a bug in the code.
 
 % AUTH_DATASRC_CLIENTS_BUILDER_SEGMENT_UNKNOWN_CLASS unknown class %1 at segment update
-A memory segment update message was sent to the authoritative server. The class
-name for which the update should happen is valid, but no client lists are
-configured for that class. The system is in inconsistent state and the
-authoritative server aborts. This may be caused by a bug in the code.
+A memory segment update message was sent to the authoritative
+server. The class name for which the update should happen is valid, but
+no client lists are configured for that class. The system is in an
+inconsistent state and the authoritative server aborts. This may be
+caused by a bug in the code.
 
 % AUTH_DATASRC_CLIENTS_BUILDER_STARTED data source builder thread started
 A separate thread for maintaining data source clients has been started.