yum-software-management yum-software-management-en.xml,1.39,1.40

[Stuart Ellis (elliss)]

Author: elliss

Update of /cvs/docs/yum-software-management
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv5297

Modified Files:
	yum-software-management-en.xml 
Log Message:

- Amended title to be less clunky.



Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- yum-software-management-en.xml	13 Aug 2005 21:47:19 -0000	1.39
+++ yum-software-management-en.xml	16 Aug 2005 22:37:02 -0000	1.40
@@ -17,7 +17,7 @@
 
 <article id="yum-software-management" lang="en">
   <articleinfo>
-    <title>Software Management with <command>yum</command></title>
+    <title>Managing Software with <command>yum</command></title>
     <copyright>
       <year>2005</year>
       <holder>Stuart Ellis</holder>
@@ -61,14 +61,14 @@
         </revdescription>
       </revision>
       <revision>
-	<revnumber>1.0</revnumber>
-	<date>2005-08-13</date>
-	<authorinitials>PaulWFrields</authorinitials>
-	<revdescription>
-	  <para>
-	    Publish to official project page.
-	  </para>
-	</revdescription>
+        <revnumber>1.0</revnumber>
+        <date>2005-08-13</date>
+        <authorinitials>PaulWFrields</authorinitials>
+        <revdescription>
+          <para>
+            Publish to official project page.
+          </para>
+        </revdescription>
       </revision>
     </revhistory>
   </articleinfo>
@@ -453,11 +453,11 @@
 
       <para>
         For clarity, <command>yum</command> lists packages in the format
-	<filename>name.architecture</filename>. Repositories also
-	commonly store packages in separate directories by architecture.
-	In each case, the hardware architecture specified for the
-	package is the <emphasis>minimum</emphasis> type of machine
-	required to use the package.
+        <filename>name.architecture</filename>. Repositories also
+        commonly store packages in separate directories by architecture.
+        In each case, the hardware architecture specified for the
+        package is the <emphasis>minimum</emphasis> type of machine
+        required to use the package.
       </para>
 
       <variablelist>
@@ -910,7 +910,7 @@
 
         <para>
           The removal process leaves user data in place but may remove
-          configuration files in some cases.  If a package removal does
+          configuration files in some cases. If a package removal does
           not include the configuration file, and you reinstall the
           package later, it may reuse the old configuration file.
         </para>
@@ -1534,8 +1534,8 @@
 
       <para>
         Ensure that the public key for the package source has been
-	imported before you install a package without a repository.
-	Refer to <xref linkend="sn-authorizing-package-sources"/>.
+        imported before you install a package without a repository.
+        Refer to <xref linkend="sn-authorizing-package-sources"/>.
       </para>
     </important>