Add some verbiage about Clang to the 2.7 release notes

[oota-llvm.git] / docs / CodingStandards.html

diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html
index 894521650a675bd829fde1a31001ef653d0b7463..7815e19739f30854872e8501f3aacb22628937e1 100644 (file)
--- a/docs/CodingStandards.html
+++ b/docs/CodingStandards.html
@@ -194,9 +194,9 @@ something sane goes a long ways towards avoiding writing documentation.</p>
 <b>Method information</b>
 
 <p>Methods defined in a class (as well as any global functions) should also be
-documented properly.  A quick note about what it does any a description of the
+documented properly.  A quick note about what it does and a description of the
 borderline behaviour is all that is necessary here (unless something
-particularly tricky or insideous is going on).  The hope is that people can
+particularly tricky or insidious is going on).  The hope is that people can
 figure out how to use your interfaces without reading the code itself... that is
 the goal metric.</p>
 
@@ -303,7 +303,7 @@ for debate.</p>
 <div class="doc_text">
 
 <p>In all cases, prefer spaces to tabs in source files.  People have different
-prefered indentation levels, and different styles of indentation that they
+preferred indentation levels, and different styles of indentation that they
 like... this is fine.  What isn't is that different editors/viewers expand tabs
 out to different tab stops.  This can cause your code to look completely
 unreadable, and it is not worth dealing with.</p>
@@ -491,7 +491,7 @@ most cases, you simply don't need the definition of a class... and not
 <b>must</b> include all of the header files that you are using -- you can 
 include them either directly
 or indirectly (through another header file).  To make sure that you don't
-accidently forget to include a header file in your module header, make sure to
+accidentally forget to include a header file in your module header, make sure to
 include your module header <b>first</b> in the implementation file (as mentioned
 above).  This way there won't be any hidden dependencies that you'll find out
 about later...</p>
@@ -790,7 +790,7 @@ locality.</p>
 <div class="doc_text">
 
 <p>Use the "<tt>assert</tt>" function to its fullest.  Check all of your
-preconditions and assumptions, you never know when a bug (not neccesarily even
+preconditions and assumptions, you never know when a bug (not necessarily even
 yours) might be caught early by an assertion, which reduces debugging time
 dramatically.  The "<tt>&lt;cassert&gt;</tt>" header file is probably already
 included by the header files you are using, so it doesn't cost anything to use