Index: postlfs/config/bootdisk.xml
===================================================================
--- postlfs/config/bootdisk.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/config/bootdisk.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -25,5 +25,5 @@
 
 <para>
-Now that we have a file mounted and useable, let's prepare it to be 
+Now that we have a file mounted and usable, let's prepare it to be 
 filled with useful material.  Since this is only a rescue floppy we'll 
 only need to set up the minimum directories.</para>
Index: postlfs/config/config.xml
===================================================================
--- postlfs/config/config.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/config/config.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -15,5 +15,5 @@
 subsystems but these are mostly simply pretty frontends to the process
 of editing the file.  The advantage of text-only configuration is that
-you can edit parameters using your favourite text editor, whether that
+you can edit parameters using your favorite text editor, whether that
 be vim, emacs or anything else.</para>
 
Index: postlfs/config/logon.xml
===================================================================
--- postlfs/config/logon.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/config/logon.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -1,5 +1,5 @@
 <sect1 id="postlfs-config-logon">
 <?dbhtml filename="logon.html" dir="postlfs"?>
-<title>/etc/issue (Customising your logon)</title>
+<title>/etc/issue (Customizing your logon)</title>
 
 <para>When you first boot up your new LFS system, the logon screen will
@@ -26,5 +26,5 @@
 alone.</para>
 
-<para>The following escapes are recognised by agetty (the program which
+<para>The following escapes are recognized by agetty (the program which
 usually parses <filename>/etc/issue</filename>).  This information is from
 <userinput>man agetty</userinput> where you can find extra information
Index: postlfs/config/profile.xml
===================================================================
--- postlfs/config/profile.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/config/profile.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -4,5 +4,5 @@
 
 <para>The shell program <filename>/bin/bash</filename> (hereafter
-refered to as just "the shell") uses a collection of startup files to
+referred to as just "the shell") uses a collection of startup files to
 help create an environment to run in.  Each file has a specific use and
 may affect login and interactive environments differently.</para>
@@ -24,5 +24,5 @@
 <filename>~/.bash_profile</filename>, and
 <filename>~/.bashrc</filename>.  The file
-<filename>~/.bash_logout</filename> is not used for an invokation of the
+<filename>~/.bash_logout</filename> is not used for an invocation of the
 shell.  It is read by the shell when a user logouts of the system.  The
 files <filename>/etc/profile</filename> and
@@ -134,5 +134,5 @@
 # by James Robertson &lt;jameswrobertson@earthlink.net&gt;
 
-# Personal envrionment variables and startup programs.
+# Personal environment variables and startup programs.
 
 # Personal aliases and functions should go in ~/.bashrc.  System wide
@@ -162,5 +162,5 @@
 
 # Personal environment variables and startup programs should go in
-# ~/.bash_profile.  System wide environment variables and starup
+# ~/.bash_profile.  System wide environment variables and startup
 # programs are in /etc/profile.  System wide aliases and functions are
 # in /etc/bashrc. 
Index: postlfs/config/vimrc.xml
===================================================================
--- postlfs/config/vimrc.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/config/vimrc.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -47,5 +47,5 @@
 
 <listitem><para><userinput>set bs=2 :</userinput>
-This influences the behaviour of the backspace option.  It is fairly
+This influences the behavior of the backspace option.  It is fairly
 complex so see <userinput>:help 'bs'</userinput> for more 
 details.</para></listitem>
@@ -56,5 +56,5 @@
 
 <listitem><para><userinput>set background=dark :</userinput>
-This tells vim to use colours which look good on a dark 
+This tells vim to use colors which look good on a dark 
 background.</para></listitem>
 
Index: postlfs/security/firewalling/busybox.xml
===================================================================
--- postlfs/security/firewalling/busybox.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/security/firewalling/busybox.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -13,5 +13,5 @@
 setup more complex and your box less secure: You induce the risks of 
 misconfigured services or running a service with an exploitable bug, both risks 
-that a firewall principially should be immune of. See the introduction to 
+that a firewall principally should be immune of. See the introduction to 
 <xref linkend="postlfs-security-fw-masqRouter"/> for some more details.</para>
 
Index: postlfs/security/firewalling/intro.xml
===================================================================
--- postlfs/security/firewalling/intro.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/security/firewalling/intro.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -13,5 +13,5 @@
 to aim no harm, you wouldn't need to do firewalling!  
 In the real world however, daemons may be misconfigured, 
-exploits against essential services are freely availiable, you 
+exploits against essential services are freely available, you 
 may wish to choose which services are accessible by certain machines, 
 you may wish to limit which machines or applications are allowed 
@@ -47,5 +47,5 @@
 <sect3><title><xref linkend="postlfs-security-fw-masqRouter"/></title>
 <para>This is a box placed between the internet and an intranet. 
-To minimize the risk of compromizing the firewall itself it
+To minimize the risk of compromising the firewall itself it
 should generally have only one role, that of protecting the intranet.
 Although not completely riskless, the tasks of doing the routing 
@@ -53,5 +53,5 @@
 of the packets it routes from clients with private IP-addresses onto 
 the internet so that they seem to come from the firewall 
-itself</para></footnote> are commonly considerd harmless.</para></sect3>
+itself</para></footnote> are commonly considered harmless.</para></sect3>
 
 <sect3><title><xref linkend="postlfs-security-fw-busybox"/></title>
Index: postlfs/security/iptables/iptables-desc.xml
===================================================================
--- postlfs/security/iptables/iptables-desc.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/security/iptables/iptables-desc.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -15,5 +15,5 @@
 
 <sect3><title>iptables-save, ~-restore</title>
-<para>to save and to restore your elabourated set of chains and rules.
+<para>to save and to restore your elaborated set of chains and rules.
 Until iptables-1.2.5 they were declared experimental.</para>
 </sect3>
Index: postlfs/security/iptables/iptables-intro.xml
===================================================================
--- postlfs/security/iptables/iptables-intro.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/security/iptables/iptables-intro.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -24,5 +24,5 @@
 is checked (if it is available at <filename>/usr/src/linux</filename> to
 see which features are available.  Support will only be compiled into
-iptables for the features recognised at compile-time.  Applying a kernel
+iptables for the features recognized at compile-time.  Applying a kernel
 patch may result in errors, often because the hooks for the patches
 have changed or because the runme script doesn't recognize that a patch
Index: postlfs/security/shadow/shadow-inst.xml
===================================================================
--- postlfs/security/shadow/shadow-inst.xml	(revision 815fed501edb98f7d8d6d893f40fa29943117779)
+++ postlfs/security/shadow/shadow-inst.xml	(revision 64d97b7c532eb01d7a1399dbb30646d77c9a6b6e)
@@ -1,4 +1,4 @@
 <sect2>
-<title>Reinstallation of shadow to utilize PAM</title>
+<title>Re-installation of shadow to utilize PAM</title>
 
 <para>Download the patch for shadow from <ulink url="&hfile-root;"/></para>
