cleanup trailing white space in SGML like files

bin/rndc/rndc.conf.docbook

@@ -60,7 +60,7 @@
   </refsynopsisdiv>
 
   <refsection><info><title>DESCRIPTION</title></info>
-    
+
     <para><filename>rndc.conf</filename> is the configuration file
       for <command>rndc</command>, the BIND 9 name server control
       utility.  This file has a similar structure and syntax to
@@ -147,7 +147,7 @@
   </refsection>
 
   <refsection><info><title>EXAMPLE</title></info>
-    
+
 
     <para><programlisting>
       options {
@@ -219,7 +219,7 @@
   </refsection>
 
   <refsection><info><title>NAME SERVER CONFIGURATION</title></info>
-    
+
     <para>
       The name server must be configured to accept rndc connections and
       to recognize the key specified in the <filename>rndc.conf</filename>
@@ -230,7 +230,7 @@
   </refsection>
 
   <refsection><info><title>SEE ALSO</title></info>
-    
+
     <para><citerefentry>
         <refentrytitle>rndc</refentrytitle><manvolnum>8</manvolnum>
       </citerefentry>,

bin/rndc/rndc.docbook

@@ -69,7 +69,7 @@
   </refsynopsisdiv>
 
   <refsection><info><title>DESCRIPTION</title></info>
-    
+
     <para><command>rndc</command>
       controls the operation of a name
       server.  It supersedes the <command>ndc</command> utility
@@ -101,7 +101,7 @@
   </refsection>
 
   <refsection><info><title>OPTIONS</title></info>
-    
+
 
     <variablelist>
       <varlistentry>
@@ -214,7 +214,7 @@
   </refsection>
 
   <refsection><info><title>COMMANDS</title></info>
-    
+
     <para>
       A list of commands supported by <command>rndc</command> can
       be seen by running <command>rndc</command> without arguments.
@@ -273,7 +273,7 @@
 	    Delete a zone while the server is running.
 	    Only zones that were originally added via
 	    <command>rndc addzone</command> can be deleted
-	    in this manner. 
+	    in this manner.
 	  </para>
 	  <para>
 	    If the <option>-clean</option> is specified,
@@ -545,7 +545,7 @@
 	<listitem>
 	  <para>
 	    Fetch all DNSSEC keys for the given zone
-	    from the key directory (see the 
+	    from the key directory (see the
 	    <command>key-directory</command> option in
 	    the BIND 9 Administrator Reference Manual).  If they are within
 	    their publication period, merge them into the
@@ -578,7 +578,7 @@
 	    operations (such as signing or generating
 	    NSEC3 chains) is stored in the zone in the form
 	    of DNS resource records of type
-	    <command>sig-signing-type</command>. 
+	    <command>sig-signing-type</command>.
 	    <command>rndc signing -list</command> converts
 	    these records into a human-readable form,
 	    indicating which keys are currently signing
@@ -604,7 +604,7 @@
 	    flags, iterations, and salt, in that order.
 	  </para>
 	  <para>
-	    Currently, the only defined value for hash algorithm 
+	    Currently, the only defined value for hash algorithm
 	    is <literal>1</literal>, representing SHA-1.
 	    The <option>flags</option> may be set to
 	    <literal>0</literal> or <literal>1</literal>,
@@ -787,7 +787,7 @@
   </refsection>
 
   <refsection><info><title>LIMITATIONS</title></info>
-    
+
     <para>
       There is currently no way to provide the shared secret for a
       <option>key_id</option> without using the configuration file.
@@ -798,7 +798,7 @@
   </refsection>
 
   <refsection><info><title>SEE ALSO</title></info>
-    
+
     <para><citerefentry>
 	<refentrytitle>rndc.conf</refentrytitle><manvolnum>5</manvolnum>
       </citerefentry>,