1.1 --- a/docs/overview.txt	Tue Jul 17 21:44:33 2007 +0000
     1.2 +++ b/docs/overview.txt	Tue Jul 17 21:49:43 2007 +0000
     1.3 @@ -90,8 +90,14 @@
     1.4  Configuring crosstool-NG  /
     1.5  _________________________/
     1.6  
     1.7 -crosstool-NG is configured the same way you configure your Linux kernel: by
     1.8 -using a curses-based menu. It is assumed you now how to handle this.
     1.9 +crosstool-NG is configured by a configurator presenting a menu-stuctured set of
    1.10 +options. These options let you specify the way you want your toolchain built,
    1.11 +where you want it installed, what architecture and specific processor it
    1.12 +will support, the version of the components you want to use, etc... The
    1.13 +value for those options are then stored in a configuration file.
    1.14 +
    1.15 +The configurator works the same way you configure your Linux kernel.It is
    1.16 +assumed you now how to handle this.
    1.17  
    1.18  To enter the menu, type:
    1.19    ct-ng menuconfig
    1.20 @@ -126,13 +132,15 @@
    1.21  ---------------------------*
    1.22  
    1.23  CT_LOCAL_TARBALLS_DIR:
    1.24 -  If you already have sone tarballs in a direcotry, enter it here. That will
    1.25 +  If you already have some tarballs in a direcotry, enter it here. That will
    1.26    speed up the retrieving phase, where crosstool-NG would otherwise download
    1.27    those tarballs.
    1.28  
    1.29  CT_PREFIX_DIR:
    1.30    This is where the toolchain will be installed in (and for now, where it
    1.31 -  will run from).
    1.32 +  will run from). Common use it to add the target triplet in the directory
    1.33 +  path, such as (see above):
    1.34 +    /opt/x-tools/${CT_TARGET}
    1.35  
    1.36  CT_TARGET_VENDOR:
    1.37    An identifier for your toolchain, will take place in the vendor part of the
    1.38 @@ -186,12 +194,6 @@
    1.39  Running crosstool-NG  /
    1.40  _____________________/
    1.41  
    1.42 -crosstool-NG is configured by a configurator presenting a menu-stuctured set of
    1.43 -options. These options let you specify the way you want your toolchain built,
    1.44 -where you want it installed, what architecture and specific processor it
    1.45 -will support, the version of the components you want to use, etc... The
    1.46 -value for those options are then stored in a configuration file.
    1.47 -
    1.48  To build the toolchain, simply type:
    1.49    ct-ng build
    1.50