From: Chris Lattner <sabre@nondot.org>
Date: Sun, 27 Jul 2008 06:13:09 +0000 (+0000)
Subject: fix tag
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=26bc8332d14c07f179d338c5c52b20514196d42a;p=clang

fix tag


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

diff --git a/www/get_involved.html b/www/get_involved.html
index 398a1151e5..75c5e8b4d4 100644
--- a/www/get_involved.html
+++ b/www/get_involved.html
@@ -122,7 +122,7 @@ about source code. One great application of Clang would be to build an
 auto-documentation system like doxygen that generates code documentation from
 source code. The advantage of using Clang for such a tool is that the tool would
 use the same preprocessor/parser/ASTs as the compiler itself, giving it a very
-rich understanding of the code.</li> </ul>
+rich understanding of the code.</li> 
 
 <li><b>Use clang libraries to implement better versions of existing tools</b>:
 Clang is built as a set of libraries, which means that it is possible to
@@ -133,6 +133,8 @@ The former can be improved to scale better and be more efficient.  The later
 could also be faster and more efficient at reducing C-family programs if built
 on the clang preprocessor.</li>
 
+</ul>
+
 <p>If you hit a bug with clang, it is very useful for us if you reduce the code
 that demonstrates the problem down to something small.  There are many ways to
 do this; ask on cfe-dev for advice.</p>