Hi,

I've found some obvious mistakes and some nonobvious suspicious points
in the Etch Release Notes.  Could you please find and apply the
attached patch to make improvements and corrections?  I believe that
most of the corrections are good, but if the patch does some
overcorrections, sorry.

Thanks,

-nori
--- release-notes.en.sgml.orig  2007-08-11 06:06:34.000000000 +0900
+++ release-notes.en.sgml       2007-08-12 17:52:31.000000000 +0900
@@ -716,11 +716,11 @@
         later do the same in the installed system.
         To get the installer to load the firmware, one has to have network
         connectivity while the machine is being installed in order to
-        download the firmware-qlogic udeb package with wget, install it
+        download the <package>firmware-qlogic</package> udeb package with 
wget, install it
         with udpkg, and then reload the qla2xxx module.
         After the installation is complete, mount the new root partition,
-        chroot to it, fetch the firmware-qlogic deb package, install it
-        with dpkg, and then run update-initramfs in order to include it
+        chroot to it, fetch the <package>firmware-qlogic</package> deb 
package, install it
+        with dpkg, and then run <prgn>update-initramfs</prgn> in order to 
include it
         in the initial ramdisk image used by the kernel.</p>
 
         <p>Alternatively, install from an older installation CD (where
@@ -1724,7 +1724,7 @@
          </sect2>
 
          <sect2 id="minimal_upgrade_server"><heading>Upgrading a system with 
no X support installed</heading>
-        <p>On a system with no X, no additional aptitude install command 
should be
+        <p>On a system with no X, no additional <tt>aptitude install</tt> 
command should be
         required, and you can move on to the next step.
         </p>
 
@@ -2768,13 +2768,13 @@
          <sect1 id="no-sound"><heading>Sound stops working</heading>
           <p>In rare cases the sound might stop working after the upgrade.
           If this happens, go through the alsa checklist:
-          run alsaconf as root user,
+          run <prgn>alsaconf</prgn> as root user,
           add your user to the <tt/audio/ group,
           use alsamixer and make sure levels are up and it is unmuted,
           make sure arts or esound stopped,
           make sure OSS modules unloaded,
           make sure speakers are on,
-          check whether the command <tt/cat /dev/urandom > /dev/dsp/ works for 
root.</p>
+          check whether the command <tt>cat /dev/urandom > /dev/dsp</tt> works 
for root.</p>
          </sect1>
         </sect>
 
@@ -2973,9 +2973,9 @@
         for more details and other issues.</p>
 
        <p>If you experience problems with X.Org after restarting, it might be
-       also worth to restart the font server <tt>/etc/init.d/xfs restart</tt>.
+       also worth to restart the font server by running <tt>/etc/init.d/xfs 
restart</tt>.
        This happens due to <file>/etc/X11/fs/xfs.options</file> containing a
-       line with no-restart-on-upgrade, but the font paths have changed.</p>
+       line with <tt>no-restart-on-upgrade</tt>, but the font paths have 
changed.</p>
 
       </sect>
 
@@ -3330,7 +3330,7 @@
         needed.</p>
 
         <p>You can submit a bug report using the program
-        <package>reportbug</package> or manually using email.
+        <prgn>reportbug</prgn> or manually using email.
         You can read more about the Bug Tracking System and how to use it by
         reading the reference cards (available at
         <file>/usr/share/doc/debian</file> if you have

Reply via email to