--- a/userguide/html/RVM/Thread Management.html
+++ b/userguide/html/RVM/Thread Management.html
@@ -76,7 +76,8 @@
 <p>The typical algorithm for requesting a thread to block looks as follows:</p>
 
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<pre class="code-java">thread.monitor().lockNoHandshake();
+<pre class="code-java">
+thread.monitor().lockNoHandshake();
 <span class="code-keyword">if</span> (thread is running) {
    thread.takeYieldpoint=1;
 
@@ -94,7 +95,8 @@
 </span>      <span class="code-comment">// acquiring the lock.
 </span>   }
 }
-thread.monitor().unlock();</pre>
+thread.monitor().unlock();
+</pre>
 </div></div>
 
 <p>Most of the time, you do not have to write such code, as the cases of blocking threads are already implemented.  For examples of how to utilize these mechanisms, see <tt>RVMThread.block()</tt>, <tt>RVMThread.hardHandshakeSuspend()</tt>, and <tt>RVMThread.softHandshake()</tt>.  A discussion of how to use these methods follows in the section below.</p>
@@ -145,17 +147,21 @@
 <p>But in all other cases, the calling thread must ensure that the handshake mechanism is notified that thread will block.  Hence, all blocking <tt>Monitor</tt> methods have both a "NoHandshake" and "WithHandshake" version.  Consider the following code:</p>
 
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<pre class="code-java">someMonitor.lockNoHandshake();
+<pre class="code-java">
+someMonitor.lockNoHandshake();
 <span class="code-comment">// perform fast, bounded-time critical section
-</span>someMonitor.unlock(); <span class="code-comment">// non-blocking</span></pre>
+</span>someMonitor.unlock(); <span class="code-comment">// non-blocking</span>
+</pre>
 </div></div>
 
 <p>In this code, lock acquisition is done without notifying handshakes.  This makes the acquisition faster.  In this case, it is safe because the critical section is bounded-time.  As well, we require that in this case, any other critical sections protected by <tt>someMonitor</tt> are bounded-time as well.  If, on the other hand, the critical section was not bounded-time, we would do:</p>
 
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<pre class="code-java">someMonitor.lockWithHandshake();
+<pre class="code-java">
+someMonitor.lockWithHandshake();
 <span class="code-comment">// perform potentially <span class="code-object">long</span> critical section
-</span>someMonitor.unlock();</pre>
+</span>someMonitor.unlock();
+</pre>
 </div></div>
 
 <p>In this case, the <tt>lockWithHandshake()</tt> operation will transition the calling thread to the IN_NATIVE state before acquiring the lock, and then transition it back to IN_JAVA once the lock is acquired.  This may cause the thread to block, if a handshake is in progress.  As an added safety provision, if the <tt>lockWithHandshake()</tt> operation blocks due to a handshake, it will ensure that it does so without holding the <tt>someMonitor</tt> lock.</p>
@@ -191,7 +197,8 @@
 <p>The spin lock is a <tt>org.jikesrvm.scheduler.SpinLock</tt>.  The queue is implemented in <tt>org.jikesrvm.scheduler.ThreadQueue</tt>.  And the blocking/unblocking mechanism leverages <tt>org.jikesrvm.scheduler.Monitor</tt>; in particular, it uses the <tt>Monitor</tt> that is attached to each thread, accessible via <tt>RVMThread.monitor()</tt>.  The basic algorithm for lock acquisition is:</p>
 
 <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
-<pre class="code-java">spinLock.lock();
+<pre class="code-java">
+spinLock.lock();
 <span class="code-keyword">while</span> (<span class="code-keyword">true</span>) {
    <span class="code-keyword">if</span> (lock available) {
       acquire the lock;
@@ -211,7 +218,8 @@
       spinLock.lock();
    }
 }
-spinLock.unlock();</pre>
+spinLock.unlock();
+</pre>
 </div></div>
 
 <p>The algorithm for unlocking dequeues the thread at the head of the queue (if there is one) and notifies its <tt>Monitor</tt> using the <tt>lockedBroadcastNoHandshake()</tt> method.  Note that these algorithms span multiple methods in <tt>org.jikesrvm.scheduler.ThinLock</tt> and <tt>org.jikesrvm.scheduler.Lock</tt>; in particular, <tt>lockHeavy()</tt>, <tt>lockHeavyLocked()</tt>, <tt>unlockHeavy()</tt>, <tt>lock()</tt>, and <tt>unlock()</tt>.</p>
@@ -230,7 +238,7 @@
 				<td height="12" background="http://docs.codehaus.org/images/border/border_bottom.gif"><img src="images/border/spacer.gif" width="1" height="1" border="0"/></td>
 			</tr>
 		    <tr>
-			    <td align="center"><font color="grey">Document generated by Confluence on Jun 10, 2009 09:12</font></td>
+			    <td align="center"><font color="grey">Document generated by Confluence on Jul 04, 2010 19:57</font></td>
 		    </tr>
 	    </table>
     </body>