[networking-guide] master: remove doublespace (f054da2)

[stephenw]

Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git

On branch  : master
>

commit f054da2b2245177fa3c8d6c662dbf1310b94ab6b
Author: Stephen Wadeley 
Date:   Wed Sep 3 22:23:42 2014 +0200

remove doublespace
>

en-US/Configure_Network_Bonding.xml |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/en-US/Configure_Network_Bonding.xml b/en-US/Configure_Network_Bonding.xml
index 17a16d8..85a064c 100644
--- a/en-US/Configure_Network_Bonding.xml
+++ b/en-US/Configure_Network_Bonding.xml
@@ -427,7 +427,7 @@ Then when complete, bring up all the slaves, which will bring up the bond (provi
      <screen>~]# <command>nmcli con load /etc/sysconfig/network-scripts/ifcfg-<replaceable>device</replaceable></command></screen>
      Alternatively, to reload all interfaces:
 <screen>~]# <command>nmcli con reload</command></screen>
-     The default behavior is for <application>NetworkManager</application> not to be aware of the changes and	 to continue using the old configuration data. The is set by the <option>monitor-connection-files</option> option in the <filename>NetworkManager.conf</filename> file. See the <filename>NetworkManager.conf(5)</filename> manual page for more information.
+     The default behavior is for <application>NetworkManager</application> not to be aware of the changes and to continue using the old configuration data. The is set by the <option>monitor-connection-files</option> option in the <filename>NetworkManager.conf</filename> file. See the <filename>NetworkManager.conf(5)</filename> manual page for more information.
    </para>

<para>
@@ -962,7 +962,7 @@ This policy is useful for devices that cannot ever alter their MAC address, or f
   ( <replaceable>&lt;source_MAC&gt;</replaceable> XOR <replaceable>&lt;destination_MAC&gt;</replaceable> ))
     MODULO <replaceable>&lt;slave_count&gt;</replaceable>
                   </screen>
-                  <para>This algorithm will place all traffic to a particular network peer on the same slave.  For non-<systemitem class="protocol">IP</systemitem> traffic, the formula is the same as for the layer2 transmit hash policy.</para>
+                  <para>This algorithm will place all traffic to a particular network peer on the same slave. For non-<systemitem class="protocol">IP</systemitem> traffic, the formula is the same as for the layer2 transmit hash policy.</para>
                   <para>This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations.</para>
                   <para>This algorithm is 802.3ad compliant.</para>
                 </listitem>