yum-software-management yum-software-management-en.xml,1.4,1.5

[Paul W. Frields (pfrields)]

Author: pfrields

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

Modified Files:
	yum-software-management-en.xml 
Log Message:
Use XMLism for empty tags, not SGML


Index: yum-software-management-en.xml
===================================================================
RCS file: /cvs/docs/yum-software-management/yum-software-management-en.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- yum-software-management-en.xml	14 Jun 2005 22:45:38 -0000	1.4
+++ yum-software-management-en.xml	22 Jun 2005 00:07:32 -0000	1.5
@@ -67,17 +67,17 @@
      </para>
      <para>
       If you are a new user, read the <xref
-      linkend="sn-software-management-concepts"></xref> before using
+      linkend="sn-software-management-concepts"/> before using
       <command>yum</command> for the first time.
      </para>
      <para>
-      Experienced Linux users should start with <xref linkend="sn-authorizing-package-sources"></xref>.
+      Experienced Linux users should start with <xref linkend="sn-authorizing-package-sources"/>.
      </para>
      <para>
       Anyone with several &FED; systems on a network may benefit from setting
       up their own software repositories to manage the process of installation and
       updates.  The details of maintaining your own repositories are explained
-      in <xref linkend="sn-managing-repositories"></xref>.
+      in <xref linkend="sn-managing-repositories"/>.
     </para>
     <para>
 	 Most of the examples use the package <filename>tsclient</filename>,
@@ -303,7 +303,7 @@
       <note>
 	<title>Other Naming Conventions are Supported</title>
          <para>
-	   Refer to <xref linkend="sn-searching-packages-byname"></xref> for
+	   Refer to <xref linkend="sn-searching-packages-byname"/> for
 	   more information on specifying packages by name or type.
          </para>
       </note>
@@ -643,7 +643,7 @@
      <note>
       <title>Search Criteria</title>
 	<para>
-	See <xref linkend="sn-searching-packages"></xref> for details of search
+	See <xref linkend="sn-searching-packages"/> for details of search
 	criteria.  The management options of <command>yum</command>
 	<emphasis>are</emphasis> case-sensitive.
       </para>
@@ -664,7 +664,7 @@
         one sub-directory per repository.  You may copy these cached packages
         and use them elsewhere if you wish.  Removing a package from your system
         does not delete the downloaded RPM from the cache.  See <xref
-        linkend="sn-yum-clearance"></xref> for details on purging the caches.
+        linkend="sn-yum-clearance"/> for details on purging the caches.
         </para>
     </tip>
 
@@ -815,7 +815,7 @@
     </para>
     <para>
 	You must also add the public key of the package provider, if you have
-	not not already imported it.  The process is described in <xref linkend="sn-authorizing-package-sources"></xref>.
+	not not already imported it.  The process is described in <xref linkend="sn-authorizing-package-sources"/>.
     </para>
     <note>
      <title>Repositories and <application>Up2date</application> Channels</title>
@@ -1050,7 +1050,7 @@
     </para>
     <para>
 	Creating a definition file is described in <xref
-	linkend="sn-writing-repodefs"></xref>.  Packaging building is beyond the
+	linkend="sn-writing-repodefs"/>.  Packaging building is beyond the
 	scope of this document.
      </para>
       <tip>