s/a LFS/an LFS/ as per list discussion.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2823 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

chapter01/how.xml

@@ -10,7 +10,7 @@ new system. Ordinarily, the required tools are available by default if you
 selected <quote>development</quote> as one of your installation options when 
 you installed your Linux distribution.</para>
 
-<para>After you have downloaded the packages that make up a LFS system, you 
+<para>After you have downloaded the packages that make up an LFS system, you 
 will create a new Linux native partition and filesystem. This new Linux 
 partition and filesystem is where your new LFS system will be compiled and 
 installed onto.</para>

preface/audience.xml

@@ -13,7 +13,7 @@ install an existing one?". That is a good question and is the impetus for this
 section of the book.</para>
 
 <para>One important reason for LFS's existence is to help people learn how a 
-Linux system works from the inside out. Building a LFS system helps demonstrate 
+Linux system works from the inside out. Building an LFS system helps demonstrate
 to you what makes Linux tick, how things work together and depend on each 
 other. One of the best things that this learning experience provides is the 
 ability to customize Linux to your own tastes and needs.</para>
@@ -28,7 +28,7 @@ programs are installed.</para>
 system. When installing a regular distribution, you are usually forced to 
 install several programs which you are likely never to use. They're just 
 sitting there wasting precious disk space (or worse, CPU cycles). It isn't 
-difficult to build a LFS system less than 100 MB. Does that still sound like a 
+difficult to build an LFS system less than 100 MB. Does that still sound like a
 lot? A few of us have been working on creating a very small embedded LFS 
 system. We successfully built a system that was just enough to run the Apache 
 web server with approximately 8MB of disk space used. Further stripping could