1.1 --- a/docs/9 - How is a toolchain constructed.txt	Sun Jul 17 16:54:50 2011 +0200
     1.2 +++ b/docs/9 - How is a toolchain constructed.txt	Sun Jul 17 16:53:40 2011 +0200
     1.3 @@ -50,13 +50,13 @@
     1.4  thereof, running on the target, we also need the C library. The C library
     1.5  provides a standard abstraction layer that performs basic tasks (such as
     1.6  allocating memory, printing output on a terminal, managing file access...).
     1.7 -There are many C libraries, each targetted to different systems. For the
     1.8 -Linux /desktop/, there is glibc or eglibc or ven uClibc, for embeded Linux,
     1.9 +There are many C libraries, each targeted to different systems. For the
    1.10 +Linux /desktop/, there is glibc or eglibc or even uClibc, for embedded Linux,
    1.11  you have a choice of eglibc or uClibc, while for system without an Operating
    1.12  System, you may use newlib, dietlibc, or even none at all. There a few other
    1.13 -C libraries, but they are not as widely used, and/or are targetted to very
    1.14 +C libraries, but they are not as widely used, and/or are targeted to very
    1.15  specific needs (eg. klibc is a very small subset of the C library aimed at
    1.16 -building contrained initial ramdisks).
    1.17 +building constrained initial ramdisks).
    1.18  
    1.19  Under Linux, the C library needs to know the API to the kernel to decide
    1.20  what features are present, and if needed, what emulation to include for
    1.21 @@ -168,7 +168,7 @@
    1.22      correct rounding, MPFR
    1.23    - the C library for the arithmetic of complex numbers, MPC
    1.24  
    1.25 -The dependencies for those liraries are:
    1.26 +The dependencies for those libraries are:
    1.27  
    1.28    - MPC requires GMP and MPFR
    1.29    - MPFR requires GMP
    1.30 @@ -205,7 +205,7 @@
    1.31  To enable LTO:
    1.32    - the ELF object file access library, libelf
    1.33  
    1.34 -The depencies for those libraries are:
    1.35 +The dependencies for those libraries are:
    1.36  
    1.37    - PPL requires GMP
    1.38    - CLooG/PPL requires GMP and PPL
    1.39 @@ -233,7 +233,7 @@
    1.40  So the list is complete. But why does crosstool-NG have more steps? |
    1.41  --------------------------------------------------------------------+
    1.42  
    1.43 -The already thirteen steps are the necessary steps, from a theorical point
    1.44 +The already thirteen steps are the necessary steps, from a theoretical point
    1.45  of view. In reality, though, there are small differences; there are three
    1.46  different reasons for the additional steps in crosstool-NG.
    1.47  
    1.48 @@ -249,9 +249,9 @@
    1.49  
    1.50  Third, crosstool-NG can also build some additional debug utilities to run on
    1.51  the target. This is where we build, for example, the cross-gdb, the gdbserver
    1.52 -and the native gdb (the last two run on the target, the furst runs on the
    1.53 +and the native gdb (the last two run on the target, the first runs on the
    1.54  same machine as the toolchain). The others (strace, ltrace, DUMA and dmalloc)
    1.55  are absolutely not related to the toolchain, but are nice-to-have stuff that
    1.56 -can greatly help when developping, so are included as goodies (and they are
    1.57 +can greatly help when developing, so are included as goodies (and they are
    1.58  quite easy to build, so it's OK; more complex stuff is not worth the effort
    1.59  to include in crosstool-NG).