BIND 10 trac2776, updated. fdb6fd8e3a4e680d6739835bc48510d2d44eb866 [2776] Minor tweaks and fixes

[BIND 10 source code commits]

The branch, trac2776 has been updated
       via  fdb6fd8e3a4e680d6739835bc48510d2d44eb866 (commit)
      from  8094aaa11df22d79f338539b338e07bd8f950117 (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 fdb6fd8e3a4e680d6739835bc48510d2d44eb866
Author: Mukund Sivaraman <muks at isc.org>
Date:   Thu Jun 13 11:13:08 2013 +0200

    [2776] Minor tweaks and fixes

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

Summary of changes:
 .../resolver/02-mixed-recursive-authority-setup    |   12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

-----------------------------------------------------------------------
diff --git a/doc/design/resolver/02-mixed-recursive-authority-setup b/doc/design/resolver/02-mixed-recursive-authority-setup
index 33750a5..a1cc5f6 100644
--- a/doc/design/resolver/02-mixed-recursive-authority-setup
+++ b/doc/design/resolver/02-mixed-recursive-authority-setup
@@ -5,7 +5,7 @@ Ideally we will run the authoritative server independently of the
 recursive resolver.
 
 We need a way to run both an authoritative and a recursive resolver on
-a single platform, listening on the same IP/port. But we need a way to
+the same machine and listening on the same IP/port. But we need a way to
 run only one of them as well.
 
 This is mostly the same problem as we have with DDNS packets and xfr-out
@@ -22,7 +22,7 @@ With some build system or dynamic linker tricks, we create three modules:
  * Stand-alone resolver
  * Compound module containing both
 
-The user then chooses either one stand alone module, or the compound one,
+The user then chooses either one stand-alone module, or the compound one,
 depending on the requirements.
 
 Advantages
@@ -36,7 +36,7 @@ Disadvantages
 
  * The code is not separated (one bugs takes down both, admin can't see which
    one takes how much CPU).
- * Bind 9 does this and bind 9 code is a jungle. Maybe it's not just a
+ * BIND 9 does this and its code is a jungle. Maybe it's not just a
    coincidence.
  * Limits flexibility -- for example, we can't then decide to make the resolver
    threaded (or we would have to make sure the auth processing doesn't break
@@ -62,7 +62,7 @@ Advantages
 Disadvantages
 ~~~~~~~~~~~~~
 
- * Counter-intuitive asymetric design
+ * Counter-intuitive asymmetric design
  * Possible slowdown on the resolver side
  * Resolver needs to know both modes (for running stand-alone too)
 
@@ -81,7 +81,7 @@ forwarded to the resolver. The resolver then updates the cache too.
 Advantages
 ~~~~~~~~~~
 
- * Probably a good performance
+ * Probably good performance
 
 Disadvantages
 ~~~~~~~~~~~~~
@@ -135,7 +135,7 @@ Implementation ideas
  * The queries are sent from the receptionist in batches, the answers are sent
    back to the receptionist in batches too.
  * It is possible to fine-tune and use OS-specific tricks (like epoll or
-   sending multiple UDP messages by single call to sendmmsg).
+   sending multiple UDP messages by single call to sendmmsg()).
 
 Proposal
 --------