[networking-guide] master: Improve "system connections" section (3ba37b1)

[stephenw at fedoraproject.org]

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

On branch  : master

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

commit 3ba37b1515a0feeeeac05c8e1c9277d3e2dfca16
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Fri Mar 21 15:25:25 2014 +0100

    Improve "system connections" section


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

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

diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index 2f380f7..6761fe7 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -172,10 +172,10 @@
        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.
         </para>
         <para>
- <application>NetworkManager</application>'s default policy enables users to create and modify user connections, but requires them to have <systemitem class="username">root</systemitem> privileges to add, modify, or delete system 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 <literal>joe-em2</literal> connection with <command>ONBOOT=yes; USERS=joe</command>, it will not be available at boot time.</para>
+ <application>NetworkManager</application>'s default policy enables users to create and modify user connections, but requires them to have <systemitem class="username">root</systemitem> privileges to add, modify, or delete system 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>
       <note
         id="note-Tip-Increase_security_by_making_VPN_connections_user-specific">
-        <para>Because creating a <firstterm>virtual private network</firstterm> (<acronym>VPN</acronym>) involves details considered confidential, it is recommended to configure your personal VPN connections as private by means of the <command>USERS</command> directive in the <filename>ifcfg</filename> files or by unselecting the checkboxes in the graphical user interface tools mentioned above. If you do so, then other non-root users on the system cannot access these connections, or view their settings, in any way.</para>
+        <para>Because creating a <firstterm>virtual private network</firstterm> (<acronym>VPN</acronym>) involves details considered confidential, it is recommended to configure your personal VPN connections as private. This can be done by unselecting the checkboxes in the graphical user interface tools mentioned above. If you do so, then other non-root users on the system cannot access these connections, or view their settings, in any way.</para>
       </note>
 
       <procedure>