[deployment-guide: 112/185] RT#101959: mk text fixes for PackageKit GUI changes, other

[jhradile]

commit 81debaa0487dba00c2edbc8e1bb3faa5f33132e9
Author: Douglas Silas <dhensley(a)redhat.com&gt;
Date:   Mon Mar 7 15:51:52 2011 +0100

    RT#101959: mk text fixes for PackageKit GUI changes, other

 en-US/PackageKit.xml |   62 +++++++++++++++++++++++++-------------------------
 1 files changed, 31 insertions(+), 31 deletions(-)
---
diff --git a/en-US/PackageKit.xml b/en-US/PackageKit.xml
index bb477d2..f0254d9 100644
--- a/en-US/PackageKit.xml
+++ b/en-US/PackageKit.xml
@@ -199,7 +199,7 @@
           <secondary>viewing Yum repositories with PackageKit</secondary>
         </indexterm>software sources. It obtains all packages from enabled software
sources. You can view the list of all <emphasis>configured</emphasis> and
unfiltered (see below)
         <application>Yum</application> repositories by opening 
<guilabel>Add/Remove Software</guilabel> and clicking
<menuchoice><guimenu>System</guimenu>
-          <guimenuitem>Software sources</guimenuitem>
+          <guimenuitem>Software Sources</guimenuitem>
         </menuchoice>. The <guilabel>Software Sources</guilabel> dialog
shows the repository name, as written on the
<computeroutput>name=<replaceable>&lt;My Repository
Name&gt;</replaceable>
         </computeroutput> field of all
[<replaceable>repository</replaceable>] sections in the
<filename>/etc/yum.conf</filename> configuration file, and in all
<filename><replaceable>repository</replaceable>.repo</filename>
files in the <filename>/etc/yum.repos.d/</filename> directory.</para>
       <para>Entries which are checked in the
<guilabel>Enabled</guilabel> column indicate that the corresponding repository
will be used to locate packages to satisfy all update and installation requests (including
dependency resolution). The <guilabel>Enabled</guilabel> column corresponds to
the <computeroutput>enabled=<replaceable>&lt;1 or
0&gt;</replaceable>
@@ -212,7 +212,7 @@
         <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>
-          <guimenuitem>Refresh package lists</guimenuitem>
+          <guimenuitem>Refresh Package Lists</guimenuitem>
         </menuchoice> and <application>PackageKit</application> will
obtain the latest lists of packages from all enabled software sources, i.e.
<application>Yum</application> repositories.</para>
     </section>
     <section
@@ -222,13 +222,13 @@
         <primary>packages</primary>
         <secondary>filtering with PackageKit for packages</secondary>
       </indexterm>
-      <para>Once the software sources have been updated, it is often beneficial to
apply some filters so that <application>PackageKit</application> retrieves the
results of our <guilabel>Find</guilabel> queries faster. This is especially
helpful when performing many package searches. Four of the filters in the
<guimenu>Filters</guimenu> drop-down menu are used to split results by
matching or not matching a single criterion. By default when
<application>PackageKit</application> starts, these filters are all unapplied
(<guibutton>No filter</guibutton>), but once you do filter by one of them,
that filter remains set until you either change it or close
<application>PackageKit</application>.</para>
+      <para>Once the software sources have been updated, it is often beneficial to
apply some filters so that <application>PackageKit</application> retrieves the
results of our <guilabel>Find</guilabel> queries faster. This is especially
helpful when performing many package searches. Four of the filters in the
<guimenu>Filters</guimenu> drop-down menu are used to split results by
matching or not matching a single criterion. By default when
<application>PackageKit</application> starts, these filters are all unapplied
(<guibutton>No Filter</guibutton>), but once you do filter by one of them,
that filter remains set until you either change it or close
<application>PackageKit</application>.</para>
       <para>Because you are usually searching for available packages that are
<emphasis>not</emphasis> installed on the system, click
<menuchoice><guimenu>Filters</guimenu>
           <guimenuitem>Installed</guimenuitem>
-        </menuchoice> and select the <guimenuitem>Only
available</guimenuitem> radio button.
+        </menuchoice> and select the <guimenuitem>Only
Available</guimenuitem> radio button.
       <indexterm><primary>packages</primary>
           <secondary>filtering with PackageKit</secondary>
-          <tertiary>installed</tertiary>
+          <tertiary>Installed</tertiary>
         </indexterm>
         <indexterm>
           <primary>packages</primary>
@@ -237,17 +237,17 @@
         <indexterm>
           <primary>packages</primary>
           <secondary>filtering with PackageKit</secondary>
-          <tertiary>only installed</tertiary>
+          <tertiary>Only Installed</tertiary>
         </indexterm>
         <indexterm>
           <primary>packages</primary>
           <secondary>filtering with PackageKit</secondary>
-          <tertiary>only available</tertiary>
+          <tertiary>Only Available</tertiary>
         </indexterm>
         <indexterm>
           <primary>packages</primary>
           <secondary>filtering with PackageKit</secondary>
-          <tertiary>no filter</tertiary>
+          <tertiary>No Filter</tertiary>
         </indexterm>
       </para>
       <figure
