path: root/docs
diff options
authorGravatar Yegor Yefremov <yegor_sub1@visionsystems.de>2010-09-28 14:28:55 +0200
committerGravatar Peter Korsgaard <jacmet@sunsite.dk>2010-09-28 14:46:55 +0200
commit3f1d79d379aaf1a0d1e6431575539043a777d160 (patch)
tree82f58fc4a3ce4203d20c1ace735f3486aea5b133 /docs
parent3e5e39a8a25a4a085afe08bdcf46933c8d569ed7 (diff)
fix buildroot.html typos
Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Diffstat (limited to 'docs')
1 files changed, 9 insertions, 9 deletions
diff --git a/docs/buildroot.html b/docs/buildroot.html
index b7a8641e91..fc754e581c 100644
--- a/docs/buildroot.html
+++ b/docs/buildroot.html
@@ -171,7 +171,7 @@ or
<p>All of these "make" commands will need to build a configuration
utility, so you may need to install "development" packages for
- relevent libraries used by the configuration utilities.
+ relevant libraries used by the configuration utilities.
On Debian-like systems, the
<code>libncurses5-dev</code> package is required to use the
<i>menuconfig</i> interface, <code>libqt3-mt-dev</code> is
@@ -345,7 +345,7 @@ $ make HOSTCXX=g++-4.3-HEAD HOSTCC=gcc-4.3-HEAD
toolchain and tools, these changes will be lost. </li>
<li>Customize the target filesystem skeleton available under
- <code>target/generic/target_skeleton/</code>. You can customize
+ <code>fs/skeleton/</code>. You can customize
configuration files or other stuff here. However, the full file hierarchy
is not yet present because it's created during the compilation process.
Therefore, you can't do everything on this target filesystem skeleton, but
@@ -486,12 +486,12 @@ $ make HOSTCXX=g++-4.3-HEAD HOSTCC=gcc-4.3-HEAD
and which steps remain to be done, Buildroot maintains stamp
files (empty files that just tell whether this or that action
has been done). The problem is that these stamp files are not
- uniformely named and handled by the different packages, so some
+ uniformly named and handled by the different packages, so some
understanding of the particular package is needed.</p>
<p>For packages relying on Buildroot packages infrastructures (see
<a href="#add_packages">this section</a> for details), the
- following stamp files are relevent:</p>
+ following stamp files are relevant:</p>
@@ -704,7 +704,7 @@ endif
<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
- 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>
@@ -885,7 +885,7 @@ source "package/libfoo/Config.in"
<li>Makefiles for autotools-based (autoconf, automake, etc.)
- softwares. We provide a dedicated infrastructure for such
+ software. We provide a dedicated infrastructure for such
packages, since autotools is a very common build system. This
infrastructure <i>must</i> be used for new packages that rely on
the autotools as their build system.<br/>We cover them through a
gettext library should not be compiled, because it creates various
kind of build failures.</p>
- <p>Additionnaly, some packages (such as libglib2) do require
- gettext unconditionnally, while other packages (those who
+ <p>Additionally, some packages (such as libglib2) do require
+ gettext unconditionally, while other packages (those who
support <code>--disable-nls</code> in general) only require
gettext when locale support is enabled.</p>
- <p>Therefore, packages that unconditionnally need gettext should:</p>
+ <p>Therefore, packages that unconditionally need gettext should:</p>
<li>Use <code>select BR2_PACKAGE_GETTEXT if