From fe89e46378a148099aea7a23f087029392cbbc87 Mon Sep 17 00:00:00 2001
From: "Jeremy C. Reed" <jreed@ISC.org>
Date: Wed, 15 Aug 2012 22:42:17 -0500
Subject: [PATCH] [master][bind10-20120816-release] get rid of trailing
 whitespace

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

diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml
index 46da1bc8ce..2860f0ee5f 100644
--- a/doc/guide/bind10-guide.xml
+++ b/doc/guide/bind10-guide.xml
@@ -1347,7 +1347,7 @@ TODO
       <para>
         This is encoded in form of JSON. Semi-formal description could look
         something like this. It is described in more details below.
-        <!-- FIXME: Is <screen> really the correct one?-->
+<!-- FIXME: Is <screen> really the correct one?-->
         <screen>ACL := [ RULE, RULE, ... ]
 RULE := { "action": "ACCEPT"|"REJECT"|"DROP", MATCH, MATCH, ... }
 RULE_RAW := { MATCH, MATCH, ... }
@@ -1376,8 +1376,8 @@ AND_MATCH := "ALL": [ RULE_RAW, RULE_RAW, ... ]
           The other is TSIG key by which the message was signed. The ACL
           contains only the name (under the name "key"), the key itself
           must be stored in the global keyring. This property is applicable only
-          to the DNS context. <!-- TODO: Section for the keyring and link to
-          it.-->
+          to the DNS context.
+<!-- TODO: Section for the keyring and link to it.-->
         </para>
 
         <para>
@@ -2162,7 +2162,7 @@ Xfrout/transfer_acl[0]	{"action": "ACCEPT"}	any	(default)</screen>
       TSIGs in the incoming messages and to sign responses.</para>
 
     <para>
-      For further details on ACL configuration, see 
+      For further details on ACL configuration, see
       <xref linkend="common-acl" />.
     </para>