Fix some obvious typoes in docs/overview.txt

docs/overview.txt

@@ -10,14 +10,14 @@ _____________/
 
 crosstool-NG aims at building toolchains. Toolchains are an essential component
 in a software development project. It will compile, assemble and link the code
-that is being developped. Some pieces of the toolchain will eventually end up
+that is being developed. Some pieces of the toolchain will eventually end up
 in the resulting binary/ies: static libraries are but an example.
 
 So, a toolchain is a very sensitive piece of software, as any bug in one of the
 components, or a poorly configured component, can lead to execution problems,
 ranging from poor performance, to applications ending unexpectedly, to
 mis-behaving software (which more than often is hard to detect), to hardware
-damage, or even to human risks (which is more than regretable).
+damage, or even to human risks (which is more than regrettable).
 
 Toolchains are made of different piece of software, each being quite complex
 and requiring specially crafted options to build and work seamlessly. This
@@ -31,7 +31,7 @@ development, but they have a number of limitations:
     no optimisation for your specific target,
   - they can be prepared for a specific target and thus are not easy to use,
     nor optimised for, or even supporting your target,
-  - they often are using ageing components (compiler, C library, etc...) not
+  - they often are using aging components (compiler, C library, etc...) not
     supporting special features of your shiny new processor;
 On the other side, these toolchain offer some advantages:
   - they are ready to use and quite easy to install and setup,
@@ -40,19 +40,19 @@ On the other side, these toolchain offer some advantages:
 But once you want to get all the juice out of your specific hardware, you will
 want to build your own toolchain. This is where crosstool-NG comes into play.
 
-There are also a number of tools that builds toolchains for specific needs,
-which is not really scalable. Examples are:
-  - buildroot (buildroot.uclibc.org) whose main puprpose is to build root file
+There are also a number of tools that build toolchains for specific needs,
+which are not really scalable. Examples are:
+  - buildroot (buildroot.uclibc.org) whose main purpose is to build root file
     systems, hence the name. But once you have your toolchain with buildroot,
     part of it is installed in the root-to-be, so if you want to build a whole
     new root, you either have to save the existing one as a template and
     restore it later, or restart again from scratch. This is not convenient,
   - ptxdist (www.pengutronix.de/software/ptxdist), whose purpose is very
     similar to buildroot,
-  - other projects (openembeded.org for example), which is again used to
+  - other projects (openembedded.org for example), which is again used to
     build root file systems.
 
-crosstool-NG is really targetted at building toolchains, and only toolchains.
+crosstool-NG is really targeted at building toolchains, and only toolchains.
 It is then up to you to use it the way you want.
 
 ___________
@@ -60,16 +60,16 @@ ___________
 History  /
 ________/
 
-crosstool was first 'conceived' by Dan Kegel, which offered it to the community,
+crosstool was first 'conceived' by Dan Kegel, who offered it to the community
 as a set of scripts, a repository of patches, and some pre-configured, general
 purpose setup files to be used to configure crosstool. This is available at
 http://www.kegel.com/crosstool, and the subversion repository is hosted on
 google at http://code.google.com/p/crosstool/.
 
-At the time of writing, crosstool only supports building with one C library,
-namely glibc, and one C compiler, gcc; it is cripled with historical support
-for legacy components, and is some kind of a mess to upgrade. Also, submited
-patches take a loooong time before they are integrated mainline.
+At the time of writing, crosstool supports building with only one C library,
+namely glibc, and one C compiler, gcc; it is crippled with historical support
+for legacy components, and is some kind of a mess to upgrade. Also, submitted
+patches take a loooong time before they are integrated into mainline.
 
 I once managed to add support for uClibc-based toolchains, but it did not make
 into mainline, mostly because I don't have time to port the patch forward to
@@ -97,7 +97,7 @@ There are two ways you can use crosstool-NG:
  - or only build it and run from the source directory.
 
 The former should be used if you got crosstool-NG from a packaged tarball, see
-"Install method", below, while the latter is most usefull for developpers that
+"Install method", below, while the latter is most useful for developpers that
 checked the code out from SVN, and want to submit patches, see "The Hacker's
 way", below.
 
@@ -261,7 +261,7 @@ or:
   man 1 ct-ng
 
 
-Stoping and restarting a build |
+Stopping and restarting a build |
 -------------------------------*
 
 If you want to stop the build after a step you are debugging, you can pass the