From a5c9a0e9e86ef3ff1ce2ae8fc63640e7a94c63fa Mon Sep 17 00:00:00 2001
From: JINMEI Tatuya <jinmei@isc.org>
Date: Tue, 14 Aug 2012 12:31:06 -0700
Subject: [PATCH] [2066] revised text about xfrout acl config per my own
 suggestion

---
 doc/guide/bind10-guide.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index 00f7e3aa46..32592d16c8 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -2115,11 +2115,6 @@ http://bind10.isc.org/wiki/ScalableZoneLoadDesign#a7.2UpdatingaZone
       <screen>&gt; <userinput>config show Xfrout/transfer_acl</userinput>
 Xfrout/transfer_acl[0]	{"action": "ACCEPT"}	any	(default)</screen>
 
-    <para>
-      You can configure it in the same way as any ACL
-      (<xref linkend="common-acl" />).
-    </para>
-
     <para>
       If you want to require TSIG in access control, a system wide TSIG
       "key ring" must be configured.
@@ -2135,6 +2130,11 @@ Xfrout/transfer_acl[0]	{"action": "ACCEPT"}	any	(default)</screen>
       will use the system wide keyring to check
       TSIGs in the incoming messages and to sign responses.</para>
 
+    <para>
+      For further details on ACL configuration, see 
+      <xref linkend="common-acl" />.
+    </para>
+
     <note><simpara>
         The way to specify zone specific configuration (ACLs, etc) is
         likely to be changed.