diff options
author | Reid Spencer <rspencer@reidspencer.com> | 2007-02-13 17:04:09 +0000 |
---|---|---|
committer | Reid Spencer <rspencer@reidspencer.com> | 2007-02-13 17:04:09 +0000 |
commit | bed9253387377b6b4d213ac3f7240894744aeb82 (patch) | |
tree | d5afb005c5bd38bab3db5c395e545f09a067e4cd /docs/DeveloperPolicy.html | |
parent | 876eaf1135b40869f59fb27c87a7d626459e9181 (diff) | |
download | external_llvm-bed9253387377b6b4d213ac3f7240894744aeb82.zip external_llvm-bed9253387377b6b4d213ac3f7240894744aeb82.tar.gz external_llvm-bed9253387377b6b4d213ac3f7240894744aeb82.tar.bz2 |
Fix tow grammaros that Bill Wendling noticed.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@34242 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/DeveloperPolicy.html')
-rw-r--r-- | docs/DeveloperPolicy.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html index 41bed52..d767209 100644 --- a/docs/DeveloperPolicy.html +++ b/docs/DeveloperPolicy.html @@ -47,7 +47,7 @@ <!--=========================================================================--> <div class="doc_text"> <p>This document contains the LLVM Developer Policy which defines the - project's policy towards developer's and their contributions. The intent of + project's policy towards developers and their contributions. The intent of this policy is to eliminate mis-communication, rework, and confusion that might arise from the distributed nature of LLVM's development. By stating the policy in clear terms, we hope each developer can know ahead of time @@ -146,7 +146,7 @@ <!-- _______________________________________________________________________ --> <div class="doc_subsection"><a name="devagree">Developer Agreements</a></div> <div class="doc_text"> - <p>With regards to the LLVM copyright and licensing, developer's agree to:</p> + <p>With regards to the LLVM copyright and licensing, developers agree to:</p> <ul> <li>give up their copy rights to any contribution made so that the entire software base can be managed by a single copyright holder.</li> |