[Buildroot] [git commit master 1/1] documentation: update buildroot internal toolchain usage

[Peter Korsgaard]

commit: http://git.buildroot.net/buildroot/commit/?id=dc5e4ca07617b8f28e759d5a22125cc8636001f2
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Gustavo Zacarias <gustavo at zacarias.com.ar>
Acked-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet at sunsite.dk>
---
 docs/buildroot.html |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/buildroot.html b/docs/buildroot.html
index 36297e0..b755922 100644
--- a/docs/buildroot.html
+++ b/docs/buildroot.html
@@ -618,8 +618,8 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured
     use the toolchain that was generated by Buildroot.</p>
 
     <p>The toolchain generated by Buildroot is located by default in
-    <code>output/staging/</code>. The simplest way to use it is to add
-    <code>output/staging/usr/bin/</code> to your PATH environment variable and
+    <code>output/host/</code>. The simplest way to use it is to add
+    <code>output/host/usr/bin/</code> to your PATH environment variable and
     then to use <code>ARCH-linux-gcc</code>, <code>ARCH-linux-objdump</code>,
     <code>ARCH-linux-ld</code>, etc.</p>
 
@@ -628,8 +628,8 @@ $(ZLIB_DIR)/libz.a: $(ZLIB_DIR)/.configured
     is called to tell where the libraries and header files are.</p>
 
     <p>It is also possible to generate the Buildroot toolchain in a
-    directory other than <code>output/staging</code> by using the <code>
-    Build options -&gt; Toolchain and header file location</code> options.
+    directory other than <code>output/host</code> by using the <code>
+    Build options -&gt; Host dir</code> option.
     This could be useful if the toolchain must be shared with other users.</p>
 
     <h2 id="ccache-support">Using <code>ccache</code> in Buildroot</h2>
-- 
1.7.3.4