More fixes for the release-notes
Hello,
Please find attached some fixes for the release notes.
Greetings,
Fred
Index: en/release-notes.en.sgml
===================================================================
RCS file: /cvs/debian-doc/ddp/manuals.sgml/release-notes/en/release-notes.en.sgml,v
retrieving revision 1.230
diff -u -r1.230 release-notes.en.sgml
--- en/release-notes.en.sgml 2 Apr 2007 17:35:15 -0000 1.230
+++ en/release-notes.en.sgml 3 Apr 2007 01:00:33 -0000
@@ -75,7 +75,7 @@
<item><p>The status of your package database before and after the
upgrade, using the backup procedure described at <ref
- id="backup">.
+ id="backup">.</p></item>
<item><p>Your aptitude logs, available at <file>/var/log/aptitude</file>.</p></item>
@@ -299,7 +299,7 @@
update stable packages that contain information that quickly goes out
of date. Examples are a virus scanner's signatures list or a spam
filter's pattern set. For more information and a list of mirrors,
- please see the archive's <url id="&url-debian-volatile"
+ please see the archive's <url id="&url-debian-volatile;"
name="web page">.</p>
</sect1>
@@ -343,7 +343,7 @@
<p>Note that SELinux support is <em/not/ enabled by default. Information
on setting up and enabling SELinux can be found on the
- <url id="&url-wiki-selinux" name="Debian Wiki">.
+ <url id="&url-wiki-selinux;" name="Debian Wiki">.
</p></item>
<tag>New default inet superdaemon</tag>
@@ -475,7 +475,7 @@
installer. If you are interested in an overview of the detailed
changes since &oldreleasename;, please check the release announcements
for the &releasename; beta and RC releases available from the
- Debian Installer's <url id="&url-installer-news" name="news history">.</p>
+ Debian Installer's <url id="&url-installer-news;" name="news history">.</p>
<sect1 id="inst-changes"><heading>Major changes</heading>
@@ -623,7 +623,7 @@
<tag>Improved system-wide localization</tag>
<item><p>Most of the internationalization and localization tasks that
were previously handled by the <package>localization-config</package> tool are now
- included in the stock &debian; installer or in packages themselves. This
+ included in the stock Debian installer or in packages themselves. This
means that selection of a language will automatically install packages
necessary for that language (dictionaries, documentation, fonts...) in both
standard and desktop environments. Configuration that is no longer
@@ -1289,7 +1289,7 @@
</example></p>
<p>This step will automatically upgrade <package/libc6/ and
- <package/locales/ and will pull in SE linux support libraries
+ <package/locales/ and will pull in SELinux support libraries
(<package/libselinux1/). At this point, some running services will be
restarted, including <prgn/xdm/, <prgn/gdm/ and <prgn/kdm/, as a
consequence local X11 sessions will be disconnected.</p>
@@ -1307,7 +1307,7 @@
# dpkg -l "xlibmesa-glu*" | grep ^ii
</example>
- if you have them installed then you have to install the latest
+ If you have them installed then you have to install the latest
versions from &releasename;. The following command will install both,
if you have only one of them you should remove the other:
@@ -1595,7 +1595,7 @@
<p><em>TRY</em>: In aptitude, upgrade only 'required' 'important'
'standard' packages limit by pressing 'l' and input
!~v(~pextra|~poptional) keep with : for hold this time upgrade by
- pressing 'U" and 'g' (untested but ...) (You can do this in much
+ pressing 'U' and 'g' (untested but ...) (You can do this in much
finer steps.)
-->
</sect1>
@@ -1610,7 +1610,7 @@
is removed from the system (in favor of <package/udev/) when you do a full system
upgrade. If you do not do the kernel upgrade before this your system might
not boot up properly from this point on. Once you have done an upgrade
- to a the 2.6 series kernel in &oldreleasename; you can do a kernel upgrade
+ to a 2.6 series kernel in &oldreleasename; you can do a kernel upgrade
as described in <ref id="upgrade-from-2.6">.</p>
<p>If your system does not rely on <package/hotplug/<footnote>You can
@@ -1836,13 +1836,13 @@
<p>If you are using <package/lilo/ as your bootloader (it is the
default bootloader for some installations of &oldreleasename;) it is strongly recommended
- that you rerun lilo after the upgrade:
+ that you rerun <prgn>lilo</prgn> after the upgrade:
<example>
# /sbin/lilo
</example></p>
<p>Notice this is needed even if you did not upgrade your system's kernel, as
- lilo's second stage will change due to the package upgrade.</p>
+ <prgn>lilo</prgn>'s second stage will change due to the package upgrade.</p>
<p>Also, review the contents of your <file>/etc/kernel-img.conf</file> and
make sure that you have <em>do_bootloader = Yes</em> in it. That way the
@@ -2283,7 +2283,7 @@
already running a 2.6 kernel you will automatically retrieve the
latest kernel when upgrading the rest of the system (see <ref
id="upgrading_other">). Failing to do this will result in an system
- that does not boot,
+ that does not boot.
</p>
]]>
Reply to: