diff --git a/docs/DeveloperPolicy.html b/docs/DeveloperPolicy.html
index 78c0fb9a381..41bed52552c 100644
--- a/docs/DeveloperPolicy.html
+++ b/docs/DeveloperPolicy.html
@@ -66,7 +66,7 @@
     <a href="#t_commit">commit</a> form.</dd>
     <dt><a name="t_commit">Commit</a><dt>
     <dd>A <a href="t_change">change</a> submitted directly to LLVM software
-    respository via the <tt>cvs commit</tt> command.</dd>
+    repository via the <tt>cvs commit</tt> command.</dd>
     <dt><a name="t_developer">Developer</a></dt>
     <dd>Anyone who submits a <a href="#t_change">change</a> to LLVM.</dd>
     <dt><a name="t_inrement">Increment</a></dt>
@@ -175,7 +175,7 @@
   made by others.</p>
   <p>Active developers must register an email account with bugzilla 
   (<a href="http://llvm.org/bugs/">http://llvm.org/bugs/</a>) and preferably
-  subscribe to the llvm-bugs email list to keep track of bugs occuring in
+  subscribe to the llvm-bugs email list to keep track of bugs occurring in
   LLVM.</p>
 </div>
 
@@ -256,7 +256,7 @@
     <li>Code must compile cleanly on all platforms.</li>
     <li>Code must pass the <tt>llvm-test</tt> test suite including 
     SPEC CINT2000, SPEC CFP2000, SPEC CINT2006, and SPEC CFP2006.</li>
-    <li>The changesat must not cause performance or correctness regressions 
+    <li>The change set must not cause performance or correctness regressions 
     for the LLVM tools.</li>
     <li>The changes must not cause performance or correctness regressions in 
     code compiled with LLVM on all applicable targets.</li>
@@ -271,7 +271,7 @@
   apply:</p>
   <ol>
     <li>All feature and regression test cases must be added to the 
-    <tt>llvm/test</tt> directory. The appropriate subdirectory should be 
+    <tt>llvm/test</tt> directory. The appropriate sub-directory should be 
     selected (see the <a href="TestingGuide.html">Testing Guide</a> for 
     details.</li>
     <li>Test cases should be written in LLVM assembly language unless the
@@ -393,7 +393,7 @@
     <li>You are granted <i>commit-after-approval</i> to all parts of LLVM.
     To get approval, submit a patch to llvm-commits per the patch policies 
     above.  When approved you may commit it yourself.</li>
-    <li>You are granted <i>commit-without-approavl</i> to those portions of LLVM
+    <li>You are granted <i>commit-without-approval</i> to those portions of LLVM
     that you own (contributed) or maintain (have been assigned responsibility 
     for), with the proviso that such commits must not break the build. This is
     a "trust but verify" policy and commits of this nature are reviewed after 
@@ -402,7 +402,7 @@
     be reverted. This is necessary when the change blocks other developers from
     making progress. The developers is welcome to re-commit the change after 
     the problem has been fixed.</li>
-    <li>Multiple violations of these policies or a single aggregious violation
+    <li>Multiple violations of these policies or a single egregious violation
     may cause commit access to be revoked, at the sole discretion of the
     LLVM Oversight Group.</li>
   </ol>