summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/FAQ.rst2
-rw-r--r--llvm/docs/LangRef.rst2
-rw-r--r--llvm/docs/Proposals/GitHubSubMod.rst2
3 files changed, 3 insertions, 3 deletions
diff --git a/llvm/docs/FAQ.rst b/llvm/docs/FAQ.rst
index 0ab99f3452a..ef8b0c886bf 100644
--- a/llvm/docs/FAQ.rst
+++ b/llvm/docs/FAQ.rst
@@ -19,7 +19,7 @@ Initiative (OSI).
Can I modify LLVM source code and redistribute the modified source?
-------------------------------------------------------------------
Yes. The modified source distribution must retain the copyright notice and
-follow the three bulletted conditions listed in the `LLVM license
+follow the three bulleted conditions listed in the `LLVM license
<http://llvm.org/svn/llvm-project/llvm/trunk/LICENSE.TXT>`_.
diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst
index 6be58f3b782..d4d0ee325c9 100644
--- a/llvm/docs/LangRef.rst
+++ b/llvm/docs/LangRef.rst
@@ -9489,7 +9489,7 @@ Semantics:
on the caller's stack. In particular, for targets where stack grows downwards,
adding this offset to the native stack pointer would get the address of the most
recent dynamic alloca. For targets where stack grows upwards, the situation is a bit more
- complicated, because substracting this value from stack pointer would get the address
+ complicated, because subtracting this value from stack pointer would get the address
one past the end of the most recent dynamic alloca.
Although for most targets `llvm.get.dynamic.area.offset <int_get_dynamic_area_offset>`
diff --git a/llvm/docs/Proposals/GitHubSubMod.rst b/llvm/docs/Proposals/GitHubSubMod.rst
index 7319c51dd41..da3d3c4d52f 100644
--- a/llvm/docs/Proposals/GitHubSubMod.rst
+++ b/llvm/docs/Proposals/GitHubSubMod.rst
@@ -151,7 +151,7 @@ The three types hooks to be implemented are:
in the lists, allowing us to retain history and do post-commit reviews.
See: https://help.github.com/articles/managing-notifications-for-pushes-to-a-repository/
-Access will be transfered one-to-one to GitHub accounts for everyone that already
+Access will be transferred one-to-one to GitHub accounts for everyone that already
has commit access to our current repository. Those who don't have accounts will
have to create one in order to continue contributing to the project. In the
future, people only need to provide their GitHub accounts to be granted access.
OpenPOWER on IntegriCloud