commit 4a5dfeeeaafe3acd086c841527c530cdfc146403
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 b70f05ec2f8012bbeb7f3cdf40c27f370aa18ed9
parent 7fdf87ff90eeb2e2b4be53c62ab4b73c73d557d1

Fix validation problem


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@29745 91177308-0d34-0410-b5e6-96231b3b80d8

docs/GetElementPtr.html

diff --git a/docs/GetElementPtr.html b/docs/GetElementPtr.html
index 13df3f4..dacc341 100644
--- a/docs/GetElementPtr.html
+++ b/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