--- a/UnlimitedSharedQueue.st	Fri Jun 21 13:13:50 2019 +0200
+++ b/UnlimitedSharedQueue.st	Tue Jun 25 07:29:04 2019 +0200
@@ -1,3 +1,5 @@
+"{ Encoding: utf8 }"
+
 "
  COPYRIGHT (c) 2016 by eXept Software AG
               All Rights Reserved
@@ -48,9 +50,10 @@
     instances of me grow the underlying container, so the writer will never block
     (of course, the reader will still block in #next, if the queue is empty).
     
-    This kind of queue is needed if the reader process itself possibly wants to
-    add more to the queue. For this, a limited sharedQueue may block the reader,
-    if this reader process cannot add a new element.
+    This kind of queue is eg. needed if the reader process itself wants to
+    add more (write) to the queue. 
+    For this, a limited sharedQueue would block the reader process (when writing),
+    if the queue is full, which would lead to a deadlock situation.
 
     [author:]
         Claus Gittinger