diff --git a/doc/changes.html b/doc/changes.html
index c79e00c9..2107193a 100644
--- a/doc/changes.html
+++ b/doc/changes.html
@@ -121,7 +121,7 @@ to see whether newer versions are available.
 
 <h2 id="LuaJIT-2.0.0-beta3">LuaJIT 2.0.0-beta3 &mdash; 2010-03-07</h2>
 <ul>
-<li>LuaJIT x64 port:</li>
+<li>LuaJIT x64 port:
 <ul>
 <li>Port integrated memory allocator to Linux/x64, Windows/x64 and OSX/x64.</li>
 <li>Port interpreter and JIT compiler to x64.</li>
diff --git a/doc/ext_ffi.html b/doc/ext_ffi.html
index f496b51b..50a44052 100644
--- a/doc/ext_ffi.html
+++ b/doc/ext_ffi.html
@@ -138,7 +138,7 @@ the proper path, add Lua code that loads the module aaaand ... finally
 call the binding function. Phew!
 </p>
 
-<h2 id="call">Motivating Example: Using C Data Structures</h2>
+<h2 id="cdata">Motivating Example: Using C Data Structures</h2>
 <p>
 The FFI library allows you to create and access C&nbsp;data
 structures. Of course the main use for this is for interfacing with
diff --git a/doc/extensions.html b/doc/extensions.html
index b9a055c5..8385727b 100644
--- a/doc/extensions.html
+++ b/doc/extensions.html
@@ -232,7 +232,7 @@ the toolchain used to compile LuaJIT:
 <tr class="odd separate">
 <td class="excplatform">POSIX/x64, DWARF2 unwinding</td>
 <td class="exccompiler">GCC 4.3+</td>
-<td class="excinterop"><b style="color: #00a000;">Full</td>
+<td class="excinterop"><b style="color: #00a000;">Full</b></td>
 </tr>
 <tr class="even">
 <td class="excplatform">Other platforms, DWARF2 unwinding</td>
@@ -242,7 +242,7 @@ the toolchain used to compile LuaJIT:
 <tr class="odd">
 <td class="excplatform">Windows/x64</td>
 <td class="exccompiler">MSVC or WinSDK</td>
-<td class="excinterop"><b style="color: #00a000;">Full</td>
+<td class="excinterop"><b style="color: #00a000;">Full</b></td>
 </tr>
 <tr class="even">
 <td class="excplatform">Windows/x86</td>
diff --git a/doc/install.html b/doc/install.html
index 73755619..55de1bd8 100644
--- a/doc/install.html
+++ b/doc/install.html
@@ -392,7 +392,7 @@ See: <tt>man rebase</tt>
 for embedding Lua or LuaJIT into your application.</li>
 <li>Make sure you use <tt>luaL_newstate</tt>. Avoid using
 <tt>lua_newstate</tt>, since this uses the (slower) default memory
-allocator from your system (no support for this on x64).</tt></li>
+allocator from your system (no support for this on x64).</li>
 <li>Make sure you use <tt>luaL_openlibs</tt> and not the old Lua 5.0 style
 of calling <tt>luaopen_base</tt> etc. directly.</li>
 <li>To change or extend the list of standard libraries to load, copy
diff --git a/doc/luajit.html b/doc/luajit.html
index aea5c657..131e4396 100644
--- a/doc/luajit.html
+++ b/doc/luajit.html
@@ -118,7 +118,7 @@ language features.
 <p>
 It's destined to break into the <a href="http://luajit.org/performance.html"><span class="ext">&raquo;</span>&nbsp;performance</a>
 range traditionally reserved for offline, static language compilers.
-Have look at these <a href="http://shootout.alioth.debian.org/u32/benchmark.php?test=all&lang=all&d=data&calc=calculate&gpp=on&java=on&luajit=on&v8=on&lua=on&tracemonkey=on&box=1"><span class="ext">&raquo;</span>&nbsp;cross-language benchmarks</a>
+Have look at these <a href="http://shootout.alioth.debian.org/u32/benchmark.php?test=all&amp;lang=all&amp;d=data&amp;calc=calculate&amp;gpp=on&amp;java=on&amp;luajit=on&amp;v8=on&amp;lua=on&amp;tracemonkey=on&amp;box=1"><span class="ext">&raquo;</span>&nbsp;cross-language benchmarks</a>
 to see how it ranks against the competition.
 </p>