--- a/DeviceWorkstation.st	Sat Jul 13 22:50:16 2013 +0200
+++ b/DeviceWorkstation.st	Mon Jul 22 11:39:25 2013 +0200
@@ -167,33 +167,33 @@
 
 events
 "
-    All events are processed in a workstations dispatchEvent method.
+    All events are processed in a workstation's dispatchEvent method.
     There, incoming events are first sent to itself, for a first (view independent)
-    preprocessing. For example, the devices state of the shift-, alt-, control and
+    preprocessing. For example, the device's state of the shift-, alt-, control and
     meta keys are updated there. After that, the event is forwarded either to
-    the views sensor or to the view directly (if it has no sensor).
+    the view's sensor or to the view directly (if it has no sensor).
     (Sensorless views are a leftover from ancient times and will sooner or
      later vanish - simplifying things a bit. Do not depend on views without
      sensors to work correctly in future versions.)
 
     This event processing is done by the event dispatcher process, which is
     launched in ST/X's startup sequence (see Smalltalk>>start).
-    Event processing is done at a high priority, to allow keyboad processing
+    Event processing is done at a high priority, to allow keyboard processing
     and CTRL-C handling to be performed even while other processes are running.
     The code executed by the event process is found in #startDispatch.
 
-    Individual events can be enabled or disabled. The ones that are enabled
-    by default are:
-	keypress / keyRelease
-	buttonPress / buttonRelease / buttonMotion (i.e. motion with button pressed)
-	pointerEnter / pointerLeave
-
-    other events have to be enabled by sending a corresponding #enableXXXEvent
+    Individual events can be enabled or disabled. 
+    The ones that are enabled by default are:
+        keypress / keyRelease
+        buttonPress / buttonRelease / buttonMotion (i.e. motion with button pressed)
+        pointerEnter / pointerLeave
+
+    Other events have to be enabled by sending a corresponding #enableXXXEvent
     message to the view which shall receive those events.
     For example, pointerMotion events (i.e. motion without button being pressed)
     are enabled by: 'aView enableMotionEvent'
 
-    The above is only of interest, if you write your own widget classes,
+    The above is only of interest, if you write your own widget classes;
     existing widgets set things as required in their #initEvents method.
 "
 !
@@ -4298,8 +4298,8 @@
     "forward a button-motion for some view"
 
     aView isNil ifTrue:[
-	"/ event arrived, after I destroyed it myself
-	^ self
+        "/ event arrived, after I destroyed it myself
+        ^ self
     ].
     aView sensor buttonMotion:buttonAndModifierState x:x y:y view:aView
 !
@@ -8248,11 +8248,11 @@
 !DeviceWorkstation class methodsFor:'documentation'!
 
 version
-    ^ '$Header: /cvs/stx/stx/libview/DeviceWorkstation.st,v 1.587 2013-07-13 20:38:32 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libview/DeviceWorkstation.st,v 1.588 2013-07-22 09:39:25 cg Exp $'
 !
 
 version_CVS
-    ^ '$Header: /cvs/stx/stx/libview/DeviceWorkstation.st,v 1.587 2013-07-13 20:38:32 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libview/DeviceWorkstation.st,v 1.588 2013-07-22 09:39:25 cg Exp $'
 ! !