[networking-guide] 21: VLAN name should correspond with VLAN id (f786909)

[stephenw at fedoraproject.org]

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

On branch  : 21

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

commit f786909858b4137f5eedb147fdfc8ceee3e3f9f5
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Sun Mar 29 19:21:13 2015 +0200

    VLAN name should correspond with VLAN id


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

 en-US/Configure_802_1Q_VLAN_Tagging.xml |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/en-US/Configure_802_1Q_VLAN_Tagging.xml b/en-US/Configure_802_1Q_VLAN_Tagging.xml
index f09c7ad..6f0810c 100644
--- a/en-US/Configure_802_1Q_VLAN_Tagging.xml
+++ b/en-US/Configure_802_1Q_VLAN_Tagging.xml
@@ -363,16 +363,16 @@ GENERAL.STATE:                          activating
 Further options for the VLAN command are listed in the VLAN section of the <filename>nmcli(1)</filename> man page. In the man pages the device on which the VLAN is created is referred to as the parent device. In the example above the device was specified by its interface name, <literal>eth0</literal>, it can also be specified by the connection UUID or MAC address.
   </para>
   <para>
-        To create an 802.1Q VLAN connection profile with ingress priority mapping on Ethernet interface <replaceable>eth1</replaceable>, with name <interface>VLAN1</interface> and ID <literal>13</literal>, issue a command as follows:
-        <screen>~]$&nbsp;<command>nmcli con add type vlan con-name <replaceable>VLAN1</replaceable> dev <replaceable>eth2</replaceable> id 13 ingress "2:3,3:5"</command></screen>
+        To create an 802.1Q VLAN connection profile with ingress priority mapping on Ethernet interface <replaceable>eth1</replaceable>, with name <interface>VLAN13</interface> and ID <literal>13</literal>, issue a command as follows:
+        <screen>~]$&nbsp;<command>nmcli con add type vlan con-name <replaceable>VLAN13</replaceable> dev <replaceable>eth2</replaceable> id 13 ingress "2:3,3:5"</command></screen>
   </para>
   <para>
     To view all the parameters associated with the VLAN created above, issue a command as follows:
-    <screen>~]$&nbsp;<command>nmcli connection show <replaceable>vlan-VLAN10</replaceable></command></screen>
+    <screen>~]$&nbsp;<command>nmcli connection show <replaceable>VLAN13</replaceable></command></screen>
   </para>
   <para>
  To change the MTU, issue a command as follows:
-    <screen>~]$&nbsp;<command>nmcli connection modify <replaceable>vlan-VLAN10</replaceable> 802.mtu 1496</command></screen>
+    <screen>~]$&nbsp;<command>nmcli connection modify <replaceable>VLAN13</replaceable> 802.mtu 1496</command></screen>
         The MTU setting determines the maximum size of the network layer packet. The maximum size of the payload the link-layer frame can carry in turn limits the network layer MTU. For standard Ethernet frames this means an MTU of 1500 bytes. It should not be necessary to change the MTU when setting up a VLAN as the link-layer header is increased in size by 4 bytes to accommodate the 802.1Q tag.
   </para>
   <para>