diff --git a/Doc/Manual/Contents.html b/Doc/Manual/Contents.html
index 0f84d937a..a44ac8fe0 100644
--- a/Doc/Manual/Contents.html
+++ b/Doc/Manual/Contents.html
@@ -355,7 +355,7 @@
 </ul>
 <li><a href="Typemaps.html#Typemaps_nn42">Multi-argument typemaps</a>
 <li><a href="Typemaps.html#runtime_type_checker">The run-time type checker</a>
-<li><a href="Typemaps.html#Typemaps_nn44">Typemaps and overloading</a>
+<li><a href="Typemaps.html#Typemaps_overloading">Typemaps and overloading</a>
 <li><a href="Typemaps.html#Typemaps_nn45">More about <tt>%apply</tt> and <tt>%clear</tt></a>
 <li><a href="Typemaps.html#Typemaps_nn46">Reducing wrapper code size</a>
 <li><a href="Typemaps.html#Typemaps_nn47">Passing data between typemaps</a>
diff --git a/Doc/Manual/SWIGPlus.html b/Doc/Manual/SWIGPlus.html
index 046577b52..c70e940c9 100644
--- a/Doc/Manual/SWIGPlus.html
+++ b/Doc/Manual/SWIGPlus.html
@@ -662,7 +662,12 @@ For example if a method has ten default arguments, then eleven wrapper methods a
 
 <p>
 Please see the <a href="Customization.html#Customization_features_default_args">Features and default arguments</a>
-section for more information on using <tt>%feature</tt> for functions with default arguments.
+section for more information on using <tt>%feature</tt> with functions with default arguments.
+The <a href="#ambiguity_resolution_renaming">Ambiguity resolution and renaming</a> section 
+also deals with using <tt>%rename</tt> and <tt>%ignore</tt> on methods with default arguments.
+If you are writing your own typemaps for types used in methods with default arguments, you may also need to write a <tt>typecheck</tt> typemap.
+See the <a href="Typemaps.html#Typemaps_overloading">Typemaps and overloading</a> section for details or otherwise use the 
+use the <tt>compactdefaultargs</tt> feature as mentioned below.
 </p>
 
 <p>
diff --git a/Doc/Manual/Sections.html b/Doc/Manual/Sections.html
index b79d695c9..1c4850124 100644
--- a/Doc/Manual/Sections.html
+++ b/Doc/Manual/Sections.html
@@ -6,7 +6,7 @@
 <body bgcolor="#ffffff">
 <H1><a name="Sections"></a>SWIG-1.3 Development Documentation</H1>
 
-Last update : SWIG-1.3.23 (November 6, 2004)
+Last update : SWIG-1.3.23 (November 11, 2004)
 
 <H2>Sections</H2>
 
diff --git a/Doc/Manual/Typemaps.html b/Doc/Manual/Typemaps.html
index 2452c7f79..2d4b405fc 100644
--- a/Doc/Manual/Typemaps.html
+++ b/Doc/Manual/Typemaps.html
@@ -63,7 +63,7 @@
 </ul>
 <li><a href="#Typemaps_nn42">Multi-argument typemaps</a>
 <li><a href="#runtime_type_checker">The run-time type checker</a>
-<li><a href="#Typemaps_nn44">Typemaps and overloading</a>
+<li><a href="#Typemaps_overloading">Typemaps and overloading</a>
 <li><a href="#Typemaps_nn45">More about <tt>%apply</tt> and <tt>%clear</tt></a>
 <li><a href="#Typemaps_nn46">Reducing wrapper code size</a>
 <li><a href="#Typemaps_nn47">Passing data between typemaps</a>
@@ -2744,7 +2744,7 @@ type-checking.  This code is also included in every generated wrapped file so yo
 probably just look at the output of SWIG to get a better sense for how types are
 managed.
 
-<H2><a name="Typemaps_nn44"></a>10.9 Typemaps and overloading</H2>
+<H2><a name="Typemaps_overloading"></a>10.9 Typemaps and overloading</H2>
 
 
 In many target languages, SWIG fully supports C++ overloaded methods and functions.   For example,
