One last sweep of the whole lot to make sure I've caught all the
recent changes.
By the way, what's all this (issues.dbk section id="consolekit") about
consolekit requiring one of gdm3, kdm, or lightdm? I'm launching my X
session from startx like I've always done (after all, why would I want
a display manager on a single-user PC?), without doing anything fancy
like unsetting XDG_SESSION_COOKIE or customising /etc/X11/Xsession.d/*
scripts. I don't see any sign of consolekit issues (ck-list-sessions
tells me "is-local = TRUE"). So why are the release-notes advising me
to stop using startx?
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
Index: upgrading.dbk
===================================================================
--- upgrading.dbk (revision 9980)
+++ upgrading.dbk (working copy)
@@ -469,7 +469,7 @@
</para>
<programlisting>deb &url-debian-mirror-eg;/debian &releasename; main contrib</programlisting>
<para>
-Note that the `<literal>dists</literal>' is added implicitly, and the arguments
+Note that the <quote><literal>dists</literal></quote> is added implicitly, and the arguments
after the release name are used to expand the path into multiple directories.
</para>
<para>
@@ -500,7 +500,7 @@
</para>
<programlisting>deb file:/var/ftp/debian &releasename; main contrib</programlisting>
<para>
-Note that the `<literal>dists</literal>' is added implicitly, and the arguments
+Note that the <quote><literal>dists</literal></quote> is added implicitly, and the arguments
after the release name are used to expand the path into multiple directories.
</para>
<para>
@@ -973,7 +973,7 @@
<para>
Debian &release; now features multiarch, which allows one to install packages
from different architectures on the same system. The
-<systemitem role="package">ia32-libs</systemitem> is now a transitional
+<systemitem role="package">ia32-libs</systemitem> package is now a transitional
package to make use of this new functionality. If you have
<systemitem role="package">ia32-libs</systemitem> installed, you need to
enable multiarch before upgrading this package. Otherwise APT will output
@@ -1099,7 +1099,7 @@
or re-configuration of several packages. When you are asked if any file in
the <filename>/etc/init.d</filename> directory, or the
<filename>/etc/manpath.config</filename> file should be replaced by the
-package maintainer's version, it's usually necessary to answer `yes' to
+package maintainer's version, it's usually necessary to answer <quote>yes</quote> to
ensure system consistency. You can always revert to the old versions, since
they will be saved with a <literal>.dpkg-old</literal> extension.
</para>
@@ -1209,7 +1209,7 @@
are exited.
</para>
<para>
-See also <filename>/usr/share/doc/screen/NEWS.Debian.gz</filename> of
+See also <filename>/usr/share/doc/screen/NEWS.Debian.gz</filename> in
wheezy's <systemitem role="package">screen</systemitem> package.
</para>
</section>
Index: issues.dbk
===================================================================
--- issues.dbk (revision 9980)
+++ issues.dbk (working copy)
@@ -123,9 +123,9 @@
Plasma Workspace.
</para>
<para>
- Should you be using the deprecated <command>knetworkmanager</command>
+ If you are using the deprecated <command>knetworkmanager</command>
standalone application, you should be prepared to do some manual
- configuration afterwards. On upgrade, you might need to manually add
+ configuration after the upgrade. You might need to manually add
plasma-widget-networkmanagement to your panel or desktop.
</para>
<para>
@@ -368,17 +368,17 @@
trying to build or use external compilers might need to be aware of this.
</para>
<para arch="ia64">
- Some hints to workaround these issues can be found in
+ Some hints to work around these issues can be found in
<filename>/usr/share/doc/libc6.1/NEWS.Debian.gz</filename> and in bugreport
<ulink url="&url-bts;637232">#637232</ulink>.
</para>
<para arch="kfreebsd-amd64;kfreebsd-i386">
- Some hints to workaround these issues can be found in
+ Some hints to work around these issues can be found in
<filename>/usr/share/doc/libc0.1/NEWS.Debian.gz</filename> and in bugreport
<ulink url="&url-bts;637232">#637232</ulink>.
</para>
<para arch="amd64;armel;armhf;i386;mips;mipsel;powerpc;s390;s390x;sparc">
- Some hints to workaround these issues can be found in
+ Some hints to work around these issues can be found in
<filename>/usr/share/doc/libc6/NEWS.Debian.gz</filename> and in bugreport
<ulink url="&url-bts;637232">#637232</ulink>.
</para>
