@@ -22,7 +22,7 @@ Building a cross-toolchain can be a real
makes it easy to build cross-toolchains, and allows you to take all the juice
out of your target by configuring the different components of the toolchain
-accordingly to the targeted processor.
+according to the targeted processor.
@@ -62,10 +62,10 @@ with the target tuple they represent.
Save the current configuration to a mini-defconfig file, that contains only
-the strictly required symbols to reproduce the configuraiton. defconfig files
+the strictly required symbols to reproduce the configuration. defconfig files
are much smaller than a complete .config, so it is easy to send by mail. As
only non-default symbols are present in a defconfig, it easy to spot the
-meaningfull values. Also, it is easy to use defconfig files with newer
+meaningful values. Also, it is easy to use defconfig files with newer
.BR crosstool-NG .
By default the mini-defconfig is saved to a file named
@@ -92,11 +92,11 @@ Configure
using a mini-defconfig file (previously saved with
-or manually edited). The default mini-defconfig is rad from the file
+or manually edited). The default mini-defconfig is read from the file
.IR defconfig ,
-unless the vraiable
+unless the variable
-is set, inwhich case the mini-defconfig will be read from the file referenced
+is set, in which case the mini-defconfig will be read from the file referenced
@@ -162,9 +162,9 @@ to have the meaning of the exit values.
As of today (@@CT_DATE@@), building tarballs is broken. It is difficult to
-foresee how every parts of
+foresee how all parts of
-are going to be installed. Each parts is needed to build a tarball, as it
+are going to be installed. Each part is needed to build a tarball, as it
contains all that is needed to rebuild the toolchain from scratch: toolchain