Re: Things to check in release notes
Why did I think I only had big ones left to do? Here's a proofreading
sweep of old-stuff.dbk.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Index: old-stuff.dbk
===================================================================
--- old-stuff.dbk (revision 9890)
+++ old-stuff.dbk (working copy)
@@ -14,7 +14,7 @@
<section id="old-upgrade">
<title>Upgrading your &oldreleasename; system</title>
<para>
-Basically this is no different than any other upgrade of &oldreleasename; you've been
+Basically this is no different from any other upgrade of &oldreleasename; you've been
doing. The only difference is that you first need to make sure your package
list still contains references to &oldreleasename; as explained in <xref
linkend="old-sources"/>.
@@ -33,7 +33,7 @@
might not be what you want if you are not ready yet for the upgrade. If
you have already run
<literal>apt-get update</literal>, you can still get back without problems
-following the procedure below.
+by following the procedure below.
</para>
<para>
If you have also already installed packages from &releasename;, there probably
@@ -90,11 +90,11 @@
<title>Upgrade legacy locales to UTF-8</title>
<para>
-If your system is localised and is using a locale that is not based on UTF-8
+If your system is localized and is using a locale that is not based on UTF-8
you should strongly consider switching your system over to using UTF-8 locales.
-In the past, there have been bugs<footnote><para>In the GNOME screensaver using
+In the past, there have been bugs<footnote><para>In the GNOME screensaver, using
passwords with non-ASCII characters, pam_ldap support, or even the ability to
-unlock the screen is unreliable when not using UTF8. The GNOME screenreader is
+unlock the screen may be unreliable when not using UTF-8. The GNOME screenreader is
affected by bug <ulink url="http://bugs.debian.org/599197";>#599197</ulink>.
The Nautilus file manager (and all glib-based programs, and likely all Qt-based
programs too) assume that filenames are in UTF-8, while the shell assumes they
@@ -104,17 +104,17 @@
access to the GNOME desktop environment) requires a UTF-8 locale since Squeeze;
under a legacy characterset, it will be unable to read out window information
for desktop elements such as Nautilus/GNOME Panel or the Alt-F1
-menu.</para></footnote> identified that manifest itself
+menu.</para></footnote> identified that manifest themselves
only when using a non-UTF-8 locale. On the desktop, such legacy locales are
-supported through ugly hacks in the libraries internals, and we cannot decently
+supported through ugly hacks in the library internals, and we cannot decently
provide support for users who still use them.
</para>
<para>
To configure your system's locale you can run <command>dpkg-reconfigure
-locales</command>. Ensure you select an UTF-8 locale when you are presented
+locales</command>. Ensure you select a UTF-8 locale when you are presented
with the question asking which locale to use as a default in the system. In
addition, you should review the locale settings of your users and ensure that
-they do not have legacy locales definitions in their configuration
+they do not have legacy locale definitions in their configuration
environment.
</para>
Reply to: