[networking-guide] master: Typos (35af15d)

stephenw at fedoraproject.org stephenw at fedoraproject.org
Fri Jan 2 07:54:22 UTC 2015


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

On branch  : master

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

commit 35af15d1fb355c42601442354770d95b1b89e571
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Fri Jan 2 08:49:11 2015 +0100

    Typos


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

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

diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index b19c415..1a49f32 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -1852,10 +1852,10 @@ Take care not to add the same token to more than one system or interface. The du
     <para>
       The command‐line tool <application>nmcli</application> can be used by both users and scripts for controlling <application>NetworkManager</application>. The basic format of a command is as follows:
       <synopsis>nmcli <option>OPTIONS</option> OBJECT { <command>COMMAND</command> | help }</synopsis>
-      where OBJECT can be one of <literal>general</literal>, <literal>networking</literal>, <literal>radio</literal>, <literal>connection</literal>, or <literal>device</literal>. The most used options are: <option>-t, --terse</option> for use in scripts, the <option>-p, --pretty</option> option for users, and the <option>-h, --help</option> option. Command completion has been implemented for <application>nmcli</application>, so remember to press <keycap>Tab</keycap> when ever you are unsure of the command options available. See the <filename>nmcli(1)</filename> man page for a complete list of the options and commands.
+      where OBJECT can be one of <literal>general</literal>, <literal>networking</literal>, <literal>radio</literal>, <literal>connection</literal>, or <literal>device</literal>. The most used options are: <option>-t, --terse</option> for use in scripts, the <option>-p, --pretty</option> option for users, and the <option>-h, --help</option> option. Command completion has been implemented for <application>nmcli</application>, so remember to press <keycap>Tab</keycap> whenever you are unsure of the command options available. See the <filename>nmcli(1)</filename> man page for a complete list of the options and commands.
   </para>
   <para>
-    The <application>nmcli</application> tool has some built-in context sensitive help. For example, issue the following two commands and notice the difference:
+    The <application>nmcli</application> tool has some built-in context-sensitive help. For example, issue the following two commands and notice the difference:
     <screen>~]$&nbsp;<command>nmcli help</command>
 Usage: nmcli [OPTIONS] OBJECT { COMMAND | help }
 
@@ -1923,7 +1923,7 @@ In the second example above the help is related to the object <literal>general</
 </para>
 <bridgehead id="bh-Starting_and_Stopping_an_Interface_Using_nmcli">Starting and Stopping an Interface Using nmcli</bridgehead>
 <para>
-  The <application>nmcli</application> tool can be used to start and stop any network interface including masters. For example:
+  The <application>nmcli</application> tool can be used to start and stop any network interface, including masters. For example:
   <screen>nmcli con up id bond0
 nmcli con up id port0
 nmcli dev disconnect iface bond0
@@ -2020,7 +2020,7 @@ lo          loopback        unmanaged</screen>
 
     <bridgehead id="Adding_an_Ethernet_Connection">Adding an Ethernet Connection</bridgehead>
     <para>
-    To add an Ethernet connection with manual <systemitem class="protocol">IP</systemitem> configuration, issue a command as follows:
+    To add an Ethernet connection with static <systemitem class="protocol">IP</systemitem> configuration, issue a command as follows:
     <screen>~]$&nbsp;<command>nmcli con add con-name <replaceable>my-eth1</replaceable> ifname <replaceable>eth1</replaceable> type ethernet ip4 192.168.100.100/24 \</command>
       <command>gw4 192.168.100.1</command></screen>
      Optionally, at the same time specify <systemitem class="protocol">IPv6</systemitem> addresses for the device as follows:
@@ -2058,9 +2058,9 @@ To make a profile usable for all compatible Ethernet interfaces, issue a command
   MyCafe         Infra  11    54 MB/s  39      ▂▄__  WPA2</screen>
 </para>
   <para>
-  To create a Wi-Fi connection profile with manual <systemitem class="protocol">IP</systemitem> configuration, but allowing automatic <systemitem class="protocol">DNS</systemitem> address assignment, issue a command as follows:
+  To create a Wi-Fi connection profile with static <systemitem class="protocol">IP</systemitem> configuration, but allowing automatic <systemitem class="protocol">DNS</systemitem> address assignment, issue a command as follows:
     <screen>~]$&nbsp;<command>nmcli con add con-name <replaceable>MyCafe</replaceable> ifname wlan0 type wifi ssid MyCafe \</command>
-      <command>p4 192.168.100.101/24 gw4 192.168.100.1</command></screen>
+<command>ip4 192.168.100.101/24 gw4 192.168.100.1</command></screen>
    To set a WPA2 password, for example <quote>caffeine</quote>, issue commands as follows:
 <screen>~]$&nbsp;<command>nmcli con modify <replaceable>MyCafe</replaceable> wifi-sec.key-mgmt wpa-psk</command>
 ~]$&nbsp;<command>nmcli con modify <replaceable>MyCafe</replaceable> wifi-sec.psk caffeine</command></screen>



More information about the docs-commits mailing list