# HG changeset patch
# User "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
# Date 1184708983 0
# Node ID 4c32aa5569b2bd6c407cdccfb86d46e5e8e19ff1
# Parent  835178a32fc1d71e420ecff8c81fef54d5550e7d
Re-order and rework a bit docs/overview.txt. Plus a typo fix.

diff -r 835178a32fc1 -r 4c32aa5569b2 docs/overview.txt
--- a/docs/overview.txt	Tue Jul 17 21:44:33 2007 +0000
+++ b/docs/overview.txt	Tue Jul 17 21:49:43 2007 +0000
@@ -90,8 +90,14 @@
 Configuring crosstool-NG  /
 _________________________/
 
-crosstool-NG is configured the same way you configure your Linux kernel: by
-using a curses-based menu. It is assumed you now how to handle this.
+crosstool-NG is configured by a configurator presenting a menu-stuctured set of
+options. These options let you specify the way you want your toolchain built,
+where you want it installed, what architecture and specific processor it
+will support, the version of the components you want to use, etc... The
+value for those options are then stored in a configuration file.
+
+The configurator works the same way you configure your Linux kernel.It is
+assumed you now how to handle this.
 
 To enter the menu, type:
   ct-ng menuconfig
@@ -126,13 +132,15 @@
 ---------------------------*
 
 CT_LOCAL_TARBALLS_DIR:
-  If you already have sone tarballs in a direcotry, enter it here. That will
+  If you already have some tarballs in a direcotry, enter it here. That will
   speed up the retrieving phase, where crosstool-NG would otherwise download
   those tarballs.
 
 CT_PREFIX_DIR:
   This is where the toolchain will be installed in (and for now, where it
-  will run from).
+  will run from). Common use it to add the target triplet in the directory
+  path, such as (see above):
+    /opt/x-tools/${CT_TARGET}
 
 CT_TARGET_VENDOR:
   An identifier for your toolchain, will take place in the vendor part of the
@@ -186,12 +194,6 @@
 Running crosstool-NG  /
 _____________________/
 
-crosstool-NG is configured by a configurator presenting a menu-stuctured set of
-options. These options let you specify the way you want your toolchain built,
-where you want it installed, what architecture and specific processor it
-will support, the version of the components you want to use, etc... The
-value for those options are then stored in a configuration file.
-
 To build the toolchain, simply type:
   ct-ng build