From b240ee6f1bff43c38e5943b1047b00ea2c13b13b Mon Sep 17 00:00:00 2001
From: George Boudreau <georgeb@linuxfromscratch.org>
Date: Thu, 4 May 2006 22:23:22 +0000
Subject: [PATCH] more README work and corrected a spelling error

---
 README                  | 75 ++++++++++++++++++++++++++---------------
 common/common-functions |  2 +-
 2 files changed, 49 insertions(+), 28 deletions(-)

diff --git a/README b/README
index 83c1b3b..1a77a99 100644
--- a/README
+++ b/README
@@ -37,44 +37,65 @@ $Id$
      The term <symlink> refers to the 1 of 4 package symlinks, lfs,hlfs,clfs,blfs.
      Replace <symlink> with your choice of packages; i.e.: ./lfs
 
-     ./<symlink>
+     ./<symlink>		eg: ./lfs or ./hlfs
      Create a makefile based on the settings found in the config files.
      You must enter the build partition/jhalfs directory and manually run <make>
 
-     ./<symlink> -G
+     ./<symlink> -G		eg: ./lfs -G
      Download the packages and patches necessary to build <symlink>
 
-     ./<symlink> -G -M
+     ./<symlink> -G -M		eg: ./lfs -G -M
      Download the packages, create and automatically run the Makefile
 
-     ./<symlink> --help  will give you a context sensitive list of command
-                         line switches.
+     ./<symlink> --help		eg: ./lfs --help
+     will give you a context sensitive list of command line switches.
 
 5. LAYOUT::
 
-        blfs --+  /BLFS config ---+             /common/config
-               |       master.sh -+                    /common_functions
-               |       xxxx.xsl  -+                    /makefile_functions
-               |                                       /func_check_versions.sh
-        clfs --+  /CLFS config ---+                    /func_validate_configs.sh
-               |       master.sh -+
-               |       xxxx.xsl  -+
-               |
-               +--------------------- master.sh --------------->>>
-               +--README
-               |
-        hlfs --+  /HLFS config ---+
-               |       master.sh -+
-               |       xxxx.xsl  -+
-               |
-        lfs  --+  /LFS  config ---+
-                       master.sh -+
-                       xxxx.xsl  -+
+        /BLFS/config
+             /master.sh
+             /xxxx.xsl
 
+        /CLFS/config
+             /master.sh
+             /xxxx.xsl
+	      
+        /HLFS/config
+             /master.sh
+             /xxxx.xsl
 
+        /LFS/config
+            / master.sh
+            /xxxx.xsl
+
+        /common/config
+               /common_functions
+               /makefile_functions
+               /func_check_versions.sh
+               /func_validate_configs.sh
+
+        /contrib/jhalfs-paco.patch
+
+	/extras/do_copy_files
+               /do_ica_prep
+               /do_ica_work
+               /farce
+               /filelist
+
+         README
+	 README.PACO
+	 TODO
+	 
+	 ./blfs  ---+
+	 ./clfs  ---|
+	            +---> master.sh
+	 ./hlfs  ---|
+	 ./lfs   ---+
+	 
+	 
 6. FAQ::
     Q. "It doesn't work"
-    A. Yes it does..
+    A. Yes it does, try ./lfs --help
     
     Q. "How do I specify the build location"
     A. The original LFS document worked against the well know location /mnt/lfs.
@@ -85,9 +106,9 @@ $Id$
        The layout below $BUILDDIR is as follows.
        $BUILDDIR/
             jhalfs      (makefile,cmd scripts,logs..etc)
-	    sources     (where packages reside
-	    temptools   (temporary bootstrap system
-	    cross-tools (CLFS only)
+	    sources     (where packages reside)
+	    temptools   (temporary bootstrap system)
+	    cross-tools (temporary CLFS only)
 	        ...
 	    FHS dir structure
 	        ...
diff --git a/common/common-functions b/common/common-functions
index 0d9c448..8f9c814 100644
--- a/common/common-functions
+++ b/common/common-functions
@@ -70,7 +70,7 @@ ${BOLD}  -T, --testsuites N ${OFF}
           0 = none
           1 = only final system Glibc, GCC and Binutils testsuites
           2 = all final system testsuites
-          3 = all temporaly tools and final system testsuites
+          3 = all temporary tools and final system testsuites
         In CLFS, 3 is an alias to 2
         In BLFS, 1, 2, and 3 are equivalents and means that the testsuites
         will be run.