Update of untranslated English docs

5 files changed, 10 insertions, 10 deletions

diff --git a/nl/appendix/chroot-install.xml b/nl/appendix/chroot-install.xml
index 884ebc92c..51bf826d3 100644
--- a/nl/appendix/chroot-install.xml
+++ b/nl/appendix/chroot-install.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 43724 untranslated -->
+<!-- original version: 43841 untranslated -->
 
  <sect1 id="linux-upgrade">
  <title>Installing &debian; from a Unix/Linux System</title>
@@ -35,7 +35,7 @@ With your current *nix partitioning tools, repartition the hard
 drive as needed, creating at least one filesystem plus swap. You
 need around 350MB of space available for a console only install,
 or about 1GB if you plan to install X (more if you intend to
-install destop environments like GNOME or KDE).
+install desktop environments like GNOME or KDE).
 
 </para><para>
 
diff --git a/nl/appendix/files.xml b/nl/appendix/files.xml
index 6c1458b38..18288c192 100644
--- a/nl/appendix/files.xml
+++ b/nl/appendix/files.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 43737 untranslated -->
+<!-- original version: 43841 untranslated -->
 
 
  <sect1 id="linuxdevices"><title>Linux Devices</title>
@@ -189,7 +189,7 @@ when your mouse only has one button. Just add the following lines to
  Sizes of tasks should be determined by running tasksel with the "new-install"
  option on a system that been fully installed without selecting any tasks. By
  selecting a task together with the "manual selection" option, aptitude will
- be started and show the sizes for the task. Use "cancel panding actions" to
+ be started and show the sizes for the task. Use "cancel pending actions" to
  clear the slate, quit aptitude and repeat for other tasks.
  Space requirements need to be determined from tasksel as tasksel will not
  install recommended packages while selecting a task from aptitude will.
diff --git a/nl/appendix/preseed.xml b/nl/appendix/preseed.xml
index cbe756d94..3b6f499b4 100644
--- a/nl/appendix/preseed.xml
+++ b/nl/appendix/preseed.xml
@@ -1,8 +1,8 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 43658 untranslated -->
+<!-- original version: 43841 untranslated -->
 
 <!--
-Be carefull with the format of this file as it is parsed to generate
+Be careful with the format of this file as it is parsed to generate
 the example preconfiguration file.
 In that file all text between <informalexample> tags that have the
 attribute 'role="example"' set is included, except if a 'condition'
diff --git a/nl/boot-installer/ia64.xml b/nl/boot-installer/ia64.xml
index c42fee170..cca48290e 100644
--- a/nl/boot-installer/ia64.xml
+++ b/nl/boot-installer/ia64.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 43255 untranslated -->
+<!-- original version: 43841 untranslated -->
 
   <sect2 arch="ia64"><title>Booting from a CD-ROM</title>
 
@@ -342,7 +342,7 @@ The only difference is how the installation kernel is loaded.
 The EFI Boot Manager can load and start programs from a server on
 the network.
 Once the installation kernel is loaded and starts, the system install
-will proceed thru the same steps as the CD install with the exception
+will proceed through the same steps as the CD install with the exception
 that the packages of the base install will be loaded from the network
 rather than the CD drive.
 
diff --git a/nl/boot-installer/sparc.xml b/nl/boot-installer/sparc.xml
index f737c2fc7..225d628ee 100644
--- a/nl/boot-installer/sparc.xml
+++ b/nl/boot-installer/sparc.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 43724 untranslated -->
+<!-- original version: 43841 untranslated -->
 
   <sect2 arch="sparc" id="boot-tftp"><title>Booting with TFTP</title>
 
@@ -37,7 +37,7 @@ command which is simply an alias to boot from the SCSI device on ID 6
   <title>Booting from Floppies</title>
 <para>
 
-Floppy images are currently only available for sparc32, but, for techinical
+Floppy images are currently only available for sparc32, but, for technical
 reasons, not for official releases. (The reason is that they can only be
 built as root, which is not supported by our build daemons.)
 Look under <quote>daily built images</quote> on the