@@ -274,13 +274,13 @@
         <indexterm>
           <primary>packages</primary>
           <secondary>filtering with PackageKit</secondary>
-          <tertiary>only development</tertiary>
+          <tertiary>Only Development</tertiary>
         </indexterm>
         <indexterm>
           <primary>packages</primary>
           <secondary>filtering with PackageKit</secondary>
-          <tertiary>only end user files</tertiary>
-        </indexterm> Also, unless we require development files such as C header
files, we can filter for <guimenu>Only end user files</guimenu> and, in doing
so, filter out all of the
<filename><replaceable>&lt;package_name&gt;</replaceable>-devel</filename>
packages we are not interested in.</para>
+          <tertiary>Only End User Files</tertiary>
+        </indexterm> Also, unless we require development files such as C header
files, we can filter for <guimenu>Only End User Files</guimenu> and, in doing
so, filter out all of the
<filename><replaceable>&lt;package_name&gt;</replaceable>-devel</filename>
packages we are not interested in.</para>
       <figure
         id="fig-Graphical_Package_Management-filters-only_end_user">
         <title>Filtering out development packages from the list of Find
results</title>
@@ -304,11 +304,11 @@
             <indexterm>
               <primary>packages</primary>
               <secondary>filtering with PackageKit</secondary>
-              <tertiary>Graphical</tertiary>
+              <tertiary>Only Graphical</tertiary>
             </indexterm>
           </term>
           <listitem>
-            <para>Narrows the search to either applications which provide a GUI
interface or those that do not (<guibutton>Only text</guibutton>). This filter
is useful when browsing for GUI applications that perform a specific
function.</para>
+            <para>Narrows the search to either applications which provide a GUI
interface (<guibutton>Only Graphical</guibutton>) or those that do not. This
filter is useful when browsing for GUI applications that perform a specific
function.</para>
           </listitem>
         </varlistentry>
         <varlistentry>
@@ -330,15 +330,15 @@
       <variablelist>
         <varlistentry>
           <term>
-            <guimenuitem>Hide subpackages</guimenuitem>
+            <guimenuitem>Hide Subpackages</guimenuitem>
           </term>
           <listitem>
-            <para>Checking the <guimenuitem>Hide
subpackages</guimenuitem>
+            <para>Checking the <guimenuitem>Hide
Subpackages</guimenuitem>
               <indexterm>
                 <primary>packages</primary>
                 <secondary>filtering with PackageKit</secondary>
-                <tertiary>hide subpackages</tertiary>
-              </indexterm> checkbox filters out generally-uninteresting packages
that are typically only dependencies of other packages that we want. For example, checking
<guimenuitem>Hide subpackages</guimenuitem> and searching for
<filename><replaceable>&lt;package&gt;</replaceable>
+                <tertiary>Hide Subpackages</tertiary>
+              </indexterm> checkbox filters out generally-uninteresting packages
that are typically only dependencies of other packages that we want. For example, checking
<guimenuitem>Hide Subpackages</guimenuitem> and searching for
<filename><replaceable>&lt;package&gt;</replaceable>
               </filename> would cause the following related packages to be filtered
out of the <guibutton>Find</guibutton> results (if it exists):</para>
             <itemizedlist>
               <listitem>
@@ -370,31 +370,31 @@
         </varlistentry>
         <varlistentry>
           <term>
-            <guimenuitem>Only newest items</guimenuitem>
+            <guimenuitem>Only Newest Packages</guimenuitem>
           </term>
           <listitem>
-            <para>Checking <guimenuitem>Only newest
items</guimenuitem>
+            <para>Checking <guimenuitem>Only Newest
Packages</guimenuitem>
               <indexterm>
                 <primary>packages</primary>
                 <secondary>filtering with PackageKit</secondary>
-                <tertiary>only newest items</tertiary>
+                <tertiary>Only Newest Packages</tertiary>
               </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 items filter</title>
-              <para>Checking <guimenuitem>Only newest
items</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>
+              <title>Important: 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>
         </varlistentry>
         <varlistentry>
           <term>Only native packages</term>
           <listitem>
-            <para>Checking the <guimenuitem>Only native
packages</guimenuitem>
+            <para>Checking the <guimenuitem>Only Native
Packages</guimenuitem>
               <indexterm>
                 <primary>packages</primary>
                 <secondary>filtering with PackageKit</secondary>
