--- a/WindowSensor.st	Sat Nov 26 21:38:57 2016 +0000
+++ b/WindowSensor.st	Sat Nov 26 22:00:53 2016 +0000
@@ -80,7 +80,7 @@
     A listener may return true to signal that it has handled the event and that the
     event should NOT be enqueued. 
     Likewise, if it returns false, the event is processed as usual 
-    (i.e. enqueued and forwarded to the views controller).
+    (i.e. enqueued and forwarded to the view's controller).
     If there are multiple listeners, all of them get a chance to process the event,
     but it will not be enqueued, if any returned true.
 
@@ -2099,7 +2099,7 @@
 basicAddDamage:newRectangle view:aView
     "{ Pragma: +optSpeed }"
 
-    "Add newRectangle to the views update region.
+    "Add newRectangle to the view's update region.
      Must be careful, if the damage queue contains an event pattern such as:
         damage  map     
      in this case, a new damage event is required to be added AFTER the map event,
@@ -2141,11 +2141,11 @@
     oldDamageEventIndex notNil ifTrue:[
         "/ there is already a damage for this view in the queue
         "/ (which will wake up the WG, if currently sleeping).
-        "/ so all we have to do is to add the reactangle to the views updateRegion.
+        "/ so all we have to do is to add the reactangle to the view's updateRegion.
         "/ However, if the view was unmapped, and there is
         "/ a mapped event AFTER the expose, we MUST perform the expose
         "/ after we have handled the mapped event.
-        "/ (otherwise, the expose-rect would be added to the views expose region,
+        "/ (otherwise, the expose-rect would be added to the view's expose region,
         "/  and handed at a time when the view thinks it's still unmapped and therefore
         "/  ignore the exposes.)
         "/ Therefore, clear the old damage event and add a new one at the end,
@@ -2593,7 +2593,7 @@
      or asynchronous communication between view applications.
      The view will perform a method as specified by aSelector,
      when it performs event processing; this is different than sending
-     this message directly, since the execution is done by the views process,
+     this message directly, since the execution is done by the view's process,
      not by the current process (which is especially worthwhile, if that method 
      shows a modal box or similar)."
 
@@ -2608,7 +2608,7 @@
      or asynchronous communication between view applications.
      anyObject will perform a method as specified by aSelector,
      when the windogroup dispatches this event. This is different than sending
-     this message directly, since the execution is done by the views process,
+     this message directly, since the execution is done by the view's process,
      not by the current process (which is especially worthwhile, if that method 
      shows a modal box or similar)."
 
@@ -2621,7 +2621,7 @@
      or asynchronous communication between view applications.
      anyObject will perform a method as specified by aSelector,
      when the windogroup dispatches this event. This is different than sending
-     this message directly, since the execution is done by the views process,
+     this message directly, since the execution is done by the view's process,
      not by the current process (which is especially worthwhile, if that method 
      shows a modal box or similar)."