Spell run on README files.

README

@@ -62,7 +62,7 @@ $Id$
      underlying menu code was borrowed from BusyBox and slightly modified for
      our use.
 
-     Help on parameter function is available from the online help. Please
+     Help on parameter function is available from the on-line help. Please
      make use of that feature for additional information not in this file.
 
      Once you have set the parameters you wish and have saved your work the
@@ -84,7 +84,7 @@ $Id$
 6. BLFS_TOOL SUPPORT::
 
      For books that support it, there is an option to install blfs-tool and its
-     dependendencies on the final system. The pre-made build dependencies
+     dependencies on the final system. The pre-made build dependencies
      scripts has been written thinking on a LFS build. For CLFS and HLFS
      builds you may need to adjust that scripts, that are found into the
      common/blfs-tool-deps directory in the jhalfs sources tree.

README.BLFS

@@ -164,7 +164,7 @@ $Id$
    discussed. They are due build procedures and/or BLFS layout particularities
    than we can't handle. In several cases editing the build scripts is mandatory.
    You may need also to insert some build script created by you to resolve
-   unhandled dependencies and/or to remove some script installing the affected
+   unhanded dependencies and/or to remove some script installing the affected
    package by hand.
 
    4.1  BLFS BOOTSCRIPTS

README.CLFS

@@ -10,8 +10,8 @@
 
   .- If you want to install additional custom packages via "Add custom tools
   support" and/or select "Add blfs-tool support", be sure to review and edit
-  their pàckages build scripts to follow the sysroot build method or you will
+  their packages build scripts to follow the sysroot build method or you will
-  end messing your host system. Be very carefull with this.
+  end messing your host system. Be very careful with this.
 
   .- If you install additional packages not using the "Add custom tools support"
   feature (i,e, you will install it manually after finished the Makefile run)

README.CUSTOM

@@ -12,7 +12,7 @@ was easier to add a tool for the user(s) to code their own package needs.
 
   There is two areas that can be customized: how the base system is build
 and what additional configurations and packages requires your hardware to can
-boot and work with. Each one of this areas is handled in a diferent way.
+boot and work with. Each one of this areas is handled in a different way.
 
 
 
@@ -34,7 +34,7 @@ boot and work with. Each one of this areas is handled in a diferent way.
 
   EDITING THE BASE SCRIPTS
 
-  Fisrt step is to generate the build scripts with book defaults. To do that,
+  First step is to generate the build scripts with book defaults. To do that,
 configure jhalfs activating any option you want included, but do not select
 "Run the Makefile" option.
 
@@ -70,7 +70,7 @@ string until have it ordered in the way you want.
   To insert a new package, for example to build Cracklib to can build Shadow
 with Cracklib support, first you should decide before what default package it
 need be installed, in this example before 107-shadow. Then create a new script
-containg the needed commands, using an existing one as template, and name it with
+containing the needed commands, using an existing one as template, and name it with
 the same 3-digits string used for that mentioned default package, but adding
 another 1-digit string. In our example, the new script to build Cracklib just
 before Shadow will be named 107-1-cracklib. This naming schema allow to insert
@@ -91,13 +91,13 @@ based on the changes you made to the build scripts.
        ADDING POST-SYSTEM BUILD CONFIGURATION FILES AND EXTRA PACKAGES
 
   The installation of BLFS packages is handled via blfs-tool and activated
-when you select the appropiate menu option. See README and README.BLFS for
+when you select the appropriate menu option. See README and README.BLFS for
 more info.
 
-  The feature descrbed below was added so users could install remaining
+  The feature described below was added so users could install remaining
-configuration files, build the packages necessary to access the internet
+configuration files, build the packages necessary to access the Internet
 or to support specific hardware, or to install basic utilities that need
-have availables from the beginning, and was not intended to replace the BLFS
+have available from the beginning, and was not intended to replace the BLFS
 install system.
 
   :::NOTICE:::
@@ -134,7 +134,7 @@ configuration file which enables/disables the inclusion of personal scripts.
     and rename it.
 
   2. Populate the variables with the necessary values.
-       Variable function is self explanitory except for the inclusion of the
+       Variable function is self explanatory except for the inclusion of the
        build cmds. If the package you want to include is found in the BLFS
        book then you only need to copy/paste the cmd strings between the xEOFx
        pairs, otherwise you will need to define the build cmds yourself.
@@ -145,7 +145,7 @@ configuration file which enables/disables the inclusion of personal scripts.
   3. As mentioned previously the build order is dictated by the 3 digit number
      in the file name. If a package has dependencies it must be numerically
      larger than the dependency files.
-       ie. The package mc has glib as a dependency and build order is
+       i.e. The package mc has glib as a dependency and build order is
            950-glib
 	   951-mc
 

README.HLFS

@@ -14,4 +14,4 @@ $Id$
  Build failures detected:
 
    -.Several patches are missing or have a bad MD5 sum, thus the tool
-     is unnable to start and test the builds.
+     is unable to start and test the builds.