4 files changed, 10 insertions, 9 deletions
diff --git a/en/preparing/bios-setup/i386.xml b/en/preparing/bios-setup/i386.xml
index ed548ce9f..e5e884612 100644
--- a/en/preparing/bios-setup/i386.xml
+++ b/en/preparing/bios-setup/i386.xml
@@ -124,10 +124,10 @@ controller.
 
 </para><para>
 
-Other popular option is to boot from a USB storage (also called USB
-memory stick or USB key).  Some BIOSes can boot USB storage directly,
-and some cannot. You may need to configure your BIOS to boot from
-a <quote>Removable drive</quote> or even a <quote>USB-ZIP</quote> to
+Another popular option is to boot from a USB storage device (also called
+a USB memory stick or USB key). Some BIOSes can boot directly from a USB
+storage device, but some cannot. You may need to configure your BIOS to boot
+from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to
 get it to boot from the USB device.
 
 </para><para>
diff --git a/en/preparing/bios-setup/powerpc.xml b/en/preparing/bios-setup/powerpc.xml
index b676a03bd..6011e6900 100644
--- a/en/preparing/bios-setup/powerpc.xml
+++ b/en/preparing/bios-setup/powerpc.xml
@@ -46,7 +46,8 @@ patch is included in the <application>System Disk 2.3.1</application>
 utility, available from Apple at
 <ulink url="ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin"></ulink>.
 After unpacking the utility in MacOS, and launching it, select the
-Save button to have the firmware patches installed to nvram.
+<guibutton>Save button</guibutton> to have the firmware patches
+installed to nvram.
 
 </para>
   </sect2>
diff --git a/en/preparing/bios-setup/s390.xml b/en/preparing/bios-setup/s390.xml
index 7da892259..cd36b61ef 100644
--- a/en/preparing/bios-setup/s390.xml
+++ b/en/preparing/bios-setup/s390.xml
@@ -94,7 +94,7 @@ FTP.
 </para><para>
 
 The installation server needs to copy the exact directory structure
-from any &debian; mirror but of only the s390 and
+from any &debian; mirror, but only the s390 and
 architecture-independent files are required. You can also copy the
 contents of all installation CDs into such a directory tree.
 
diff --git a/en/preparing/bios-setup/sparc.xml b/en/preparing/bios-setup/sparc.xml
index 6b222a142..e0dfe0bbf 100644
--- a/en/preparing/bios-setup/sparc.xml
+++ b/en/preparing/bios-setup/sparc.xml
@@ -10,7 +10,7 @@ OpenBoot provides the basic functions needed to boot the &arch-title;
 architecture.  This is rather similar in function to the BIOS in the
 x86 architecture, although much nicer.  The Sun boot PROMs have a
 built-in forth interpreter which lets you do quite a number of things
-with your machine, such as diagnostics, simple scripts, etc.
+with your machine, such as diagnostics and simple scripts.
 
 </para><para>
 
@@ -41,7 +41,7 @@ emulator if you are using a different program.
 
 You can use OpenBoot to boot from specific devices, and also to change
 your default boot device.  However, you need to know some details
-about how OpenBoot names devices; it's much different from Linux
+about how OpenBoot names devices; it's considerably different from Linux
 device naming, described in <xref linkend="device-names"/>.
 Also, the command will vary a bit, depending on what version of
 OpenBoot you have.  More information about OpenBoot can be found in
@@ -49,7 +49,7 @@ the <ulink url="&url-openboot;">Sun OpenBoot Reference</ulink>.
 
 </para><para>
 
-Typically, with newer revisions, you can use OpenBoot device such as
+Typically, with newer revisions, you can use OpenBoot devices such as
 <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>,
 <quote>disk</quote>, or <quote>disk2</quote>.  These have the obvious
 meanings; the <quote>net</quote> device is for booting from the network.