6 files changed, 18 insertions, 19 deletions
diff --git a/en/preparing/bios-setup/s390.xml b/en/preparing/bios-setup/s390.xml
index cd36b61ef..6802ec4b9 100644
--- a/en/preparing/bios-setup/s390.xml
+++ b/en/preparing/bios-setup/s390.xml
@@ -30,13 +30,13 @@ an LPAR if the HMC and this option is available for you.
 Before you actually perform an installation, you have to go over some
 design and preparation steps.  IBM has made documentation available
 about the whole process, e.g. how to prepare an installation medium
-and how actually boot from that medium.  Duplicating that information
+and how actually to boot from that medium.  Duplicating that information
 here is neither possible nor necessary.  However, we will describe
-here which kind of Debian-specific data is needed and where do you
-find them.  Based on both sources of information you have to prepare
-your machine and the installation medium and to perform a boot from
-it.  When you see the welcome message in your client session join this
-document again for the Debian-specific installation steps.
+here which kind of Debian-specific data is needed and where to find it.
+Using both sources of information you have to prepare your machine
+and the installation medium do you can perform a boot from it.
+When you see the welcome message in your client session, return to this
+document to go through the Debian-specific installation steps.
 
 </para>
   </sect2>
diff --git a/en/preparing/nondeb-part/alpha.xml b/en/preparing/nondeb-part/alpha.xml
index 39b6f876d..2743367ba 100644
--- a/en/preparing/nondeb-part/alpha.xml
+++ b/en/preparing/nondeb-part/alpha.xml
@@ -65,7 +65,7 @@ native Windows NT tools (or, more conveniently, you can also
 repartition your disk from the AlphaBIOS setup menu).  Otherwise, it
 is not really necessary to partition from Windows; the Linux
 partitioning tools will generally do a better job.  Note that when you
-run NT, the Disk Administrator may offer you to write a <quote>harmless
+run NT, the Disk Administrator may offer to write a <quote>harmless
 signature</quote> on non-Windows disks if you have any.
 <emphasis>Never</emphasis> let it do that, as this signature will destroy
 the partition information.
diff --git a/en/preparing/nondeb-part/m68k.xml b/en/preparing/nondeb-part/m68k.xml
index 09f677851..37734ca55 100644
--- a/en/preparing/nondeb-part/m68k.xml
+++ b/en/preparing/nondeb-part/m68k.xml
@@ -119,8 +119,8 @@ SC Setup</command> using <command>ResEdit</command> can be found at
 
 For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create
 empty space for the Linux partitions, and complete the partitioning under
-Linux, or use the MacOS version of pdisk available from the MkLinux FTP
-server.
+Linux, or use the MacOS version of pdisk available for download from
+<ulink url="http://homepage.mac.com/alk/downloads/pdisk.sit.hqx">Alsoft</ulink>.
 
 </para>
 </sect2>
diff --git a/en/preparing/nondeb-part/sparc.xml b/en/preparing/nondeb-part/sparc.xml
index 2784f6a2b..2fd599773 100644
--- a/en/preparing/nondeb-part/sparc.xml
+++ b/en/preparing/nondeb-part/sparc.xml
@@ -13,8 +13,8 @@ kernel understands Sun disk labels, so there are no problems there.
 Just make sure you leave room for the Debian root partition within the
 first 1GB area of the boot disk. You can also place the kernel image on a
 UFS partition if that is easier than putting the root partition there.
-SILO supports booting Linux and SunOS from either EXT2 (Linux), UFS
-(SunOS), romfs and iso9660 (CDROM) partitions.
+SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS
+(SunOS), romfs or iso9660 (CDROM) partitions.
 
 </para>
   </sect2>
diff --git a/en/preparing/nondeb-part/x86.xml b/en/preparing/nondeb-part/x86.xml
index 95315fef5..edc98ecb7 100644
--- a/en/preparing/nondeb-part/x86.xml
+++ b/en/preparing/nondeb-part/x86.xml
@@ -13,12 +13,12 @@ job.
 
 </para><para>
 
-But if you have a large IDE disk, and are using neither LBA addressing,
-overlay drivers (sometimes provided by hard disk manufacturers), nor a
+But if you have a large IDE disk, and are not using LBA addressing,
+overlay drivers (sometimes provided by hard disk manufacturers), or a
 new (post 1998) BIOS that supports large disk access extensions, then
 you must locate your Debian boot partition carefully. In this case,
 you will have to put the boot partition into the first 1024 cylinders
-of your hard drive (usually around 524 megabytes, without BIOS
+of your hard disk (usually around 524 megabytes, without BIOS
 translation). This may require that you move an existing FAT or NTFS
 partition.
 
diff --git a/en/preparing/pre-install-bios-setup.xml b/en/preparing/pre-install-bios-setup.xml
index 224b66f8f..8b0304b26 100644
--- a/en/preparing/pre-install-bios-setup.xml
+++ b/en/preparing/pre-install-bios-setup.xml
@@ -138,14 +138,13 @@ this is the case please look at <xref linkend="boot-parms"/>.
    </sect3>
 
    <sect3 arch="powerpc">
-   <title>Display visibility on OldWorld Powermacs</title>
+   <title>Display-visibility on OldWorld Powermacs</title>
 <para>
 
 Some OldWorld Powermacs, most notably those with the <quote>control</quote>
-display driver but possibly others as well, may not produce a colormap with
-reliably results in visible output under Linux when the display is
-configured for more than 256 colors. If you are experiencing such issues
-with your display after rebooting (you can sometimes see data on
+display driver, may not reliable produce a colormap under Linux when the
+display is configured for more than 256 colors. If you are experiencing such
+issues with your display after rebooting (you can sometimes see data on
 the monitor, but on other occasions cannot see anything) or, if the screen
 turns black after booting the installer instead of showing you the user
 interface, try changing your display settings under MacOS to use 256