-                <tertiary>only native packages</tertiary>
-              </indexterm> box on a multilib system causes
<application>PackageKit</application> to omit listing results for packages
compiled for the architecture that runs in <emphasis>compatibility
mode</emphasis>. For example, enabling this filter on a 64-bit system with an AMD64
CPU would cause all packages built for the 32-bit x86 CPU architecture not to be shown in
the list of results, even though those packages are able to run on an AMD64 machine.
Packages which are architecture-agnostic (i.e. <firstterm>noarch</firstterm>
packages such as <filename>crontabs-1.10-32.1.el6.noarch.rpm</filename>) are
never filtered out by checking <guimenuitem>Only native
packages</guimenuitem>. This filter has no affect on non-multilib systems, such as
x86 machines.</para>
+                <tertiary>Only Native Packages</tertiary>
+              </indexterm> box on a multilib system causes
<application>PackageKit</application> to omit listing results for packages
compiled for the architecture that runs in <emphasis>compatibility
mode</emphasis>. For example, enabling this filter on a 64-bit system with an AMD64
CPU would cause all packages built for the 32-bit x86 CPU architecture not to be shown in
the list of results, even though those packages are able to run on an AMD64 machine.
Packages which are architecture-agnostic (i.e. <firstterm>noarch</firstterm>
packages such as <filename>crontabs-1.10-32.1.el6.noarch.rpm</filename>) are
never filtered out by checking <guimenuitem>Only Native
Packages</guimenuitem>. This filter has no affect on non-multilib systems, such as
x86 machines.</para>
           </listitem>
         </varlistentry>
       </variablelist>
@@ -410,7 +410,7 @@
         <primary>packages</primary>
         <secondary>removing packages with PackageKit</secondary>
       </indexterm>
-      <para>With the two filters selected, <guibutton>Only
available</guibutton> and <guibutton>Only end user files</guibutton>,
search for the <application>htop</application> interactive process viewer and
highlight the package. You now have access to some very useful information about it,
including: a clickable link to the project homepage; the
<application>Yum</application> package group it is found in, if any; the
license of the package; a pointer to the GNOME menu location from where the application
can be opened, if applicable
(<menuchoice><guimenu>Applications</guimenu>
+      <para>With the two filters selected, <guibutton>Only
Available</guibutton> and <guibutton>Only End User Files</guibutton>,
search for the <application>htop</application> interactive process viewer and
highlight the package. You now have access to some very useful information about it,
including: a clickable link to the project homepage; the
<application>Yum</application> package group it is found in, if any; the
license of the package; a pointer to the GNOME menu location from where the application
can be opened, if applicable
(<menuchoice><guimenu>Applications</guimenu>
           <guimenuitem>System Tools</guimenuitem>
           <guimenuitem>Htop</guimenuitem>
         </menuchoice> in our case); and the size of the package, which is relevant
when we download and install it.</para>
@@ -449,7 +449,7 @@
         </caption>
       </mediaobject>
       <para>
-        <application>htop</application> is nifty, but we decide that
<command>top</command> is good enough for us and we want to uninstall it.
Remembering that we need to change the <guibutton>Only available</guibutton>
filter we recently used to install it to <guibutton>Only installed</guibutton>
in <menuchoice><guimenu>Filters</guimenu>
+        <application>htop</application> is nifty, but we decide that
<command>top</command> is good enough for us and we want to uninstall it.
Remembering that we need to change the <guibutton>Only Available</guibutton>
filter we recently used to install it to <guibutton>Only Installed</guibutton>
in <menuchoice><guimenu>Filters</guimenu>
           <guimenuitem>Installed</guimenuitem>
         </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
@@ -523,7 +523,7 @@
           <primary>PackageKit</primary>
           <secondary>viewing transaction log</secondary>
         </indexterm>that it performs. To view the log, from the
<guilabel>Add/Remove Software</guilabel> window, click
<menuchoice><guimenu>System</guimenu>
-          <guimenuitem>Software log</guimenuitem>
+          <guimenuitem>Software Log</guimenuitem>
         </menuchoice>, or run the <command>gpk-log</command> command at
the shell prompt.</para>
       <para>The <guilabel>Software Log Viewer</guilabel> shows the
<guilabel>Action</guilabel>, such as <replaceable>Updated
System</replaceable> or <replaceable>Installed Packages</replaceable>,
the <guilabel>Date</guilabel> on which that action was performed, the
<guilabel>Username</guilabel> of the user who performed the action, and the
front end <guilabel>Application</guilabel> the user used (such as
<replaceable>Update Icon</replaceable>, or
<replaceable>kpackagekit</replaceable>). The
<guilabel>Details</guilabel> column provides the types of the transactions,
such as <replaceable>Updated</replaceable>,
<replaceable>Installed</replaceable> or
<replaceable>Removed</replaceable>, as well as the list of packages the
transactions were performed on.</para>
       <figure
@@ -537,7 +537,7 @@
               format="PNG" />
           </imageobject>
           <textobject>
-            <para>viewing the log of package management transactions with
packagekit's loftware log viewer window</para>
+            <para>Viewing the log of package management transactions with
PackageKit's Software Log viewer window</para>
           </textobject>
         </mediaobject>
       </figure>
@@ -618,7 +618,7 @@
             <entry>
               <para>From <guilabel>Add/Remove Software</guilabel>:
<menuchoice>
                 <guimenu>System</guimenu>
-                  <guimenuitem>Software sources</guimenuitem>
+                  <guimenuitem>Software Sources</guimenuitem>
                 </menuchoice>
               </para>
             </entry>
@@ -630,7 +630,7 @@
             <entry>
               <para>From <guilabel>Add/Remove Software</guilabel>:
<menuchoice>
                 <guimenu>System</guimenu>
-                  <guimenuitem>Software log</guimenuitem>
+                  <guimenuitem>Software Log</guimenuitem>
                 </menuchoice>
               </para>
             </entry>