close <a> tags like they should be for valid html

docs/uclibc.org/FAQ.html

@@ -262,7 +262,7 @@ How could it be smaller and not suck?</a></h2>
 
 <hr />
 <p>
-<h2><a name="toolchain">Do I really need to build a uClibc toolchain?</h2>
+<h2><a name="toolchain">Do I really need to build a uClibc toolchain?</a></h2>
 <p>
 
     Yes, you really do need to build a toolchain to produce uClibc binaries.
@@ -283,7 +283,7 @@ How could it be smaller and not suck?</a></h2>
 
 <hr />
 <p>
-<h2><a name="wrapper">What happened to the old toolchain wrapper?</h2>
+<h2><a name="wrapper">What happened to the old toolchain wrapper?</a></h2>
 <p>
 
     It is possible in some limited cases to re-use an existing glibc toolchain
@@ -366,7 +366,7 @@ How could it be smaller and not suck?</a></h2>
 
 <hr />
 <p>
-<h2><a name="bugs">I think I found a bug in uClibc!  What should I do?</h2>
+<h2><a name="bugs">I think I found a bug in uClibc!  What should I do?</a></h2>
 <p>
 
     If you find a problem with uClibc, please submit a detailed bug report to
@@ -387,7 +387,7 @@ How could it be smaller and not suck?</a></h2>
 <hr />
 <p>
 <h2><a name="miscompile">My package builds fine but link fails with errors like 
-	"undefined reference to __fputc_unlocked", who do I blame?!</h2>
+	"undefined reference to __fputc_unlocked", who do I blame?!</a></h2>
 <p>
 
     This error crops up when a build system mixes system headers (say glibc) 
@@ -401,7 +401,7 @@ How could it be smaller and not suck?</a></h2>
 <hr />
 <p>
 <h2><a name="gnu_malloc">My package builds fine but link fails with errors like "undefined reference
-	to rpl_realloc / rpl_malloc", who do I blame?!</h2>
+	to rpl_realloc / rpl_malloc", who do I blame?!</a></h2>
 <p>
 
     This error crops up because you didn't enable MALLOC_GLIBC_COMPAT support.