--- a/ImmArray.st	Mon Jul 03 04:38:59 1995 +0200
+++ b/ImmArray.st	Sun Jul 23 04:24:56 1995 +0200
@@ -37,21 +37,21 @@
 
 version
 "
-$Header: /cvs/stx/stx/libcomp/Attic/ImmArray.st,v 1.5 1995-07-03 02:38:27 claus Exp $
+$Header: /cvs/stx/stx/libcomp/Attic/ImmArray.st,v 1.6 1995-07-23 02:23:34 claus Exp $
 "
 !
 
 documentation
 "
     By default, array literals in smalltalk are mutable objects. That
-    may lead to some subtle (and hard to find errors) if some method passes
+    may lead to some subtle (and hard to find errors), if some method passes
     a literal array constant as argument to someone else, who changes the
     array using at:put: like messages. Since the array object is kept in 
     the first methods literals, the array constant has now been changed without
-    having the methods sourcecode reflect this. Thus, method the methods will
+    having the methods sourcecode reflect this. Thus, the method will
     behave differently from what its source may make you think.
 
-    To help finding this kind of 'feature/bug', the compiler class can be
+    To help finding this kind of 'feature/bug', the compiler can be
     configured to create instances of this ImmutableArray instead of Arrays
     for array literals. Instances of ImmutableArray catch storing accesses and
     enter the debugger. Although useful, this feature is disabled by default
@@ -60,7 +60,7 @@
      a workspace somewhat strange: you cannot modify it any longer).
 
     Turn the ImmutableArray feature on by setting the Parsers class variable
-    'ArraysAreImmutable' to true.
+    'ArraysAreImmutable' to true or use the new launchers settings menu.
 "
 ! !