Skip to content

Commit

Permalink
fix some typos in the doc
Browse files Browse the repository at this point in the history
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@276968 91177308-0d34-0410-b5e6-96231b3b80d8
  • Loading branch information
sylvestre committed Jul 28, 2016
1 parent 35df7fd commit 0bab80e
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion docs/FAQ.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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>`_.


Expand Down
2 changes: 1 addition & 1 deletion docs/LangRef.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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>`
Expand Down
2 changes: 1 addition & 1 deletion docs/Proposals/GitHubSubMod.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 0bab80e

Please sign in to comment.