commit 00597283c4d3d886ce69c27b0c4ed4fffa7e9cee
author Chris Lattner <sabre@nondot.org> Thu Aug 17 03:26:50 2006 +0000
committer Chris Lattner <sabre@nondot.org> Thu Aug 17 03:26:50 2006 +0000
tree e81fdaa26beb6363262ccce6eb9f0d22d45eb78c
parent ee02e9743efff92a2b43e74c04e4ee8e04c82d82

Fix validation problem

llvm-svn: 29745

llvm/docs/GetElementPtr.html

diff --git a/llvm/docs/GetElementPtr.html b/llvm/docs/GetElementPtr.html
index 13df3f4..dacc341 100644
--- a/llvm/docs/GetElementPtr.html
+++ b/llvm/docs/GetElementPtr.html
@@ -88,8 +88,8 @@
   <pre>
   X = &amp;Foo[0].F;</pre>
   <p>Sometimes this question gets rephrased as:</p>
-  <blockquote><i>Why is it okay to index through the first pointer, but 
-      subsequent pointers won't be dereferenced?</i></blockquote> 
+  <blockquote><p><i>Why is it okay to index through the first pointer, but 
+      subsequent pointers won't be dereferenced?</i></p></blockquote> 
   <p>The answer is simply because memory does not have to be accessed to 
   perform the computation. The first operand to the GEP instruction must be a 
   value of a pointer type. The value of the pointer is provided directly to