[llvm-commits] [llvm] r96594 - /llvm/trunk/docs/AdvancedGetElementPtr.html

[Dan Gohman]

Author: djg
Date: Thu Feb 18 12:19:17 2010
New Revision: 96594

URL: http://llvm.org/viewvc/llvm-project?rev=96594&view=rev
Log:
Fix typos Duncan noticed.

Modified:
    llvm/trunk/docs/AdvancedGetElementPtr.html

Modified: llvm/trunk/docs/AdvancedGetElementPtr.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/AdvancedGetElementPtr.html?rev=96594&r1=96593&r2=96594&view=diff

==============================================================================
--- llvm/trunk/docs/AdvancedGetElementPtr.html (original)
+++ llvm/trunk/docs/AdvancedGetElementPtr.html Thu Feb 18 12:19:17 2010
@@ -51,7 +51,7 @@
 
   <p>And, GEP is more concise in common cases.</p>
 
-  <p>However, for of the underlying integer computation implied, there
+  <p>However, for the underlying integer computation implied, there
      is no difference.</p>
 
 </div>
@@ -141,7 +141,7 @@
      assume that the static array type bounds are respected.</p>
 
   <p>The second sense of being out of bounds is computing an address that's
-     beyond of the actual underlying allocated object.</p>
+     beyond the actual underlying allocated object.</p>
 
   <p>With the <tt>inbounds</tt> keyword, the result value of the GEP is
      undefined if the address is outside the actual underlying allocated