# HG changeset patch
# User Claus Gittinger <cg@exept.de>
# Date 1487012723 -3600
# Node ID 4aaf30c174e9c44e21208dedf24033afc5ce4405
# Parent  83d6f106ccafdddf25da4905d29bfea9270c2636
#DOCUMENTATION by cg
class: Context
comment/format in: #documentation

diff -r 83d6f106ccaf -r 4aaf30c174e9 Context.st
--- a/Context.st	Mon Feb 13 14:44:51 2017 +0100
+++ b/Context.st	Mon Feb 13 20:05:23 2017 +0100
@@ -44,15 +44,15 @@
     Every message send adds a context to a chain, which can be traced back via
     the sender field. The context of the currently active method is always
     accessible via the pseuodoVariable called 'thisContext'.
-    The actual implementation uses the machines stack for this, building real
-    contexts on demand only, whenever a contexts is needed. Also, initially these are
+    The actual implementation uses the machine's stack for this, building real
+    contexts on demand only, whenever a context is needed. Also, initially these are
     allocated on the stack and only moved to the heap, when a context outlives its
     activation.
 
     For both method- and block-contexts, the layout is the same.
     For method contexts, the home-field is nil, while for block contexts the home-
     field is either the context of its surrounding block (i.e. the context of the
-    block, in which the receiving block was created, if its a nested block) or of
+    block, in which the receiving block was created, if it's a nested block) or of
     its home method.
 
     Cheap blocks are blocks which do not refer to any locals or the receiver (currently),