From: Chris Lattner <sabre@nondot.org>
Date: Mon, 14 Aug 2006 20:51:35 +0000 (+0000)
Subject: Fix more validation issues
X-Git-Url: http://plrg.eecs.uci.edu/git/?a=commitdiff_plain;h=6e3b7c28f37295cf2a90fa246a77bfe104257ad1;p=oota-llvm.git

Fix more validation issues


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

diff --git a/docs/GettingStarted.html b/docs/GettingStarted.html
index ca0256d9e05..5910ebc305f 100644
--- a/docs/GettingStarted.html
+++ b/docs/GettingStarted.html
@@ -1535,10 +1535,10 @@ transitioning from llvm-gcc3 to llvm-gcc4, we include examples for both.
  
       <p>and</p>
 
-      <p><tt>% lli hello.bc</tt></p></li>
+      <p><tt>% lli hello.bc</tt></p>
 
       <p>The second examples shows how to invoke the LLVM JIT, <a
-       href="CommandGuide/html/lli.html">lli</a>.</p>
+       href="CommandGuide/html/lli.html">lli</a>.</p></li>
 
   <li><p>Use the <tt>llvm-dis</tt> utility to take a look at the LLVM assembly
       code:</p>
@@ -1557,10 +1557,11 @@ transitioning from llvm-gcc3 to llvm-gcc4, we include examples for both.
 
   <li><p>Execute the native code program:</p>
 
-      <p><tt>% ./hello.native</tt></p></li>
+      <p><tt>% ./hello.native</tt></p>
 
       <p>Note that using llvm-gcc to compile directly to native code (i.e. when
          the -emit-llvm option is not present) does steps 6/7/8 for you.</p>
+        </li>
 
 </ol>