Regenerate all the rest of the docs
diff --git a/doc/html/callbacks.html b/doc/html/callbacks.html
index d6df95e..9a9aeaf 100644
--- a/doc/html/callbacks.html
+++ b/doc/html/callbacks.html
@@ -55,8 +55,8 @@
functions can block if the socket is in blocking mode, and then you want other
Python threads to be able to do other things. The real trouble is if you've
released the thread lock to do a potentially blocking operation, and the
-operation calls a callback. Then we must take the thread lock back<A NAME="tex2html6"
- HREF="#foot974"><SUP>5</SUP></A>.
+operation calls a callback. Then we must take the thread lock back<A NAME="tex2html5"
+ HREF="#foot972"><SUP>4</SUP></A>.
<P>
There are two solutions to the first problem, both of which are necessary. The
@@ -84,8 +84,8 @@
<P>
<BR><HR><H4>Footnotes</H4>
<DL>
-<DT><A NAME="foot974">... back</A><A
- href="callbacks.html#tex2html6"><SUP>5</SUP></A></DT>
+<DT><A NAME="foot972">... back</A><A
+ href="callbacks.html#tex2html5"><SUP>4</SUP></A></DT>
<DD>I'm
not sure why this is necessary, but otherwise I get a segmentation violation on
<tt class="cfunction">PyEval_CallObject</tt>
@@ -120,7 +120,7 @@
<b class="navlabel">Up:</b> <a class="sectref" href="internals.html">4 Internals</A>
<b class="navlabel">Next:</b> <a class="sectref" href="socket-methods.html">4.3 Acessing Socket Methods</A>
<hr>
-<span class="release-info">Release 0.7a2.</span>
+<span class="release-info">Release 0.7.</span>
</DIV>
<!--End of Navigation Panel-->