[networking-guide] master: Minor corrections after review (7357868)

[stephenw at fedoraproject.org]

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

On branch  : master

>---------------------------------------------------------------

commit 7357868c169e13120f48d57c89868391507cc6b9
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Tue Jan 6 22:45:06 2015 +0100

    Minor corrections after review


>---------------------------------------------------------------

 en-US/Consistent_Network_Device_Naming.xml |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/en-US/Consistent_Network_Device_Naming.xml b/en-US/Consistent_Network_Device_Naming.xml
index 6e72c48..b6876d3 100644
--- a/en-US/Consistent_Network_Device_Naming.xml
+++ b/en-US/Consistent_Network_Device_Naming.xml
@@ -13,7 +13,7 @@
     Traditionally, network interfaces in Linux are enumerated as <interfacename>eth[0123&#8230;]</interfacename>, but these names do not necessarily correspond to actual labels on the chassis. Modern server platforms with multiple network adapters can encounter non-deterministic and counter-intuitive naming of these interfaces. This affects both network adapters embedded on the motherboard (<firstterm>Lan-on-Motherboard</firstterm>, or <firstterm><acronym>LOM</acronym></firstterm>) and add-in (single and multiport) adapters.
   </para>
   <para>
-    In &MAJOROSVER;, <systemitem class="daemon">systemd</systemitem> and <application>udev</application> support a number of different naming schemes. The default is to assign fixed names based on firmware, topology, and location information. This has the advantage that the names are fully automatic, fully predictable, that they stay fixed even if hardware is added or removed (no re-enumeration takes place), and that broken hardware can be replaced seamlessly. The disadvantage is that they are sometimes harder to read than the <interface>eth0</interface> or <interface>wlan0</interface> names traditionally used. For example: <interface>enp5s0</interface>.
+    In &MAJOROSVER;, <application>udev</application> supports a number of different naming schemes. The default is to assign fixed names based on firmware, topology, and location information. This has the advantage that the names are fully automatic, fully predictable, that they stay fixed even if hardware is added or removed (no re-enumeration takes place), and that broken hardware can be replaced seamlessly. The disadvantage is that they are sometimes harder to read than the <interface>eth0</interface> or <interface>wlan0</interface> names traditionally used. For example: <interface>enp5s0</interface>.
   </para>
 
 <section id="sec-Naming_Schemes_Hierarchy">
@@ -52,7 +52,7 @@
 
 
    <para>
-     This policy, the procedure outlined above, is the default. If the system has <application>biosdevname</application> enabled, it will be used. Note that enabling <application>biosdevname</application> requires passing <command>biosdevname=1</command> as a command line parameter except in the case of a Dell system, where <application>biosdevname</application> will be used by default as long as it is installed. If the user has added <application>udev</application> rules which change the name of the kernel devices, those rules will take precedence.
+     This policy, the procedure outlined above, is the default. If the system has <application>biosdevname</application> enabled, it will be used. Note that enabling <application>biosdevname</application> requires passing <command>biosdevname=1</command> as a command-line parameter except in the case of a Dell system, where <application>biosdevname</application> will be used by default as long as it is installed. If the user has added <application>udev</application> rules which change the name of the kernel devices, those rules will take precedence.
    </para>
 
    </section>
@@ -428,7 +428,7 @@ The name provided by <systemitem class="daemon">systemd-udev</systemitem> will b
       <para>
         Add the following line to the <filename>/etc/default/grub</filename> file:
         <synopsis>net.ifnames=0</synopsis>
-        or pass it to the kernel at boot time using the GRUB2 command line interface. For more information about GRUB2 see <ulink url="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/"><citetitle pubwork="book">&MAJOROSVER; System Administrator's Guide</citetitle></ulink>.</para>
+        or pass it to the kernel at boot time using the GRUB2 command-line interface. For more information about GRUB2 see <citetitle pubwork="book">&MAJOROSVER; System Administrator's Guide</citetitle>.</para>
     </listitem>
   </itemizedlist>
 </para>