[deployment-guide: 174/185] A couple of corrections.
Jaromir Hradilek
jhradile at fedoraproject.org
Sun May 15 21:25:56 UTC 2011
commit f065cea590c2670b448a3cb4b40e7f822c1bb955
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Fri Apr 29 12:31:05 2011 +0200
A couple of corrections.
en-US/Book_Info.xml | 2 +-
en-US/NetworkManager.xml | 2 +-
en-US/Network_Interfaces.xml | 2 +-
en-US/PackageKit.xml | 8 ++++----
4 files changed, 7 insertions(+), 7 deletions(-)
---
diff --git a/en-US/Book_Info.xml b/en-US/Book_Info.xml
index f9dd3d0..3880b58 100644
--- a/en-US/Book_Info.xml
+++ b/en-US/Book_Info.xml
@@ -7,7 +7,7 @@
<productname>Red Hat Enterprise Linux</productname>
<productnumber>6</productnumber>
<edition>1</edition>
- <pubsnumber>115</pubsnumber>
+ <pubsnumber>116</pubsnumber>
<abstract>
<para>
The <citetitle pubwork="book">Deployment Guide</citetitle> documents relevant information regarding the deployment, configuration and administration of &MAJOROSVER;. It is oriented towards system administrators with a basic understanding of the system.
diff --git a/en-US/NetworkManager.xml b/en-US/NetworkManager.xml
index fd36450..8a1ffe3 100644
--- a/en-US/NetworkManager.xml
+++ b/en-US/NetworkManager.xml
@@ -172,7 +172,7 @@ NetworkManager (pid 1527) is running...
</filename> interface configuration files), user connection settings are stored in the GConf configuration database and the GNOME keyring, and are only available during login sessions for the user who created them. Thus, logging out of the desktop session causes user-specific connections to become unavailable.</para>
<note
id="note-Tip-Increase_security_by_making_VPN_connections_user-specific">
- <title>Tip: Increase security by making VPN connections user-specific</title>
+ <title>Increase security by making VPN connections user-specific</title>
<para>Because <application>NetworkManager</application> uses the GConf and GNOME keyring applications to store user connection settings, and because these settings are specific to your desktop session, it is highly recommended to configure your personal VPN connections as user connections. If you do so, other non-root users on the system cannot view or access these connections in any way.</para>
</note>
<para>System connections, on the other hand, become available at boot time and can be used by other users on the system without first logging in to a desktop session.</para>
diff --git a/en-US/Network_Interfaces.xml b/en-US/Network_Interfaces.xml
index bc19662..889cf35 100644
--- a/en-US/Network_Interfaces.xml
+++ b/en-US/Network_Interfaces.xml
@@ -486,7 +486,7 @@ USERCTL=no
<screen>alias bond<replaceable><N></replaceable> bonding</screen>
<para>Replace <replaceable><N></replaceable> with the interface number, such as <command>0</command>. For each configured channel bonding interface, there must be a corresponding entry in your new <filename>/etc/modprobe.d/<replaceable><bonding></replaceable>.conf</filename> file.</para>
<important>
- <title>Important: put all bonding module parameters in ifcfg-bondN files</title>
+ <title>Put all bonding module parameters in ifcfg-bondN files</title>
<para>Parameters for the bonding kernel module must be specified as a space-separated list in the <parameter
class="option">BONDING_OPTS="<replaceable><bonding parameters></replaceable>"</parameter> directive in the ifcfg-bond<replaceable><N></replaceable> interface file. Do <emphasis>not</emphasis> specify options for the bonding device in <filename>/etc/modprobe.d/<replaceable><bonding></replaceable>.conf</filename>, or in the deprecated <filename>/etc/modprobe.conf</filename> file. For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, refer to <xref
linkend="sec-Using_Channel_Bonding"/>.</para>
diff --git a/en-US/PackageKit.xml b/en-US/PackageKit.xml
index ef1343b..5d0c9b3 100644
--- a/en-US/PackageKit.xml
+++ b/en-US/PackageKit.xml
@@ -208,7 +208,7 @@
<para>Note that it is not possible to add or remove <application>Yum</application> repositories through <application>PackageKit</application>.</para>
<note
id="note-Showing_Source_RPM_and_Test_Repositories">
- <title>Showing Source RPM, Test and Debuginfo Repositories</title>
+ <title>Showing source RPM, test and debuginfo repositories</title>
<para>Checking the box at the bottom of the <guilabel>Software Sources</guilabel> window causes <application>PackageKit</application> to display source RPM, testing and debuginfo repositories as well. This box is unchecked by default.</para>
</note>
<para>After enabling and/or disabling the correct <application>Yum</application> repositories, ensure that you have the latest list of available packages. Click on <menuchoice><guimenu>System</guimenu>
@@ -381,7 +381,7 @@
</indexterm> filters out all older versions of the same package from the list of results, which is generally what we want.</para>
<important
id="important-Using_the_Only_newest_items_filter">
- <title>Important: Using the Only Newest Packages filter</title>
+ <title>Using the Only Newest Packages filter</title>
<para>Checking <guimenuitem>Only Newest Packages</guimenuitem> filters out all but the most recent version of any package from the results list. This filter is often combined with the <guimenuitem>Only Available</guimenuitem> filter to search for the latest available versions of new (not installed) packages.</para>
</important>
</listitem>
@@ -454,7 +454,7 @@
</menuchoice>, we search for <application>htop</application> again and uncheck it. The program did not install any dependencies of its own; if it had, those would be automatically removed as well, as long as they were not also dependencies of any other packages still installed on our system.</para>
<warning
id="warning-PackageKit-Removing_a_Package_Without_Removing_Packages_Depending_on_It">
- <title>Warning: Removing a Package when Other Packages Depend On It</title>
+ <title>Removing a package when other packages depend on it</title>
<para>Although <application>PackageKit</application> automatically resolves dependencies during package installation and removal, it is unable to remove a package without also removing packages which depend on it. This type of operation can only be performed by <application>RPM</application>, is not advised, and can potentially leave your system in a non-functioning state or cause applications to misbehave and/or crash.</para>
</warning>
<figure
@@ -558,7 +558,7 @@
<table
id="table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands"
frame="all">
- <title>PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands</title>
+ <title>PackageKit GUI windows, menu locations, and shell prompt commands</title>
<tgroup
cols="4"
align="left"
More information about the docs-commits
mailing list