[system-administrators-reference-guide/draft] I forgot trailing ulink

[stephenw]

commit 89e5f521e5a9becfa2488b34f05cc26932f8ad5d
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Mon Mar 17 17:57:24 2014 +0100

    I forgot trailing ulink

 en-US/Network_Interfaces.xml |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
---
diff --git a/en-US/Network_Interfaces.xml b/en-US/Network_Interfaces.xml
index c44a84c..60724d8 100644
--- a/en-US/Network_Interfaces.xml
+++ b/en-US/Network_Interfaces.xml
@@ -108,7 +108,7 @@
     <important>
       <title>Network interface names</title>
       <para>
-        Network interface names may be different on different hardware types. See the <citetitle pubwork="book">Fedora Networking Guide</citetitle></ulink> for more information on device naming.
+        Network interface names may be different on different hardware types. See the <citetitle pubwork="book">Fedora Networking Guide</citetitle> for more information on device naming.
       </para>
     </important>
 
@@ -358,7 +358,7 @@ ONBOOT=yes</programlisting>
           <listitem>
             <para>
               where <replaceable>MAC-address</replaceable> is the hardware address of the Ethernet device in the form <replaceable>AA:BB:CC:DD:EE:FF</replaceable>. This directive must be used in machines containing more than one NIC to ensure that the interfaces are assigned the correct device names regardless of the configured load order for each NIC's module. This directive should <emphasis
-                role="strong">not</emphasis> be used in conjunction with <option>MACADDR</option>. See the <citetitle pubwork="book">Fedora Networking Guide</citetitle></ulink> for more information on device naming.
+                role="strong">not</emphasis> be used in conjunction with <option>MACADDR</option>. See the <citetitle pubwork="book">Fedora Networking Guide</citetitle> for more information on device naming.
               </para>
               </listitem>
         </varlistentry>
@@ -785,7 +785,7 @@ ONBOOT=yes</programlisting>
           </para>
         </note>
         <para>
-        For new installations, users should select the <guilabel>Manual</guilabel> method on the <systemitem class="protocol">IPv4</systemitem> or <systemitem class="protocol">IPv6</systemitem> tab in <application>NetworkManager</application> to assign multiple <systemitem class="protocol">IP</systemitem> address to the same interface. For more information on using this tool, see the <citetitle pubwork="book">Fedora Networking Guide</citetitle></ulink>.
+        For new installations, users should select the <guilabel>Manual</guilabel> method on the <systemitem class="protocol">IPv4</systemitem> or <systemitem class="protocol">IPv6</systemitem> tab in <application>NetworkManager</application> to assign multiple <systemitem class="protocol">IP</systemitem> address to the same interface. For more information on using this tool, see the <citetitle pubwork="book">Fedora Networking Guide</citetitle>.
       </para>
       <para>
         Alias interface configuration files, which are used to bind multiple addresses to a single interface, use the <filename>ifcfg-<replaceable>if-name</replaceable>:<replaceable>alias-value</replaceable></filename> naming scheme.
@@ -812,7 +812,7 @@ BOOTPROTO=dhcp</programlisting>
         This way a user can bring up the <systemitem class="etheraddress">eth0</systemitem> interface using the <command>/sbin/ifup eth0-user</command> command because the configuration options from <filename>ifcfg-eth0</filename> and <filename>ifcfg-eth0-user</filename> are combined. While this is a very basic example, this method can be used with a variety of options and interfaces.
       </para>
       <para>
-      It is no longer possible to create alias and clone interface configuration files using a graphical tool. However, as explained at the beginning of this section, it is no longer necessary to use this method as it is now possible to directly assign multiple <systemitem class="protocol">IP</systemitem> address to the same interface. For new installations, users should select the <guilabel>Manual</guilabel> method on the <systemitem class="protocol">IPv4</systemitem> or <systemitem class="protocol">IPv6</systemitem> tab in <application>NetworkManager</application> to assign multiple <systemitem class="protocol">IP</systemitem> address to the same interface. For more information on using this tool, see the <citetitle pubwork="book">Fedora Networking Guide</citetitle></ulink>.
+      It is no longer possible to create alias and clone interface configuration files using a graphical tool. However, as explained at the beginning of this section, it is no longer necessary to use this method as it is now possible to directly assign multiple <systemitem class="protocol">IP</systemitem> address to the same interface. For new installations, users should select the <guilabel>Manual</guilabel> method on the <systemitem class="protocol">IPv4</systemitem> or <systemitem class="protocol">IPv6</systemitem> tab in <application>NetworkManager</application> to assign multiple <systemitem class="protocol">IP</systemitem> address to the same interface. For more information on using this tool, see the <citetitle pubwork="book">Fedora Networking Guide</citetitle>.
       </para>
     </section>