1.1 --- a/docs/overview.txt	Wed Feb 20 08:01:12 2008 +0000
     1.2 +++ b/docs/overview.txt	Wed Feb 20 22:48:35 2008 +0000
     1.3 @@ -66,24 +66,16 @@
     1.4  http://www.kegel.com/crosstool, and the subversion repository is hosted on
     1.5  google at http://code.google.com/p/crosstool/.
     1.6  
     1.7 -At the time of writing, crosstool supports building with only one C library,
     1.8 -namely glibc, and one C compiler, gcc; it is crippled with historical support
     1.9 -for legacy components, and is some kind of a mess to upgrade. Also, submitted
    1.10 -patches take a loooong time before they are integrated into mainline.
    1.11 -
    1.12  I once managed to add support for uClibc-based toolchains, but it did not make
    1.13 -into mainline, mostly because I don't have time to port the patch forward to
    1.14 +into mainline, mostly because I didn't have time to port the patch forward to
    1.15  the new versions, due in part to the big effort it was taking.
    1.16  
    1.17  So I decided to clean up crosstool in the state it was, re-order the things
    1.18 -in place, and add appropriate support for what I needed, that is uClibc
    1.19 -support. That was a disaster, as inclusion into mainline is slow as hell,
    1.20 -and the changes were so numerous.
    1.21 -
    1.22 -The only option left to me was rewrite crosstool from scratch. I decided to go
    1.23 -this way, and name the new implementation crosstool-NG, standing for crosstool
    1.24 -Next Generation, as many other comunity projects do, and as a wink at the TV
    1.25 -series "Star Trek: The Next Generation". ;-)
    1.26 +in place, add appropriate support for what I needed, that is uClibc support
    1.27 +and a menu-driven configuration, named the new implementation crosstool-NG,
    1.28 +(standing for crosstool Next Generation, as many other comunity projects do,
    1.29 +and as a wink at the TV series "Star Trek: The Next Generation" ;-) ) and
    1.30 +made it available to the community, in case it was of interest to any one.
    1.31  
    1.32  
    1.33  ___________________________
    1.34 @@ -190,7 +182,7 @@
    1.35  
    1.36  CT_PREFIX_DIR:
    1.37    This is where the toolchain will be installed in (and for now, where it
    1.38 -  will run from). Common use it to add the target tuple in the directory
    1.39 +  will run from). Common use is to add the target tuple in the directory
    1.40    path, such as (see above):
    1.41      /opt/x-tools/${CT_TARGET}
    1.42  
    1.43 @@ -447,7 +439,7 @@
    1.44  ct-ng loads sub- Makefiles from the library directory $(CT_LIB_DIR), as set up
    1.45  at configuration time with ./configure.
    1.46  
    1.47 -ct-ng also search for config files, sub-tools, samples, scripts and patches in
    1.48 +ct-ng also searches for config files, sub-tools, samples, scripts and patches in
    1.49  that library directory.
    1.50  
    1.51  Because of a stupid make behavior/bug I was unable to track down, implicit make