rev 4081 - trunk/packages/kdebase/debian

[Christopher Martin]

Author: chrsmrtn
Date: 2006-07-07 15:05:29 +0000 (Fri, 07 Jul 2006)
New Revision: 4081

Modified:
   trunk/packages/kdebase/debian/NEWS
Log:
Minor edits.


Modified: trunk/packages/kdebase/debian/NEWS
===================================================================
--- trunk/packages/kdebase/debian/NEWS	2006-07-07 15:00:35 UTC (rev 4080)
+++ trunk/packages/kdebase/debian/NEWS	2006-07-07 15:05:29 UTC (rev 4081)
@@ -2,9 +2,9 @@
 
   *** Changes to KDM conffiles:
 
-  * Users upgrading KDM to a 3.4.x, from 3.3.x, will find that KDM no longer
-    uses the /etc/kde3/kdm/Xservers file, if /etc/kde3/kdm/kdmrc has been
-    updated to the version shipped with KDM 3.4.x. The package upgrade scripts
+  * Users upgrading KDM from 3.3.x, will find that KDM no longer uses the
+    /etc/kde3/kdm/Xservers file, if /etc/kde3/kdm/kdmrc was updated to
+    the version shipped with KDM 3.4.x. The package upgrade scripts
     will not remove Xservers even if kdmrc has been upgraded, if they detect
     local modifications. This should allow administrators to merge their
     Xservers changes into kdmrc before themselves removing Xservers. The new
@@ -12,14 +12,13 @@
     should be placed.
 
   * Irrespective of the removal of the Xservers file, we highly recommend that
-    all administrators accept the installation of the updated 3.4.x kdmrc file
+    all administrators accept the installation of the updated kdmrc file
     during the package upgrade. Many important changes to KDM's defaults have
     been made, and KDM is exceedingly bad at handling anything but the latest
     kdmrc format, so the nuissance of re-customizing KDM will likely prove
     less than the nuissance of dealing with a KDM that isn't working properly.
-    If you have already upgraded KDM to a 3.4.x package without accepting the
-    new kdmrc, purging and reinstalling the package should achieve the desired
-    effect.
+    If you have already upgraded KDM package without accepting the new kdmrc,
+    purging and reinstalling the package should achieve the desired result.
 
   *** Changes to user login script handling: