[release-notes] networking.xml | Some typos, some xml tag improvements.

[stephenw]

commit f47c794cbbcfe97d8974f4ea81c3ab9553e72040
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Mon Oct 29 21:35:12 2012 +0100

    networking.xml | Some typos, some xml tag improvements.

 en-US/Networking.xml |   20 ++++++++++----------
 1 files changed, 10 insertions(+), 10 deletions(-)
---
diff --git a/en-US/Networking.xml b/en-US/Networking.xml
index 30b8da3..7c9f334 100644
--- a/en-US/Networking.xml
+++ b/en-US/Networking.xml
@@ -8,23 +8,23 @@
   <title>Networking</title>
   
      <section>
-          <title>Consistent network device naming </title>
-        <para>Fedora 18 continues previous releases' use of <package>biosdevname</package> to set network device names in a deterministic manner. Ethernet ports embedded on server motherboards will be named <literal>em<replaceable>port_number</replaceable></literal>, while ports on PCI cards will be named <literal>p<replaceable>slot_number</replaceable>p<replaceable>port_number</replaceable></literal>, corresponding to the chassis labels. This feature may be disabled by passing <literal>biosdevname=0</literal> on the kernel command line, in which case, behavior will revert to using ethX names. </para>
+          <title>Consistent network device naming</title>
+        <para>Fedora 18 continues the previous releases' use of <package>biosdevname</package> to set network device names in a deterministic manner. Ethernet ports embedded on server motherboards will be named <literal>em<replaceable>port_number</replaceable></literal>, while ports on PCI cards will be named <literal>p<replaceable>slot_number</replaceable>p<replaceable>port_number</replaceable></literal>, corresponding to the chassis labels. This feature may be disabled by passing <literal>biosdevname=0</literal> on the kernel command line, in which case, behavior will revert to using ethX names.</para>
       </section><section>
         
-          <title>better network security with <application>firewalld</application> </title>
+          <title>Better network security with <application>firewalld</application></title>
           <para>
-          <package>firewalld</package> will be the default firewall solution for Fedora 18, replacing <package>iptables</package>.  Using <application>firewalld</application> will allow for application of policy changes without reloading, allowing connection states to stay unbroken when rules are changed. </para>
-          <para>A <function>D-BUS</function> interface allows approved applications to communicate status and present complex or temporary needs to the firewall without requiring hand configuration by an administrator. This improves support for dynamic environments like <application>libvirtd</application>, which previously had to be restarted when <application>iptables</application> rules were changed.  </para>
-          <para>Manual administration can be done with <command>firewall-cmd</command>. Documentation on firewalld can be found in the included manpages: <literal>firewall-cmd(1)</literal>, <literal>firewalld(1)</literal>, <literal>firewalld.conf(5)</literal>, <literal>firewalld.icmptype(5)</literal>, <literal>firewalld.service(5)</literal>, <literal>firewalld.zone(5)</literal>. </para>
+          The firewall daemon <package>firewalld</package> will be the default firewall solution for Fedora 18, replacing <package>iptables</package>. Using <application>firewalld</application> will allow for application of policy changes without reloading, allowing connection states to stay unbroken when rules are changed.</para>
+          <para>A <function>D-BUS</function> interface allows approved applications to communicate thier status and present complex or temporary needs to the firewall without requiring hand configuration by an administrator. This improves support for dynamic environments such as <application>libvirtd</application>, which previously had to be restarted when <application>iptables</application> rules were changed.</para>
+          <para>Manual administration can be done with <command>firewall-cmd</command>. Documentation on firewalld can be found in the included manpages: <filename>firewall-cmd(1)</filename>, <filename>firewalld(1)</filename>, <filename>firewalld.conf(5)</filename>, <filename>firewalld.icmptype(5)</filename>, <filename>firewalld.service(5)</filename>, <filename>firewalld.zone(5)</filename>.</para>
       </section>
       <section>
-        <title><function>Team Driver</function> improves NIC bonding </title>
-        <para> Fedora 18 includes <function>Team Driver</function> which facilitates grouping of multiple network interfaces together so they act like a single network interface. This extends teaming possibilities provided by existing bonding driver. It also provides userspace driven, modular alternative to bonding driver. Usage information can be found in the include manpages: <literal>teamd.conf(5)</literal>, <literal>teamd(8)</literal>, and <literal>teamdctl(8)</literal>. </para>
+        <title><application>Team Driver</application> improves NIC bonding</title>
+        <para> Fedora 18 includes <function>Team Driver</function> which facilitates grouping of multiple network interfaces together so they act like a single network interface. This extends teaming possibilities provided by the existing bonding driver. It also provides a userspace driven, modular alternative to the existing bonding driver. Usage information can be found in the included manpages: <filename>teamd.conf(5)</filename>, <filename>teamd(8)</filename>, and <filename>teamdctl(8)</filename>.</para>
       </section>
       <section>
-        <title>Bring your own hotspot </title>
-        <para><package>NetworkManager</package>now supports an enhanced Hotspot/Internet Connection Sharing mode for <trademark>WiFi</trademark>, which enables a much smoother connection sharing experience and is better supported by hardware. This mode is automatically enabled only for newly created connection to ensure existing configuration is unchanged. </para>
+        <title>Bring your own Hotspot</title>
+        <para><package>NetworkManager</package> now supports an enhanced Hotspot or Internet Connection Sharing mode for <trademark>Wi-Fi</trademark>, which enables a much smoother connection sharing experience and is better supported by hardware. This mode is automatically enabled only for new connections to ensure existing configurations are unchanged.</para>
       </section>
 </section>