BIND 10 trac2252, updated. d36c276d69d8897175964b8a2002405c53630663 [2252] wording cleanups, and omission of the repeated same notes

[BIND 10 source code commits]

The branch, trac2252 has been updated
       via  d36c276d69d8897175964b8a2002405c53630663 (commit)
      from  0475216923e0c60294c0901ae3e6af09f5e961ae (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 d36c276d69d8897175964b8a2002405c53630663
Author: Naoki Kambe <kambe at jprs.co.jp>
Date:   Tue May 7 09:47:56 2013 +0900

    [2252] wording cleanups, and omission of the repeated same notes
    
    (The original patch is proposed by Jinmei-san.)

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

Summary of changes:
 .../lettuce/features/xfrin_notify_handling.feature |   28 ++++----------------
 1 file changed, 5 insertions(+), 23 deletions(-)

-----------------------------------------------------------------------
diff --git a/tests/lettuce/features/xfrin_notify_handling.feature b/tests/lettuce/features/xfrin_notify_handling.feature
index dab0688..375a8a9 100644
--- a/tests/lettuce/features/xfrin_notify_handling.feature
+++ b/tests/lettuce/features/xfrin_notify_handling.feature
@@ -31,11 +31,11 @@ Feature: Xfrin incoming notify handling
       | item_name                | item_max | item_min |
       | socket.unixdomain.open   |        1 |        0 |
     # Note: .Xfrout.socket.unixdomain.open can be either expected to
-    # be 0 or 1 here.  The reason is: if b10-xfrout starts all and is
+    # be 0 or 1 here.  The reason is: if b10-xfrout has started up and is
     # ready for a request from b10-stats, then b10-stats does request
     # to b10-xfrout and the value results in 1. Otherwise if
     # b10-xfrout is starting and isn't yet ready, then b10-stats
-    # doesn't request to b10-xfrout and the value still remains to the
+    # doesn't request to b10-xfrout and the value still remains to be the
     # default value(0).
 
     #
@@ -138,13 +138,7 @@ Feature: Xfrin incoming notify handling
     check initial statistics not containing example.org for Xfrout with cmdctl port 47804 except for the following items
       | item_name                | item_max | item_min |
       | socket.unixdomain.open   |        1 |        0 |
-    # Note: .Xfrout.socket.unixdomain.open can be either expected to
-    # be 0 or 1 here.  The reason is: if b10-xfrout starts all and is
-    # ready for a request from b10-stats, then b10-stats does request
-    # to b10-xfrout and the value results in 1. Otherwise if
-    # b10-xfrout is starting and isn't yet ready, then b10-stats
-    # doesn't request to b10-xfrout and the value still remains to the
-    # default value(0).
+    # Note: See above about .Xfrout.socket.unixdomain.open.
 
     #
     # Test2 for Xfrin statistics
@@ -246,13 +240,7 @@ Feature: Xfrin incoming notify handling
     check initial statistics not containing example.org for Xfrout with cmdctl port 47804 except for the following items
       | item_name                | item_max | item_min |
       | socket.unixdomain.open   |        1 |        0 |
-    # Note: .Xfrout.socket.unixdomain.open can be either expected to
-    # be 0 or 1 here.  The reason is: if b10-xfrout starts all and is
-    # ready for a request from b10-stats, then b10-stats does request
-    # to b10-xfrout and the value results in 1. Otherwise if
-    # b10-xfrout is starting and isn't yet ready, then b10-stats
-    # doesn't request to b10-xfrout and the value still remains to the
-    # default value(0).
+    # Note: See above about .Xfrout.socket.unixdomain.open.
 
     #
     # Test2 for Xfrin statistics
@@ -358,13 +346,7 @@ Feature: Xfrin incoming notify handling
     check initial statistics not containing example.org for Xfrout with cmdctl port 47804 except for the following items
       | item_name                | item_max | item_min |
       | socket.unixdomain.open   |        1 |        0 |
-    # Note: .Xfrout.socket.unixdomain.open can be either expected to
-    # be 0 or 1 here.  The reason is: if b10-xfrout starts all and is
-    # ready for a request from b10-stats, then b10-stats does request
-    # to b10-xfrout and the value results in 1. Otherwise if
-    # b10-xfrout is starting and isn't yet ready, then b10-stats
-    # doesn't request to b10-xfrout and the value still remains to the
-    # default value(0).
+    # Note: See above about .Xfrout.socket.unixdomain.open.
 
     #
     # Test2 for Xfrin statistics