Update of original English documents

1 files changed, 13 insertions, 13 deletions

diff --git a/nl/boot-installer/trouble.xml b/nl/boot-installer/trouble.xml
index d5cf3b1cc..312c6132b 100644
--- a/nl/boot-installer/trouble.xml
+++ b/nl/boot-installer/trouble.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 42461 untranslated -->
+<!-- original version: 42532 untranslated -->
 
  <sect1 id="boot-troubleshooting">
  <title>Troubleshooting the Installation Process</title>
@@ -35,8 +35,8 @@ it is not dirty.
 <listitem><para>
 
 If the installer fails to recognize a CD-ROM, try just running the option
-<guimenu> <guimenuitem>Detect and mount CD-ROM</guimenuitem></guimenu> a
-second time. Some DMA related isses with older CD-ROM drives are known to
+<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice>
+a second time. Some DMA related isses with older CD-ROM drives are known to
 be resolved in this way.
 
 </para></listitem>
@@ -231,32 +231,32 @@ The boot floppy is the floppy with the worst problems, because it
 is read by the hardware directly, before Linux boots.  Often, the
 hardware doesn't read as reliably as the Linux floppy disk driver, and
 may just stop without printing an error message if it reads incorrect
-data. There can also be failures in the Driver Floppies most of which
+data. There can also be failures in the driver floppies, most of which
 indicate themselves with a flood of messages about disk I/O errors.
 
 </para><para>
 
-If you are having the installation stall at a particular floppy, the
-first thing you should write it to a <emphasis>different</emphasis>
-floppy. Simply reformatting the old
+If you are having the installation stall at a particular floppy, the first
+thing you should do is write the image to a <emphasis>different</emphasis>
+floppy and see if that solves the problem. Simply reformatting the old
 floppy may not be sufficient, even if it appears that the floppy was
 reformatted and written with no errors. It is sometimes useful to try
 writing the floppy on a different system.
 
 </para><para>
 
-Normally you should not have download a floppy image again, but if you
-are experiencing problems it is always useful to verify that the images
-were downloaded correctly by verifying their md5sums.
-
-</para><para>
-
 One user reports he had to write the images to floppy
 <emphasis>three</emphasis> times before one worked, and then
 everything was fine with the third floppy.
 
 </para><para>
 
+Normally you should not have to download a floppy image again, but if you
+are experiencing problems it is always useful to verify that the images
+were downloaded correctly by verifying their md5sums.
+
+</para><para>
+
 Other users have reported that simply rebooting a few times with the
 same floppy in the floppy drive can lead to a successful boot. This is
 all due to buggy hardware or firmware floppy drivers.