BIND 10 trac1077, updated. 27c6b8cef44f5daaa149ec72e3b7052e516ebc26 [trac1077] add space between "BIND 10"

[BIND 10 source code commits]

The branch, trac1077 has been updated
       via  27c6b8cef44f5daaa149ec72e3b7052e516ebc26 (commit)
      from  846493567722add45db6e7296d570f8ecf99837e (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 27c6b8cef44f5daaa149ec72e3b7052e516ebc26
Author: Jeremy C. Reed <jreed at ISC.org>
Date:   Wed Jul 6 08:50:32 2011 -0500

    [trac1077] add space between "BIND 10"
    
    Where is the style guide for .mes messages files?

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

Summary of changes:
 src/lib/log/log_messages.mes |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/lib/log/log_messages.mes b/src/lib/log/log_messages.mes
index b88d563..6c05315 100644
--- a/src/lib/log/log_messages.mes
+++ b/src/lib/log/log_messages.mes
@@ -36,8 +36,8 @@ Logging has been configured so that output is written to the terminal
 Allowed values are "stdout" and "stderr".
 
 % LOG_DUPLICATE_MESSAGE_ID duplicate message ID (%1) in compiled code
-During start-up, BIND10 detected that the given message identification
-had been defined multiple times in the BIND10 code.  This indicates a
+During start-up, BIND 10 detected that the given message identification
+had been defined multiple times in the BIND 10 code.  This indicates a
 programming error; please log a bug report.
 
 % LOG_DUPLICATE_NAMESPACE line %1: duplicate $NAMESPACE directive found
@@ -99,10 +99,10 @@ There may be several reasons why this message may appear:
 - The program outputting the message may not use that particular message
 (e.g. it originates in a module not used by the program.)
 
-- The local file was written for an earlier version of the BIND10 software
+- The local file was written for an earlier version of the BIND 10 software
 and the later version no longer generates that message.
 
-Whatever the reason, there is no impact on the operation of BIND10.
+Whatever the reason, there is no impact on the operation of BIND 10.
 
 % LOG_OPEN_OUTPUT_FAIL unable to open %1 for output: %2
 Originating within the logging code, the program was not able to open
@@ -115,7 +115,7 @@ This error is generated when the compiler finds a $PREFIX directive with
 more than one argument.
 
 Note: the $PREFIX directive is deprecated and will be removed in a future
-version of BIND10.
+version of BIND 10.
 
 % LOG_PREFIX_INVALID_ARG line %1: $PREFIX directive has an invalid argument ('%2')
 Within a message file, the $PREFIX directive takes a single argument,
@@ -126,10 +126,10 @@ with a digit).  A $PREFIX directive was found with an argument (given
 in the message) that violates those restrictions.
 
 Note: the $PREFIX directive is deprecated and will be removed in a future
-version of BIND10.
+version of BIND 10.
 
 % LOG_READING_LOCAL_FILE reading local message file %1
-This is an informational message output by BIND10 when it starts to read
+This is an informational message output by BIND 10 when it starts to read
 a local message file.  (A local message file may replace the text of
 one of more messages; the ID of the message will not be changed though.)