[networking-guide] master: Typos and style improvements (47498b1)
stephenw at fedoraproject.org
stephenw at fedoraproject.org
Mon Jul 28 20:44:39 UTC 2014
Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
>---------------------------------------------------------------
commit 47498b1933f8d1040f830d6af4c161db830c15c1
Author: Stephen Wadeley <swadeley at redhat.com>
Date: Mon Jul 28 22:42:16 2014 +0200
Typos and style improvements
Thanks to yruseva and jherrman for their review.
>---------------------------------------------------------------
en-US/Configure_Networking.xml | 66 ++++++++++++++++++++--------------------
1 files changed, 33 insertions(+), 33 deletions(-)
diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index 53c8c7e..ecf7aa0 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -10,7 +10,7 @@
<section id="sec-Static_and_Dynamic_Interface_Settings">
<title>Static and Dynamic Interface Settings</title>
<para>
- When to use static addressing and when to use dynamic addressing? These decisions are subjective, they depend on your accessed needs, your specific requirements. Having a policy, documenting it, and applying it consistently are usually more important than the specific decisions you make. In a traditional company LAN, this is an easier decision to make as you typically have fewer servers than other hosts. Provisioning and installation tools make providing static configurations to new hosts easy and using such tools will change your work flow and requirements. The following two sections are intended to provide guidance to those who have not already been through this decision making process. For more information on automated configuration and management, see the <application>OpenLMI</application> section in the <citetitle pubwork="book">System Administrators Guide</citetitle>. The <citetitle pubwork="book">System Installation Guide</citetitle> documents the use of <applicat
ion>kickstart</application> which can also be used for automating the assignment of network settings.
+ When to use static addressing and when to use dynamic addressing? These decisions are subjective, they depend on your accessed needs, your specific requirements. Having a policy, documenting it, and applying it consistently are usually more important than the specific decisions you make. In a traditional company LAN, this is an easier decision to make as you typically have fewer servers than other hosts. Provisioning and installation tools make providing static configurations to new hosts easy and using such tools will change your work flow and requirements. The following two sections are intended to provide guidance to those who have not already been through this decision-making process. For more information on automated configuration and management, see the <application>OpenLMI</application> section in the <citetitle pubwork="book">System Administrators Guide</citetitle>. The <citetitle pubwork="book">System Installation Guide</citetitle> documents the use of <applicat
ion>kickstart</application> which can also be used for automating the assignment of network settings.
</para>
<section id="sec-When_to_Use_Static_Network_Interface_Settings">
<title>When to Use Static Network Interface Settings</title>
@@ -27,7 +27,7 @@
<para>
</para>
<para>
- Enable and use dynamic assignment of <systemitem class="protocol">IP</systemitem> addresses and other network information whenever there is no compelling reason not to. The time saved in planing and documenting manual settings can be better spent elsewhere. See <xref linkend="sec-dhcp-why" /> for more information on this subject.
+ Enable and use dynamic assignment of <systemitem class="protocol">IP</systemitem> addresses and other network information whenever there is no compelling reason not to. The time saved in planning and documenting manual settings can be better spent elsewhere. See <xref linkend="sec-dhcp-why" /> for more information on this subject.
</para>
<para>
Note that <application>NetworkManager</application> will start the <systemitem class="protocol">DHCP</systemitem> client, <application>dhclient</application>, automatically.
@@ -91,7 +91,7 @@
</mediaobject>
</figure>
<para>
- The <guilabel>Network</guilabel> settings window has a menu on the left-hand side showing the available network devices or interfaces. This includes software interfaces such as for VLANs, bridges, bonds, and teams. On the right-hand side the <firstterm>connection profiles</firstterm> are shown for the selected network device or interface. A profile is a named collection of settings that can be applied to an interface. Below that is a plus and minus button for adding and deleting new network connections, and on the right a gear wheel icon will appear for editing the connection details of the selected network device or VPN connection. To add a new connection, click the plus symbol to open the <guilabel>Add Network Connection</guilabel> window and proceed to <xref linkend="bh-Configuring_a_New_Connection" />.</para>
+ The <guilabel>Network</guilabel> settings window has a menu on the left-hand side showing the available network devices or interfaces. This includes software interfaces such as for VLANs, bridges, bonds, and teams. On the right-hand side, the <firstterm>connection profiles</firstterm> are shown for the selected network device or interface. A profile is a named collection of settings that can be applied to an interface. Below that is a plus and a minus button for adding and deleting new network connections, and on the right a gear wheel icon will appear for editing the connection details of the selected network device or VPN connection. To add a new connection, click the plus symbol to open the <guilabel>Add Network Connection</guilabel> window and proceed to <xref linkend="bh-Configuring_a_New_Connection" />.</para>
<bridgehead id="bh-Editing_an_Existing_Connection">Editing an Existing Connection</bridgehead>
<para>Clicking on the gear wheel icon of an existing connection profile in the <guilabel>Network</guilabel> settings window opens the <guilabel>Network</guilabel> details window, from where you can perform most network configuration tasks such as <systemitem class="protocol">IP</systemitem> addressing, <systemitem class="protocol">DNS</systemitem>, and routing configuration.</para>
<figure id="exam-Configuring_New_and_Editing_Existing_Connections_Network-Details-Window">
@@ -109,7 +109,7 @@
</figure>
<bridgehead id="bh-Configuring_a_New_Connection">Configuring a New Connection</bridgehead>
<para>
- On the <guilabel>Network</guilabel> settings window, clicking on the plus sign below the menu opens the <guilabel>Add Network Connection</guilabel> window. This displays a list of connection types that can be added.
+ In the <guilabel>Network</guilabel> settings window, click the plus sign below the menu to open the <guilabel>Add Network Connection</guilabel> window. This displays a list of connection types that can be added.
</para>
<para>Then, to configure:</para>
@@ -126,16 +126,16 @@
</listitem>
<listitem>
<para>Bridge connections, click the <guilabel>Bridge</guilabel> entry and proceed to <xref
- linkend="sec-Establishing_a_Bridge_Connection"/>; or,
+ linkend="sec-Establishing_a_Bridge_Connection"/>;
</para>
</listitem>
<listitem>
<para>VLAN connections, click the <guilabel>VLAN</guilabel> entry and proceed to <xref
- linkend="sec-Establishing_a_VLAN_Connection"/>.
+ linkend="sec-Establishing_a_VLAN_Connection"/>;or,
</para>
</listitem>
<listitem>
- <para>Team connections, click the <guilabel>Team</guilabel> entry and proceed to <xref linkend="sec-Creating_a_Network_Team_Using_a_GUI" />
+ <para>Team connections, click the <guilabel>Team</guilabel> entry and proceed to <xref linkend="sec-Creating_a_Network_Team_Using_a_GUI" />.
</para>
</listitem>
</itemizedlist>
@@ -161,7 +161,7 @@
<para>Select the <guilabel>Identity</guilabel> menu entry on the left. The <guilabel>Network</guilabel> window changes to the identity view.</para>
</step>
<step>
- <para>Select <guilabel>Connect automatically</guilabel> to cause <application>NetworkManager</application> to auto-connect to the connection whenever <application>NetworkManager</application> detects that it is available. Unselect the check box if you do not want <application>NetworkManager</application> to connect automatically. If the box is unselected, you will have to select that connection manually in the network applet menu to cause it to connect.</para>
+ <para>Select <guilabel>Connect automatically</guilabel> to cause <application>NetworkManager</application> to auto-connect to the connection whenever <application>NetworkManager</application> detects that it is available. Clear the check box if you do not want <application>NetworkManager</application> to connect automatically. If the check box is clear, you will have to select that connection manually in the network applet menu to cause it to connect.</para>
</step>
</procedure>
</section>
@@ -170,18 +170,18 @@
id="sec-System-wide_and_Private_Connection_Profiles">
<title>System-wide and Private Connection Profiles</title>
<para>
- <application>NetworkManager</application> stores all <firstterm>connection profiles</firstterm>. A profile is a named collection of settings that can be applied to an interface. <application>NetworkManager</application> stores these connection profiles for system-wide use (<firstterm>system connections</firstterm>) as well as all <firstterm>user connection</firstterm> profiles. Access to the connection profiles is controlled by permissions which are stored by <application>NetworkManager</application>. See man <filename>nm-settings(5)</filename> for more information on the <option>connection</option> settings <option>permissions</option> property. The permissions correspond to the <command>USERS</command> directive in the <filename>ifcfg</filename> files. If the <command>USERS</command> directive is not present, the network profile will be available to all users. As an example, the following command in an <filename>ifcfg</filename> file will make the connection availa
ble only to the users listed:
+ <application>NetworkManager</application> stores all <firstterm>connection profiles</firstterm>. A profile is a named collection of settings that can be applied to an interface. <application>NetworkManager</application> stores these connection profiles for system-wide use (<firstterm>system connections</firstterm>), as well as all <firstterm>user connection</firstterm> profiles. Access to the connection profiles is controlled by permissions which are stored by <application>NetworkManager</application>. See the <filename>nm-settings(5)</filename> man page for more information on the <option>connection</option> settings <option>permissions</option> property. The permissions correspond to the <command>USERS</command> directive in the <filename>ifcfg</filename> files. If the <command>USERS</command> directive is not present, the network profile will be available to all users. As an example, the following command in an <filename>ifcfg</filename> file will make the connect
ion available only to the users listed:
<synopsis>USERS="joe bob alice"</synopsis>
- This can also be set using graphical user interface tools. In <application>nm-connection-editor</application> there is the corresponding <guilabel>All users may connect to this network</guilabel> checkbox on the <guilabel>General</guilabel> tab and in the GNOME <application>control-center</application> Network settings Identity window there is the <guilabel>Make available to other users</guilabel> checkbox.
+ This can also be set using graphical user interface tools. In <application>nm-connection-editor</application>, there is the corresponding <guilabel>All users may connect to this network</guilabel> check box on the <guilabel>General</guilabel> tab, and in the GNOME <application>control-center</application> Network settings Identity window, there is the <guilabel>Make available to other users</guilabel> check box.
</para>
<para>
- <application>NetworkManager</application>'s default policy is to allow all users to create and modify system-wide connections. Profiles that should be available at boot time cannot be private because they will not be visible until the user logs in. For example, if user <systemitem class="username">joe</systemitem> creates a connection profile <literal>joe-em2</literal> with the <guilabel>Connect Automatically</guilabel> checkbox selected but the <guilabel>Make available to other users</guilabel> unselected, then the connection will not be available at boot time.</para>
+ <application>NetworkManager</application>'s default policy is to allow all users to create and modify system-wide connections. Profiles that should be available at boot time cannot be private because they will not be visible until the user logs in. For example, if user <systemitem class="username">user</systemitem> creates a connection profile <literal>user-em2</literal> with the <guilabel>Connect Automatically</guilabel> check box selected but with the <guilabel>Make available to other users</guilabel> not selected, then the connection will not be available at boot time.</para>
<para>
-To restrict a connections and networking, there are two options which can be used alone or in combination:
+To restrict connections and networking, there are two options which can be used alone or in combination:
<itemizedlist>
<listitem>
<para>
- Unselect the <guilabel>Make available to other users</guilabel> box, which changes the connection to be modifiable and usable only by the user doing the changing.
+ Clear the <guilabel>Make available to other users</guilabel> check box, which changes the connection to be modifiable and usable only by the user doing the changing.
</para>
</listitem>
<listitem>
@@ -190,7 +190,7 @@ To restrict a connections and networking, there are two options which can be use
</para>
</listitem>
</itemizedlist>
- The combination of these two options provides fine-grained security and control over networking. See man <filename>polkit(8)</filename> for more information on <application>polkit</application>.
+ The combination of these two options provides fine-grained security and control over networking. See the <filename>polkit(8)</filename> man page for more information on <application>polkit</application>.
</para>
<para>
@@ -213,8 +213,8 @@ To restrict a connections and networking, there are two options which can be use
<para>Select the <guilabel>Identity</guilabel> menu entry on the left. The <guilabel>Network</guilabel> window changes to the identity view.</para>
</step>
<step>
- <para>Select the <guilabel>Make available to other users</guilabel> check box to cause <application>NetworkManager</application> to make the connection a system-wide connection. Depending on system policy, you may then be prompted for the root password by the <application>PolicyKit</application> application. If so, enter the <systemitem class="username">root</systemitem> password to finalize the change.</para>
- <para>Conversely, unselect the <guilabel>Make available to other users</guilabel> check box to make the connection user-specific.</para>
+ <para>Select the <guilabel>Make available to other users</guilabel> check box to cause <application>NetworkManager</application> to make the connection available system-wide. Depending on system policy, you may then be prompted for the root password by the <application>PolicyKit</application> application. If so, enter the <systemitem class="username">root</systemitem> password to finalize the change.</para>
+ <para>Conversely, clear the <guilabel>Make available to other users</guilabel> check box to make the connection user-specific.</para>
</step>
</procedure>
</section>
@@ -243,7 +243,7 @@ To restrict a connections and networking, there are two options which can be use
</listitem>
<listitem>
<para>
- <guilabel>MAC Address</guilabel> — Select the MAC address of the interface this profile must be applied too.
+ <guilabel>MAC Address</guilabel> — Select the MAC address of the interface this profile must be applied to.
</para>
</listitem>
<listitem>
@@ -283,12 +283,12 @@ To restrict a connections and networking, there are two options which can be use
id="bh-Saving_Your_New_or_Modified_Connection_and_Making_Further_Configurations-Wired">Saving Your New (or Modified) Connection and Making Further Configurations</bridgehead>
<para>Once you have finished editing your wired connection, click the <guibutton>Apply</guibutton> button and <application>NetworkManager</application> will immediately save your customized configuration. Given a correct configuration, you can connect to your new or customized connection by selecting it from the network Notification Area applet. See <xref
linkend="sec-Connecting_to_a_Network_Using_a_GUI"/> for information on using your new or altered connection.</para>
- <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking gear wheel icon to return to the editing dialog.</para>
+ <para>You can further configure an existing connection by selecting it in the <guilabel>Network</guilabel> window and clicking the gear wheel icon to return to the editing dialog.</para>
<para>Then, to configure:</para>
<itemizedlist>
<listitem>
- <para>port-based Network Access Control (PNAC), click the <guilabel>802.1x Security</guilabel> tab and proceed to <xref
- linkend="sec-Configuring_802.1x_Security"/>;
+ <para>port-based Network Access Control (PNAC), click the <guilabel>802.1X Security</guilabel> tab and proceed to <xref
+ linkend="sec-Configuring_802.1X_Security"/>;
</para>
</listitem>
<listitem>
@@ -315,7 +315,7 @@ To restrict a connections and networking, there are two options which can be use
id="bh-Quickly_Connecting_to_an_Available_Access_Point">Quickly Connecting to an Available Access Point</bridgehead>
<para>The easiest way to connect to an available access point is to click on the network icon to activate the Notification Area applet, locate the <firstterm>Service Set Identifier</firstterm> (<acronym>SSID</acronym>) of the access point in the list of <guilabel>Wi-Fi</guilabel> networks, and click on it. A padlock symbol indicates the access point requires authentication. If the access point is secured, a dialog prompts you for an authentication key or password.</para>
<para>
- <application>NetworkManager</application> tries to auto-detect the type of security used by the access point. If there are multiple possibilities, <application>NetworkManager</application> guesses the security type and presents it in the <guilabel>Wi-Fi security</guilabel> dropdown menu. To see if there are multiple choices, click the <guilabel>Wi-Fi security</guilabel> dropdown menu and select the type of security the access point is using. If you are unsure, try connecting to each type in turn. Finally, enter the key or passphrase in the <guilabel>Password</guilabel> field. Certain password types, such as a 40-bit WEP or 128-bit WPA key, are invalid unless they are of a requisite length. The <guilabel>Connect</guilabel> button will remain inactive until you enter a key of the length required for the selected security type. To learn more about wireless security, see <xref
+ <application>NetworkManager</application> tries to auto-detect the type of security used by the access point. If there are multiple possibilities, <application>NetworkManager</application> guesses the security type and presents it in the <guilabel>Wi-Fi security</guilabel> drop-down menu. To see if there are multiple choices, click the <guilabel>Wi-Fi security</guilabel> drop-down menu and select the type of security the access point is using. If you are unsure, try connecting to each type in turn. Finally, enter the key or passphrase in the <guilabel>Password</guilabel> field. Certain password types, such as a 40-bit WEP or 128-bit WPA key, are invalid unless they are of a requisite length. The <guilabel>Connect</guilabel> button will remain inactive until you enter a key of the length required for the selected security type. To learn more about wireless security, see <xref
linkend="sec-Configuring_Wi-Fi_Security"/>.</para>
@@ -713,7 +713,7 @@ To restrict a connections and networking, there are two options which can be use
<step>
<para>Select your provider from the list or enter it manually. Click the <guilabel>Continue</guilabel> button.</para>
</step>
- <step><para>Select your payment plan from the dropdown menu and confirm the <firstterm>Access Point Name</firstterm> (<acronym>APN</acronym>) is correct. Click the <guilabel>Continue</guilabel> button.</para>
+ <step><para>Select your payment plan from the drop-down menu and confirm the <firstterm>Access Point Name</firstterm> (<acronym>APN</acronym>) is correct. Click the <guilabel>Continue</guilabel> button.</para>
</step>
<step>
<para>Review and confirm the settings and then click the <guilabel>Apply</guilabel> button.</para>
@@ -764,7 +764,7 @@ To restrict a connections and networking, there are two options which can be use
</listitem>
<listitem>
<para>
- <guilabel>Firewall Zone</guilabel> — Select the Firewall Zone from the dropdown menu.
+ <guilabel>Firewall Zone</guilabel> — Select the Firewall Zone from the drop-down menu.
</para>
</listitem>
</itemizedlist>
@@ -956,7 +956,7 @@ To restrict a connections and networking, there are two options which can be use
</listitem>
<listitem>
<para>
- <guilabel>Firewall Zone</guilabel> — Select the Firewall Zone from the dropdown menu.
+ <guilabel>Firewall Zone</guilabel> — Select the Firewall Zone from the drop-down menu.
</para>
</listitem>
</itemizedlist>
@@ -1059,11 +1059,11 @@ To restrict a connections and networking, there are two options which can be use
</step>
<step>
<para>
- From the dropdown menu select one of the following security methods: <guimenuitem>LEAP</guimenuitem>, <guimenuitem>Dynamic WEP (802.1x)</guimenuitem>, or <guimenuitem>WPA & WPA2 Enterprise</guimenuitem>.</para>
+ From the drop-down menu select one of the following security methods: <guimenuitem>LEAP</guimenuitem>, <guimenuitem>Dynamic WEP (802.1X)</guimenuitem>, or <guimenuitem>WPA & WPA2 Enterprise</guimenuitem>.</para>
</step>
<step>
<para>Refer to <xref
- linkend="sec-Configuring_TLS_Transport_Layer_Security_Settings"/> for descriptions of which <firstterm>extensible authentication protocol</firstterm> (<acronym>EAP</acronym>) types correspond to your selection in the <guilabel>Security</guilabel> dropdown menu.</para>
+ linkend="sec-Configuring_TLS_Transport_Layer_Security_Settings"/> for descriptions of which <firstterm>extensible authentication protocol</firstterm> (<acronym>EAP</acronym>) types correspond to your selection in the <guilabel>Security</guilabel> drop-down menu.</para>
</step>
</procedure>
<section
@@ -1169,7 +1169,7 @@ To restrict a connections and networking, there are two options which can be use
<guilabel>PAC provisioning</guilabel>
</term>
<listitem>
- <para>Select the checkbox to enable and then select from <guimenu>Anonymous</guimenu>, <guimenu>Authenticated</guimenu>, and <guimenu>Both</guimenu>.</para>
+ <para>Select the check box to enable and then select from <guimenu>Anonymous</guimenu>, <guimenu>Authenticated</guimenu>, and <guimenu>Both</guimenu>.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1342,11 +1342,11 @@ To restrict a connections and networking, there are two options which can be use
<para>
<guimenuitem>LEAP</guimenuitem> — Lightweight Extensible Authentication Protocol, from Cisco Systems.</para>
<para>
- <guimenuitem>Dynamic WEP (802.1x)</guimenuitem> — WEP keys are changed dynamically. Use with <xref linkend="sec-Configuring_TLS_Transport_Layer_Security_Settings" /> </para>
+ <guimenuitem>Dynamic WEP (802.1X)</guimenuitem> — WEP keys are changed dynamically. Use with <xref linkend="sec-Configuring_TLS_Transport_Layer_Security_Settings" /> </para>
<para>
<guimenuitem>WPA & WPA2 Personal</guimenuitem> — Wi-Fi Protected Access (WPA), from the draft IEEE 802.11i standard. A replacement for WEP. Wi-Fi Protected Access II (WPA2), from the 802.11i-2004 standard. Personal mode uses a pre-shared key (WPA-PSK).</para>
<para>
- <guimenuitem>WPA & WPA2 Enterprise</guimenuitem> — WPA for use with a RADUIS authentication server to provide IEEE 802.1x network access control. Use with <xref linkend="sec-Configuring_TLS_Transport_Layer_Security_Settings" /></para>
+ <guimenuitem>WPA & WPA2 Enterprise</guimenuitem> — WPA for use with a RADIUS authentication server to provide IEEE 802.1X network access control. Use with <xref linkend="sec-Configuring_TLS_Transport_Layer_Security_Settings" /></para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1423,7 +1423,7 @@ To restrict a connections and networking, there are two options which can be use
<variablelist
id="varlist-Available_IPv4_Methods_by_Connection_Type">
<title>Available IPv4 Methods by Connection Type</title>
- <para>When you click the <guilabel>Method</guilabel> dropdown menu, depending on the type of connection you are configuring, you are able to select one of the following <systemitem class="protocol">IPv4</systemitem> connection methods. All of the methods are listed here according to which connection type, or types, they are associated with:</para>
+ <para>When you click the <guilabel>Method</guilabel> drop-down menu, depending on the type of connection you are configuring, you are able to select one of the following <systemitem class="protocol">IPv4</systemitem> connection methods. All of the methods are listed here according to which connection type, or types, they are associated with:</para>
<varlistentry>
<term>
<guilabel>Method</guilabel>
@@ -1543,7 +1543,7 @@ To restrict a connections and networking, there are two options which can be use
<para>
<guimenuitem>Gateway</guimenuitem> — The <systemitem class="protocol">IP</systemitem> address of the gateway leading to the remote network, sub-net, or host entered above.</para>
<para>
- <guimenuitem>Metric</guimenuitem> — A network cost, that is to say a preference value to give to this route. Lower values will be preferred over higher values.</para>
+ <guimenuitem>Metric</guimenuitem> — A network cost, a preference value to give to this route. Lower values will be preferred over higher values.</para>
</listitem>
</varlistentry>
<varlistentry>
@@ -1559,7 +1559,7 @@ To restrict a connections and networking, there are two options which can be use
<guilabel>Use this connection only for resources on its network</guilabel>
</term>
<listitem>
- <para>Select this check box to prevent the connection from becoming the default route. Typical examples are where a connection is a VPN tunnel or a leased line to a head office and you do not want any Internet bound traffic to pass over the connection. Selecting this option means that only traffic specifically destined for routes learned automatically over the connection or entered here manually will be routed over the connection.</para>
+ <para>Select this check box to prevent the connection from becoming the default route. Typical examples are where a connection is a VPN tunnel or a leased line to a head office and you do not want any Internet-bound traffic to pass over the connection. Selecting this option means that only traffic specifically destined for routes learned automatically over the connection or entered here manually will be routed over the connection.</para>
</listitem>
</varlistentry>
</variablelist>
@@ -2074,7 +2074,7 @@ To make a profile usable for all compatible Ethernet interfaces, issue a command
</varlistentry>
<varlistentry>
-<term><ulink url="http://www.rfc-editor.org/info/rfc3330"><citetitle pubwork="webpage">RFC 3330</citetitle></ulink> — Special-Use IPv4 Addresses</term>
+<term><ulink url="http://www.rfc-editor.org/info/rfc3330"><citetitle pubwork="webpage">RFC 3330</citetitle></ulink> — Special-Use IPv4 Addresses</term>
<listitem>
<para>
Describes the global and other specialized <systemitem class="protocol">IPv4</systemitem> address blocks that have been assigned by the Internet Assigned Numbers Authority (IANA).
More information about the docs-commits
mailing list