path: root/docs
diff options
authorGravatar Rodrigo Rebello <rprebello@gmail.com>2016-08-18 22:02:11 -0300
committerGravatar Thomas Petazzoni <thomas.petazzoni@free-electrons.com>2016-08-19 11:25:39 +0200
commitf6017708fcf63bb6eb1703b1aee43aff549af484 (patch)
tree1d9b57cd4b7cdbd1fea7e8934c54145e5ab35423 /docs
parent817938bb1699a972463fd576df981145f87624cb (diff)
manual: fix typo
Signed-off-by: Rodrigo Rebello <rprebello@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'docs')
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/manual/using-buildroot-development.txt b/docs/manual/using-buildroot-development.txt
index a075416ba1..e167849cdc 100644
--- a/docs/manual/using-buildroot-development.txt
+++ b/docs/manual/using-buildroot-development.txt
@@ -8,7 +8,7 @@ it, configure, compile and install the software component found inside
this tarball. The source code is extracted in
+output/build/<package>-<version>+, which is a temporary directory:
whenever +make clean+ is used, this directory is entirely removed, and
-re-recreated at the next +make+ invocation. Even when a Git or
+re-created at the next +make+ invocation. Even when a Git or
Subversion repository is used as the input for the package source
code, Buildroot creates a tarball out of it, and then behaves as it
normally does with tarballs.