[networking-guide] master: Remove markup tags from Fedora (3412dba)

[stephenw at fedoraproject.org]

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

On branch  : master

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

commit 3412dba26c44532b717f21ddfb6124a5af016c38
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Mon Jul 28 22:16:50 2014 +0200

    Remove markup tags from Fedora


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

 en-US/Configure_802_1Q_VLAN_Tagging.xml     |    2 +-
 en-US/Configure_Network_Bridging.xml        |    2 +-
 en-US/Introduction_to_Fedora_Networking.xml |    8 ++++----
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/en-US/Configure_802_1Q_VLAN_Tagging.xml b/en-US/Configure_802_1Q_VLAN_Tagging.xml
index 368fbf7..353cb8e 100644
--- a/en-US/Configure_802_1Q_VLAN_Tagging.xml
+++ b/en-US/Configure_802_1Q_VLAN_Tagging.xml
@@ -164,7 +164,7 @@
 <section id="sec-Configure_802_1Q_VLAN_Tagging_Using_the_Command_Line">
   <title>Configure 802.1Q VLAN Tagging Using the Command Line</title>
 <para>
-    In <application>Fedora</application>, the <systemitem class="resource">8021q</systemitem> module is loaded by default. If necessary, you can make sure that the module is loaded by issuing the following command as <systemitem class="username">root</systemitem>:
+    In Fedora, the <systemitem class="resource">8021q</systemitem> module is loaded by default. If necessary, you can make sure that the module is loaded by issuing the following command as <systemitem class="username">root</systemitem>:
     <screen>~]# <command>modprobe --first-time 8021q</command>
 modprobe: ERROR: could not insert '8021q': Module already in kernel</screen>
 To display information about the module, issue the following command:
diff --git a/en-US/Configure_Network_Bridging.xml b/en-US/Configure_Network_Bridging.xml
index 9833cc0..067d8cc 100644
--- a/en-US/Configure_Network_Bridging.xml
+++ b/en-US/Configure_Network_Bridging.xml
@@ -232,7 +232,7 @@
  <section id="sec-Check_if_Bridging_Kernel_Module_is_Installed">
    <title>Check if Bridging Kernel Module is Installed</title>
    <para>
-    In <application>Fedora</application>, the bridging module is loaded by default. If necessary, you can make sure that the module is loaded by issuing the following command as <systemitem class="username">root</systemitem>:
+    In Fedora, the bridging module is loaded by default. If necessary, you can make sure that the module is loaded by issuing the following command as <systemitem class="username">root</systemitem>:
     <screen>~]# <command>modprobe --first-time bridge</command>
 modprobe: ERROR: could not insert 'bridge': Module already in kernel</screen>
 To display information about the module, issue the following command:
diff --git a/en-US/Introduction_to_Fedora_Networking.xml b/en-US/Introduction_to_Fedora_Networking.xml
index 3cbe9d4..5080a01 100644
--- a/en-US/Introduction_to_Fedora_Networking.xml
+++ b/en-US/Introduction_to_Fedora_Networking.xml
@@ -25,7 +25,7 @@
   <title>Introduction to NetworkManager</title>
 
 <para>
- As of <application>Fedora 20</application>, the default networking service is provided by <systemitem class="service">NetworkManager</systemitem>, which is a dynamic network control and configuration daemon that attempts to keep network devices and connections up and active when they are available. The traditional <filename>ifcfg</filename> type configuration files are still supported. See <xref linkend="sec-NetworkManager_and_the_Network_Scripts" /> for more information.</para>
+ As of Fedora 20, the default networking service is provided by <systemitem class="service">NetworkManager</systemitem>, which is a dynamic network control and configuration daemon that attempts to keep network devices and connections up and active when they are available. The traditional <filename>ifcfg</filename> type configuration files are still supported. See <xref linkend="sec-NetworkManager_and_the_Network_Scripts" /> for more information.</para>
 <table id="tb-A_Summary_of_Networking_Tools_and_Applications" frame='all'>
 <title>A Summary of Networking Tools and Applications</title>
 <tgroup cols='2' align='left' colsep='1' rowsep='1'>
@@ -91,7 +91,7 @@ NetworkManager.service - Network Manager
   <section
     id="sec-Interacting_with_NetworkManager">
     <title>Interacting with NetworkManager</title>
-    <para>Users do not interact with the <application>NetworkManager</application> system service directly. Instead, users perform network configuration tasks via graphical and command line user interface tools. The following tools are available in <application>Fedora</application>:</para>
+    <para>Users do not interact with the <application>NetworkManager</application> system service directly. Instead, users perform network configuration tasks via graphical and command line user interface tools. The following tools are available in Fedora:</para>
     <para>
     <orderedlist>
       <listitem>
@@ -220,7 +220,7 @@ The file <filename>/etc/sysconfig/network</filename> is for global settings. Inf
 </para>
 
    <para>
-  In <application>Fedora</application>, when you edit an <filename>ifcfg</filename> file, <application>NetworkManager</application> is not automatically aware of the change and has to be prompted to notice the change. If you use one of the tools to update <application>NetworkManager</application> profile settings, then <application>NetworkManager</application> does not implement those changes until you reconnect using that profile. For example, if configuration files have been changed using an editor, <application>NetworkManager</application> must be told to read the configuration files again. To do that, issue the following command as <systemitem class="username">root</systemitem>:
+  In Fedora, when you edit an <filename>ifcfg</filename> file, <application>NetworkManager</application> is not automatically aware of the change and has to be prompted to notice the change. If you use one of the tools to update <application>NetworkManager</application> profile settings, then <application>NetworkManager</application> does not implement those changes until you reconnect using that profile. For example, if configuration files have been changed using an editor, <application>NetworkManager</application> must be told to read the configuration files again. To do that, issue the following command as <systemitem class="username">root</systemitem>:
   <screen>~]# <command>nmcli connection reload</command></screen>
   The above command reads all connection profiles. Alternatively, to reload only one changed file, <filename>ifcfg-<replaceable>ifname</replaceable></filename>, issue a command as follows:
   <screen>~]# <command>nmcli con load /etc/sysconfig/network-scripts/ifcfg-<replaceable>ifname</replaceable></command></screen>
@@ -283,7 +283,7 @@ The file <filename>/etc/sysconfig/network</filename> is for global settings. Inf
 
 <title>Additional Resources</title>
 <para>
-      The following sources of information provide additional resources regarding networking for <application>Fedora</application>.
+      The following sources of information provide additional resources regarding networking for Fedora.
     </para>
         <section id="sec-Introduction_to_Fedora_Networking-docs-inst">
       <title>Installed Documentation</title>