--- a/InstrumentationContext.st	Fri Oct 26 11:48:52 2012 +0200
+++ b/InstrumentationContext.st	Fri Oct 26 12:53:40 2012 +0200
@@ -39,11 +39,14 @@
 "
     installed as a thread-local variable (instrumentationContext) by the
     beActiveIn:aProcess method, instances of me keep some meta state while
-    instrumentation is ongoing. 
-    Especially, only in processes with a context are instrumentationInfo objects
-    updated. This has two advantages:
-    - it blocks recursive calls, while inside instrumentation code
-    - it blocks instrumentation from other processes (so only test-code is instrumented)
+    instrumentation is ongoing.
+
+    Especially, instrumentationInfo objects are only updated in processes with a context. 
+    This has two advantages:
+        - it blocks recursive calls, while inside instrumentation code
+        - it blocks measurements from other processes 
+          (so code coverage is only measured when executed during a test run, not if
+           executed by other processes)
 "
 ! !
 
@@ -292,9 +295,9 @@
 !InstrumentationContext class methodsFor:'documentation'!
 
 version
-    ^ '$Header: /cvs/stx/stx/libcomp/InstrumentationContext.st,v 1.10 2012-10-17 23:40:02 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libcomp/InstrumentationContext.st,v 1.11 2012-10-26 10:53:40 cg Exp $'
 !
 
 version_CVS
-    ^ '$Header: /cvs/stx/stx/libcomp/InstrumentationContext.st,v 1.10 2012-10-17 23:40:02 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libcomp/InstrumentationContext.st,v 1.11 2012-10-26 10:53:40 cg Exp $'
 ! !