commit bb72f7741608f258274cb3e413cdb02205544108
author Chris Lattner <sabre@nondot.org> Fri Apr 10 05:54:56 2009 +0000
committer Chris Lattner <sabre@nondot.org> Fri Apr 10 05:54:56 2009 +0000
tree ce2710e4df3e3c6a1d59042196dfdbda3674f2ba
parent b36338aa007a4afbaf452d6e13d85a2907edb5e6

typos

llvm-svn: 68770

clang/docs/LanguageExtensions.html

diff --git a/clang/docs/LanguageExtensions.html b/clang/docs/LanguageExtensions.html
index 270d32d..d298a56 100644
--- a/clang/docs/LanguageExtensions.html
+++ b/clang/docs/LanguageExtensions.html
@@ -303,11 +303,11 @@
 occurs) but may actually return so that the program can fail gracefully. The
 <tt>analyzer_noreturn</tt> attribute allows one to annotate such functions as
 being interpreted as &quot;no return&quot; functions by the analyzer (thus
-pruning bogus paths) but will not effect compilation (as in the case of
+pruning bogus paths) but will not affect compilation (as in the case of
 <tt>noreturn</tt>).</p>
 
 <p><b>Usage</b>: The <tt>analyzer_noreturn</tt> attribute can be placed in the
-sampe places where the <tt>noreturn</tt> attribute can be placed. It is commonly
+same places where the <tt>noreturn</tt> attribute can be placed. It is commonly
 placed at the end of function prototypes:</p>
 
 <pre>