diff --git a/Doc/Manual/Contents.html b/Doc/Manual/Contents.html
index 4af66298c..bdb3aa9f5 100644
--- a/Doc/Manual/Contents.html
+++ b/Doc/Manual/Contents.html
@@ -912,6 +912,7 @@
 <li><a href="Java.html#Java_directors_overhead">Overhead and code bloat</a>
 <li><a href="Java.html#Java_directors_example">Simple directors example</a>
 <li><a href="Java.html#Java_directors_threading">Director threading issues</a>
+<li><a href="Java.html#Java_directors_performance">Director performance tuning</a>
 </ul>
 <li><a href="Java.html#Java_allprotected">Accessing protected members</a>
 <li><a href="Java.html#Java_common_customization">Common customization features</a>
diff --git a/Doc/Manual/Java.html b/Doc/Manual/Java.html
index cfee64fa0..ed99549b0 100644
--- a/Doc/Manual/Java.html
+++ b/Doc/Manual/Java.html
@@ -3528,6 +3528,7 @@ Macros can be defined on the commandline when compiling your C++ code, or altern
 
 <H3><a name="Java_directors_performance"></a>24.5.6 Director performance tuning</H3>
 
+
 <p>
 When a new instance of a director (or subclass) is created in Java, the C++ side of the director performs a runtime check per director method to determine if that particular method is overridden in Java or if it should invoke the C++ base implementation directly.  Although this makes initialization slightly more expensive, it is generally a good overall tradeoff.
 </p>