BIND 10 trac3221, updated. 412fdad4d0da738faa07d5e3016c4a5ae0bdaa5a [3221] Corrected typo and spelling in new log message

[BIND 10 source code commits]

The branch, trac3221 has been updated
       via  412fdad4d0da738faa07d5e3016c4a5ae0bdaa5a (commit)
      from  2ca54a3ed0a89b2b90a10e2cc80bed218ae8607c (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 412fdad4d0da738faa07d5e3016c4a5ae0bdaa5a
Author: Thomas Markwalder <tmark at isc.org>
Date:   Mon Feb 10 12:57:27 2014 -0500

    [3221] Corrected typo and spelling in new log message
    
    Also ran dhcp_ddns_messages.mes through reorder tool.

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

Summary of changes:
 src/lib/dhcp_ddns/dhcp_ddns_messages.mes |   20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/lib/dhcp_ddns/dhcp_ddns_messages.mes b/src/lib/dhcp_ddns/dhcp_ddns_messages.mes
index fa28354..554139f 100644
--- a/src/lib/dhcp_ddns/dhcp_ddns_messages.mes
+++ b/src/lib/dhcp_ddns/dhcp_ddns_messages.mes
@@ -45,6 +45,12 @@ start another send after completing the send of the previous request.  While
 possible, this is highly unlikely and is probably a programmatic error.  The
 application should recover on its own.
 
+% DHCP_DDNS_NCR_UDP_CLEAR_READY_ERROR NCR UDP watch socket failed to clear: %1
+This is an error message that indicates the application was unable to reset the
+UDP NCR sender ready status after completing a send.  This is programmatic error
+that should be reported.  The application may or may not continue to operate
+correctly.
+
 % DHCP_DDNS_NCR_UDP_RECV_CANCELED UDP socket receive was canceled while listening for DNS Update requests: %1
 This is an informational  message indicating that the listening over a UDP socket for DNS update requests has been canceled.  This is a normal part of suspending listening operations.
 
@@ -75,20 +81,14 @@ caught in the application's send completion handler.  This is a programmatic
 error that needs to be reported.  Dependent upon the nature of the error the
 client may or may not continue operating normally.
 
-% DHCP_DDNS_WATCH_SOURCE_CLOSE_ERROR Source-side watch socket failed to close: %1
+% DHCP_DDNS_WATCH_SINK_CLOSE_ERROR Sink-side watch socket failed to close: %1
 This is an error message that indicates the application was unable to close
-the outbound side of a NCR sender's watch socket.  While technically possible
+the inbound side of a NCR sender's watch socket.  While technically possible
 this error is highly unlikely to occur and should not impair the application's
 ability to process requests.
 
-% DHCP_DDNS_WATCH_SINK_CLOSE_ERROR Sink-side watch socket failed to close: %1
+% DHCP_DDNS_WATCH_SOURCE_CLOSE_ERROR Source-side watch socket failed to close: %1
 This is an error message that indicates the application was unable to close
-the inbound side of a NCR sender's watch socket.  While technically possible
+the outbound side of a NCR sender's watch socket.  While technically possible
 this error is highly unlikely to occur and should not impair the application's
 ability to process requests.
-
-% DHCP_DDNS_NCR_UDP_CLEAR_READY_ERROR NCR UPD watch socket failed to clear: %1
-This is an error message that indicates the application was unable to reset the
-UDP NCR sender ready status after completing a send.  This is programmatic error
-that should be reported.  The application may or may not continue to operator
-correctly.