--- a/Monitor.st	Sat Jul 20 02:52:53 2013 +0200
+++ b/Monitor.st	Thu Jul 25 11:40:25 2013 +0200
@@ -37,25 +37,24 @@
 
 documentation
 "
-    Monitors - functionality much like RecursionLocks, but not
-    block based.
-    Monitors are not unwind-save (i.e. a return or unwind while a
+    Monitors (as used in Java) provide a functionality much like RecursionLocks, 
+    but are not block based.
+    Therefore, monitors are not unwind-save (i.e. a return or unwind while a
     monitor is locked, will lead to a deadlock situation).
-    You have to care for unwinds yourself.
+    You have to care for unwind protection yourself.
 
     Notice:
-	This is an experimental demo class - there is no WARRANTY.
-	Smalltalkers should use Semaphores and RecursionLocks, which
-	are unwind-save.
+        This is an experimental demo class - there is no WARRANTY.
+        Smalltalkers should use Semaphores and RecursionLocks, which
+        are unwind-save.
 
     [see also:]
-	RecursionLock Semaphore Delay SharedQueue
-	Block
+        RecursionLock Semaphore Delay SharedQueue
+        Block
 
     [author:]
-	Claus Gittinger
+        Claus Gittinger
 "
-
 !
 
 examples
@@ -296,6 +295,6 @@
 !Monitor class methodsFor:'documentation'!
 
 version
-    ^ '$Header: /cvs/stx/stx/libbasic2/Monitor.st,v 1.17 2013-04-01 00:44:18 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libbasic2/Monitor.st,v 1.18 2013-07-25 09:40:25 cg Exp $'
 ! !