diff --git a/Doc/Manual/Contents.html b/Doc/Manual/Contents.html
index 736bd08a8..04cbbcf2a 100644
--- a/Doc/Manual/Contents.html
+++ b/Doc/Manual/Contents.html
@@ -1332,7 +1332,7 @@
 <li><a href="Python.html#Python_nn28">Further details on the Python class interface</a>
 <ul>
 <li><a href="Python.html#Python_nn29">Proxy classes</a>
-<li><a href="Python.html#Python_builtin_classes">Built-in Classes</a>
+<li><a href="Python.html#Python_builtin_types">Built-in Types</a>
 <ul>
 <li><a href="Python.html#Python_builtin_limitations">Limitations</a>
 <li><a href="Python.html#Python_builtin_overloads">Operator overloads -- use them!</a>
diff --git a/Doc/Manual/Python.html b/Doc/Manual/Python.html
index d179d3beb..81b2fe04e 100644
--- a/Doc/Manual/Python.html
+++ b/Doc/Manual/Python.html
@@ -2480,9 +2480,8 @@ doesn't know how to add an instance of <tt>MyString</tt> to itself.
 <li><p>If you have multiple SWIG modules that share type information (<a href="Modules.html#Modules_nn2">more info</a>),
 the <tt>-builtin</tt> option requiress a bit of extra discipline to ensure that base classes are initialized before derived classes.  Specifically:</p>
 <ul>
-<li>There must be an unambiguous dependency graph for the modules.</li>
-<li>Module dependencies must be explicitly stated with <tt>%import</tt> statements in the SWIG interface file.</li>
-</li>
+<li><p>There must be an unambiguous dependency graph for the modules.</p></li>
+<li><p>Module dependencies must be explicitly stated with <tt>%import</tt> statements in the SWIG interface file.</p>
 </ul>
 
 <p>As an example, suppose module <tt>A</tt> has this interface in <tt>A.i</tt> :</p>