[networking-guide] master: command line (not prompt) (a924a6d)

[stephenw at fedoraproject.org]

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

On branch  : master

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

commit a924a6dd5e9a96122adcde24cbf9e98ad41ca658
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Mon Sep 29 21:38:11 2014 +0200

    command line (not prompt)
    
    as per IBM Style Guide


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

 en-US/Configure_802_1Q_VLAN_Tagging.xml |    2 +-
 en-US/Configure_Networking.xml          |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/en-US/Configure_802_1Q_VLAN_Tagging.xml b/en-US/Configure_802_1Q_VLAN_Tagging.xml
index 2feb998..3d0ae27 100644
--- a/en-US/Configure_802_1Q_VLAN_Tagging.xml
+++ b/en-US/Configure_802_1Q_VLAN_Tagging.xml
@@ -224,7 +224,7 @@ To create an 802.1Q VLAN interface on Ethernet interface <replaceable>eth0</repl
   <screen>~]# <command>ip link delete <replaceable>eth0.8</replaceable></command></screen>
 </para>
 <para>
-  VLAN interfaces created using <application>ip</application> commands at the command prompt will be lost if the system is shutdown or restarted. To configure VLAN interfaces to be persistent after a system restart, use <filename>ifcfg</filename> files. See <xref linkend="sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files" />
+  VLAN interfaces created using <application>ip</application> commands on the command line will be lost if the system is shutdown or restarted. To configure VLAN interfaces to be persistent after a system restart, use <filename>ifcfg</filename> files. See <xref linkend="sec-Setting_Up_802.1Q_VLAN_Tagging_Using_ifcfg_Files" />
 </para>
 </section>
 
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index 7de0702..b4f84e6 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -1687,7 +1687,7 @@ The address assignment of a specific device can be viewed as follows:
 <section id="sec-Configuring_Static_Routes_in_ifcfg_files">
 <title>Configuring Static Routes in ifcfg files</title>
 <para>
-Static routes set using <application>ip</application> commands at the command prompt will be lost if the system is shutdown or restarted. To configure static routes to be persistent after a system restart, they must be placed in per-interface configuration files in the <filename class="directory">/etc/sysconfig/network-scripts/</filename> directory. The file name should be of the format <filename>route-<replaceable>ethX</replaceable></filename>. There are two types of commands to use in the configuration files; <application>ip</application> commands as explained in <xref linkend="bh-networkscripts-static-routes-ip-command" /> and the <firstterm>Network/Netmask</firstterm> format as explained in <xref linkend="bh-networkscripts-static-routes-network-netmask-directives" />.
+Static routes set using <application>ip</application> commands on the command line will be lost if the system is shutdown or restarted. To configure static routes to be persistent after a system restart, they must be placed in per-interface configuration files in the <filename class="directory">/etc/sysconfig/network-scripts/</filename> directory. The file name should be of the format <filename>route-<replaceable>ethX</replaceable></filename>. There are two types of commands to use in the configuration files; <application>ip</application> commands as explained in <xref linkend="bh-networkscripts-static-routes-ip-command" /> and the <firstterm>Network/Netmask</firstterm> format as explained in <xref linkend="bh-networkscripts-static-routes-network-netmask-directives" />.
 </para>
 
 <bridgehead id="bh-networkscripts-static-routes-ip-command">