Applied Bill Maltby's grammar patch. Changed $LFS to LFS where appropriate. Internal XML cleanup: removed double spacing where appropriate.

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

1 files changed, 11 insertions, 11 deletions

diff --git a/chapter02/askforhelp.xml b/chapter02/askforhelp.xml
index 6fb4becec..8cbc00f31 100644
--- a/chapter02/askforhelp.xml
+++ b/chapter02/askforhelp.xml
@@ -24,7 +24,7 @@ essential things to include in your request are:</para>
 </itemizedlist>
 
 <para>(Note that saying that you've deviated from the book doesn't mean
-that we won't help you.  After all, LFS is about choice.  It'll just
+that we won't help you. After all, LFS is about choice. It'll just
 help us to see other possible causes of your problem.)</para>
 
 </sect2>
@@ -45,17 +45,17 @@ Include those relevant lines if you decide to ask for help.</para>
 
 <para>To help us find the cause of the problem, both screen output and
 the contents of various files are useful. The screen output from both
-the ./configure script and the make run can be useful.  Don't blindly
+the ./configure script and the make run can be useful. Don't blindly
 include the whole thing but on the other hand, don't include too little.
 As an example, here is some screen output from make:</para>
 
-<para><screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\" 
--DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\" 
--DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.   
+<para><screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
+-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\"
+-DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
 -g -O2 -c getopt1.c
-gcc  -g -O2 -static -o make  ar.o arscan.o commands.o dir.o expand.o file.o 
-function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o 
-signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o    
+gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o
+function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o
+signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o
 -lutil job.o: In function `load_too_high':
 /lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg'
 collect2: ld returned 1 exit status
@@ -66,16 +66,16 @@ make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
 make: *** [all-recursive-am] Error 2</screen></para>
 
 <para>In this case, many people just include the bottom section where it
-says <screen>make [2]: *** [make] Error 1</screen> and onwards.  This
+says <screen>make [2]: *** [make] Error 1</screen> and onwards. This
 isn't enough for us to diagnose the problem because it only tells us
 that <emphasis>something</emphasis> went wrong, not
-<emphasis>what</emphasis> went wrong.  The whole section, as
+<emphasis>what</emphasis> went wrong. The whole section, as
 in the example above, is what should be included to be helpful, because it
 includes the command that was executed and the command's error
 message(s).</para>
 
 <para>An excellent article on asking for help on the Internet in general
-has been written by Eric S. Raymond.  It is available online at <ulink
+has been written by Eric S. Raymond. It is available online at <ulink
 url="http://www.tuxedo.org/~esr/faqs/smart-questions.html"/>.
 Read and follow the hints in that document and you are much more likely
 to get a response to start with and also to get the help you actually