1.1 --- a/docs/overview.txt	Sat Sep 15 21:44:18 2007 +0000
     1.2 +++ b/docs/overview.txt	Wed Feb 20 08:01:12 2008 +0000
     1.3 @@ -10,14 +10,14 @@
     1.4  
     1.5  crosstool-NG aims at building toolchains. Toolchains are an essential component
     1.6  in a software development project. It will compile, assemble and link the code
     1.7 -that is being developped. Some pieces of the toolchain will eventually end up
     1.8 +that is being developed. Some pieces of the toolchain will eventually end up
     1.9  in the resulting binary/ies: static libraries are but an example.
    1.10  
    1.11  So, a toolchain is a very sensitive piece of software, as any bug in one of the
    1.12  components, or a poorly configured component, can lead to execution problems,
    1.13  ranging from poor performance, to applications ending unexpectedly, to
    1.14  mis-behaving software (which more than often is hard to detect), to hardware
    1.15 -damage, or even to human risks (which is more than regretable).
    1.16 +damage, or even to human risks (which is more than regrettable).
    1.17  
    1.18  Toolchains are made of different piece of software, each being quite complex
    1.19  and requiring specially crafted options to build and work seamlessly. This
    1.20 @@ -31,7 +31,7 @@
    1.21      no optimisation for your specific target,
    1.22    - they can be prepared for a specific target and thus are not easy to use,
    1.23      nor optimised for, or even supporting your target,
    1.24 -  - they often are using ageing components (compiler, C library, etc...) not
    1.25 +  - they often are using aging components (compiler, C library, etc...) not
    1.26      supporting special features of your shiny new processor;
    1.27  On the other side, these toolchain offer some advantages:
    1.28    - they are ready to use and quite easy to install and setup,
    1.29 @@ -40,19 +40,19 @@
    1.30  But once you want to get all the juice out of your specific hardware, you will
    1.31  want to build your own toolchain. This is where crosstool-NG comes into play.
    1.32  
    1.33 -There are also a number of tools that builds toolchains for specific needs,
    1.34 -which is not really scalable. Examples are:
    1.35 -  - buildroot (buildroot.uclibc.org) whose main puprpose is to build root file
    1.36 +There are also a number of tools that build toolchains for specific needs,
    1.37 +which are not really scalable. Examples are:
    1.38 +  - buildroot (buildroot.uclibc.org) whose main purpose is to build root file
    1.39      systems, hence the name. But once you have your toolchain with buildroot,
    1.40      part of it is installed in the root-to-be, so if you want to build a whole
    1.41      new root, you either have to save the existing one as a template and
    1.42      restore it later, or restart again from scratch. This is not convenient,
    1.43    - ptxdist (www.pengutronix.de/software/ptxdist), whose purpose is very
    1.44      similar to buildroot,
    1.45 -  - other projects (openembeded.org for example), which is again used to
    1.46 +  - other projects (openembedded.org for example), which is again used to
    1.47      build root file systems.
    1.48  
    1.49 -crosstool-NG is really targetted at building toolchains, and only toolchains.
    1.50 +crosstool-NG is really targeted at building toolchains, and only toolchains.
    1.51  It is then up to you to use it the way you want.
    1.52  
    1.53  ___________
    1.54 @@ -60,16 +60,16 @@
    1.55  History  /
    1.56  ________/
    1.57  
    1.58 -crosstool was first 'conceived' by Dan Kegel, which offered it to the community,
    1.59 +crosstool was first 'conceived' by Dan Kegel, who offered it to the community
    1.60  as a set of scripts, a repository of patches, and some pre-configured, general
    1.61  purpose setup files to be used to configure crosstool. This is available at
    1.62  http://www.kegel.com/crosstool, and the subversion repository is hosted on
    1.63  google at http://code.google.com/p/crosstool/.
    1.64  
    1.65 -At the time of writing, crosstool only supports building with one C library,
    1.66 -namely glibc, and one C compiler, gcc; it is cripled with historical support
    1.67 -for legacy components, and is some kind of a mess to upgrade. Also, submited
    1.68 -patches take a loooong time before they are integrated mainline.
    1.69 +At the time of writing, crosstool supports building with only one C library,
    1.70 +namely glibc, and one C compiler, gcc; it is crippled with historical support
    1.71 +for legacy components, and is some kind of a mess to upgrade. Also, submitted
    1.72 +patches take a loooong time before they are integrated into mainline.
    1.73  
    1.74  I once managed to add support for uClibc-based toolchains, but it did not make
    1.75  into mainline, mostly because I don't have time to port the patch forward to
    1.76 @@ -97,7 +97,7 @@
    1.77   - or only build it and run from the source directory.
    1.78  
    1.79  The former should be used if you got crosstool-NG from a packaged tarball, see
    1.80 -"Install method", below, while the latter is most usefull for developpers that
    1.81 +"Install method", below, while the latter is most useful for developpers that
    1.82  checked the code out from SVN, and want to submit patches, see "The Hacker's
    1.83  way", below.
    1.84  
    1.85 @@ -261,7 +261,7 @@
    1.86    man 1 ct-ng
    1.87  
    1.88  
    1.89 -Stoping and restarting a build |
    1.90 +Stopping and restarting a build |
    1.91  -------------------------------*
    1.92  
    1.93  If you want to stop the build after a step you are debugging, you can pass the