--- a/CharacterArray.st	Mon Aug 01 11:25:15 2016 +0200
+++ b/CharacterArray.st	Mon Aug 01 11:28:46 2016 +0200
@@ -44,7 +44,7 @@
 "
     CharacterArray is a superclass for all kinds of Strings (i.e.
     (singleByte-)Strings, TwoByteStrings, UnicodeStrings
-    and whatever my come in the future.
+    and whatever may come in the future.
 
     This class is abstract, meaning that there are no instances of it;
     concrete subclasses define how the characters are stored (i.e. either as
@@ -53,30 +53,30 @@
     All this class does is provide common protocol for concrete subclasses.
 
     Notice:
-	internally, ST/X uses a unicode encoding for ALL characters - both
-	for individual chatacter entities and for strings of characters.
-	When reading/writing files in different encodings, the conversion is
-	done at read/write time by use of a CharacterEncoder instance.
-	These know how to convert to a wide range of encodings.
+        internally, ST/X uses a unicode encoding for ALL characters - both
+        for individual chatacter entities and for strings of characters.
+        When reading/writing files in different encodings, the conversion is
+        done at read/write time by use of a CharacterEncoder instance.
+        These know how to convert to a wide range of encodings.
 
     Also notice:
-	UTF8 and UTF16 are external encodings of a Unicode string; they are never
-	used internally. When interacting with a UTF8 interface (OS-API or files),
-	you should convert UTF8 into the internal full Unicode right at the interface.
-	Do not keep UTF8 around internally as String instances.
-	The reason is that UTF8 makes it harder to manipulate strings (for example
-	to insert/extract substrings or to get its size. Of such operations would
-	require a scan of the UTF8, which would complicate them).
-	Of course, there may be rare exceptions to this, for example if a file's contents
-	is treated as raw data, and the strings have to be copied/shuffled around only,
-	without any real processing on it.
+        UTF8 and UTF16 are external encodings of a Unicode string; they are never
+        used internally. When interacting with a UTF8 interface (OS-API or files),
+        you should convert UTF8 into the internal full Unicode right at the interface.
+        Do not keep UTF8 around internally as String instances.
+        The reason is that UTF8 makes it harder to manipulate strings (for example
+        to insert/extract substrings or to get its size. Of such operations would
+        require a scan of the UTF8, which would complicate them).
+        Of course, there may be rare exceptions to this, for example if a file's contents
+        is treated as raw data, and the strings have to be copied/shuffled around only,
+        without any real processing on it.
 
     [author:]
-	Claus Gittinger
+        Claus Gittinger
 
     [see also:]
-	String TwoByteString Unicode16String Uniode32String
-	StringCollection
+        String TwoByteString Unicode16String Uniode32String
+        StringCollection
 "
 ! !
 
@@ -8111,9 +8111,9 @@
 isUnicodeString
     "true if this is a 2- or 4-byte unicode string
      (i.e. not a single byte string).
-     Notice, that the name is misleading: 
+     Notice, that the name is misleading:
      all strings are use unicode encoding"
-     
+
     ^ false
 !