BIND 10 master, updated. 8cad081427cd8326318ef1a0dc81c1eefaf73d29 [master] fix twpo misspelling typos

[BIND 10 source code commits]

The branch, master has been updated
       via  8cad081427cd8326318ef1a0dc81c1eefaf73d29 (commit)
      from  a948a71497441782d409e98f4068bd04cadf581a (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 8cad081427cd8326318ef1a0dc81c1eefaf73d29
Author: Jeremy C. Reed <jreed at ISC.org>
Date:   Thu Jun 16 13:28:22 2011 -0500

    [master] fix twpo misspelling typos

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

Summary of changes:
 src/bin/resolver/resolverdef.mes |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/bin/resolver/resolverdef.mes b/src/bin/resolver/resolverdef.mes
index bb89cfa..47433a4 100644
--- a/src/bin/resolver/resolverdef.mes
+++ b/src/bin/resolver/resolverdef.mes
@@ -118,7 +118,7 @@ of the body of the message failed due to some non-protocol related reason
 (although the parsing of the header succeeded).  The message parameters give
 a textual description of the problem and the RCODE returned.
 
-% PRINTMSG      print message command, aeguments are: %1
+% PRINTMSG      print message command, arguments are: %1
 This message is logged when a "print_message" command is received over the
 command channel.
 
@@ -169,7 +169,7 @@ resolver gives up trying to resolve a query.  Retry count: the number of times
 the resolver will retry a query to an upstream server if it gets a timeout.
 
 The client and lookup timeouts require a bit more explanation. The
-resolution of the clent query might require a large number of queries to
+resolution of the client query might require a large number of queries to
 upstream nameservers.  Even if none of these queries timeout, the total time
 taken to perform all the queries may exceed the client timeout.  When this
 happens, a SERVFAIL is returned to the client, but the resolver continues