diff --git a/docs/FAQ.rst b/docs/FAQ.rst index 0ab99f3452a7..ef8b0c886bfa 100644 --- a/docs/FAQ.rst +++ b/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 `_. diff --git a/docs/LangRef.rst b/docs/LangRef.rst index 6be58f3b7826..d4d0ee325c99 100644 --- a/docs/LangRef.rst +++ b/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 ` diff --git a/docs/Proposals/GitHubSubMod.rst b/docs/Proposals/GitHubSubMod.rst index 7319c51dd414..da3d3c4d52f2 100644 --- a/docs/Proposals/GitHubSubMod.rst +++ b/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.