summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJoel Jones <joelkevinjones@gmail.com>2017-04-03 18:21:50 +0000
committerJoel Jones <joelkevinjones@gmail.com>2017-04-03 18:21:50 +0000
commit0a5e55e819b2fcd33263374d44ae7ad719d46ca8 (patch)
tree607135c25ec1e6688170a1a542215a11ac902efe
parent754dd3eaef5059653f39ac8e0805a9959fb59dc8 (diff)
downloadbcm5719-llvm-0a5e55e819b2fcd33263374d44ae7ad719d46ca8.tar.gz
bcm5719-llvm-0a5e55e819b2fcd33263374d44ae7ad719d46ca8.zip
Fix LLVMBuild.txt typo. NFC
llvm-svn: 299373
-rw-r--r--llvm/docs/LLVMBuild.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/docs/LLVMBuild.rst b/llvm/docs/LLVMBuild.rst
index a93dcf64408..622780aee31 100644
--- a/llvm/docs/LLVMBuild.rst
+++ b/llvm/docs/LLVMBuild.rst
@@ -54,7 +54,7 @@ handled by another build system (See: :doc:`CMake <CMake>`).
The build system implementation will load the relevant contents of the
LLVMBuild files and use that to drive the actual project build.
Typically, the build system will only need to load this information at
-"configure" time, and use it to generative native information. Build
+"configure" time, and use it to generate native information. Build
systems will also handle automatically reconfiguring their information
when the contents of the ``LLVMBuild.txt`` files change.
OpenPOWER on IntegriCloud