From 9c6c1dff2e80cafcd828cd663755efdea55645a5 Mon Sep 17 00:00:00 2001
From: Waldemar Brodkorb <mail@waldemar-brodkorb.de>
Date: Mon, 21 Mar 2005 22:22:49 +0000
Subject: [PATCH] some minor fixes

SVN-Revision: 414
---
 openwrt/docs/buildroot-documentation.html | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/openwrt/docs/buildroot-documentation.html b/openwrt/docs/buildroot-documentation.html
index 5a8bb7afe1..91becd8856 100644
--- a/openwrt/docs/buildroot-documentation.html
+++ b/openwrt/docs/buildroot-documentation.html
@@ -231,11 +231,11 @@
 
       <li><b>target</b> (in the <code>target</code> directory) contains the
       Makefiles and associated files for software related to the generation of
-      the target root filesystem image. Four types of filesystems are supported
+      the target root filesystem image. Two types of filesystems are supported
       : jffs2 and squashfs. 
     </ul>
 
-    <p>Each directory contains at least 3 files :</p>
+    <p>Each directory contains at least 2 files :</p>
 
     <ul>
       <li><code>Makefile</code> is the Makefile that downloads, configures,
@@ -294,7 +294,7 @@
     <p>The toolchain generated by the Buildroot by default is located in
     <code>build_ARCH/staging_dir/</code>. The simplest way to use it
     is to add <code>build_ARCH/staging_dir/bin/</code> to your PATH
-    environnement variable, and then to use
+    environment variable, and then to use
     <code>arch-linux-gcc</code>, <code>arch-linux-objdump</code>,
     <code>arch-linux-ld</code>, etc.</p>
 
@@ -304,13 +304,13 @@
     <code>~/buildroot/</code>) :</p>
 
 <pre>
-export PATH=$PATH:~/buildroot/build_mips/bin/
+export PATH=$PATH:~/buildroot/build_mipsel/staging_dir/bin/
 </pre>
 
     <p>Then you can simply do :</p>
 
 <pre>
-mips-linux-gcc -o foo foo.c
+mipsel-linux-uclibc-gcc -o foo foo.c
 </pre>
 
     <p><b>Important</b> : do not try to move the toolchain to an other
@@ -510,7 +510,7 @@ foo-compile: bar-compile
      of <code>BUILD_DIR</code> which is created upon decompression of
      the tarball.</li>
 
-     <li><code>PKG_IPK</code> : The resulting <i>ipkg</i> pacakge
+     <li><code>PKG_IPK</code> : The resulting <i>ipkg</i> package
 
     </ul>