summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
authorHiroshi Inoue <inouehrs@jp.ibm.com>2018-01-29 05:17:03 +0000
committerHiroshi Inoue <inouehrs@jp.ibm.com>2018-01-29 05:17:03 +0000
commitc8e924581676b4386e4ab6a28e121d3a5b13c025 (patch)
tree94e44a040ceff8ea1d2c0ecd1fce8cb8c2e7b22d /llvm/docs
parent1019f8a98e33c56e98592733b2e7e92723b4e404 (diff)
downloadbcm5719-llvm-c8e924581676b4386e4ab6a28e121d3a5b13c025.tar.gz
bcm5719-llvm-c8e924581676b4386e4ab6a28e121d3a5b13c025.zip
[NFC] fix trivial typos in comments and documents
"to to" -> "to" llvm-svn: 323628
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/GettingStarted.rst2
-rw-r--r--llvm/docs/tutorial/LangImpl08.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/llvm/docs/GettingStarted.rst b/llvm/docs/GettingStarted.rst
index dfc32cab828..7afccc56aa9 100644
--- a/llvm/docs/GettingStarted.rst
+++ b/llvm/docs/GettingStarted.rst
@@ -324,7 +324,7 @@ However, some Linux distributions and some other or older BSDs sometimes have
extremely old versions of GCC. These steps attempt to help you upgrade you
compiler even on such a system. However, if at all possible, we encourage you
to use a recent version of a distribution with a modern system compiler that
-meets these requirements. Note that it is tempting to to install a prior
+meets these requirements. Note that it is tempting to install a prior
version of Clang and libc++ to be the host compiler, however libc++ was not
well tested or set up to build on Linux until relatively recently. As
a consequence, this guide suggests just using libstdc++ and a modern GCC as the
diff --git a/llvm/docs/tutorial/LangImpl08.rst b/llvm/docs/tutorial/LangImpl08.rst
index 96eccaebd32..da4e60f84b8 100644
--- a/llvm/docs/tutorial/LangImpl08.rst
+++ b/llvm/docs/tutorial/LangImpl08.rst
@@ -44,7 +44,7 @@ returns the target triple of the current machine.
auto TargetTriple = sys::getDefaultTargetTriple();
-LLVM doesn't require us to to link in all the target
+LLVM doesn't require us to link in all the target
functionality. For example, if we're just using the JIT, we don't need
the assembly printers. Similarly, if we're only targeting certain
architectures, we can only link in the functionality for those
OpenPOWER on IntegriCloud