--- a/Registry.st	Wed Mar 30 11:38:21 1994 +0200
+++ b/Registry.st	Wed Mar 30 11:41:04 1994 +0200
@@ -22,7 +22,7 @@
 COPYRIGHT (c) 1993 by Claus Gittinger
               All Rights Reserved
 
-$Header: /cvs/stx/stx/libbasic/Registry.st,v 1.5 1994-02-25 13:03:36 claus Exp $
+$Header: /cvs/stx/stx/libbasic/Registry.st,v 1.6 1994-03-30 09:41:00 claus Exp $
 written jun 93 by claus
 '!
 
@@ -30,20 +30,20 @@
 
 documentation
 "
-Registries provide an easy interface to using WeakArrays. 
-A class, which wants to be informed of instance-death, can put a created object
-into a registry. The registry will create a copy of the object, and
-watch out for death of the registered object. When it dies, the copy will
-be sent the message >>disposed.
-The trick with the shallow copy is especially nice, you can think of it as
-being the original object which died.
+    Registries provide an easy interface to using WeakArrays. 
+    A class, which wants to be informed of instance-death, can put a created object
+    into a registry. The registry will create a copy of the object, and
+    watch out for death of the registered object. When it dies, the copy will
+    be sent the message >>disposed.
+    The trick with the shallow copy is especially nice, you can think of it as
+    being the original object which died.
 
-All objects, which keep external resources (such as fileDescriptors, fonts, 
-colormap-entries etc.) should be registered, so that the underlying resource
-can be freed when the object goes away.
+    All objects, which keep external resources (such as fileDescriptors, fonts, 
+    colormap-entries etc.) should be registered, so that the underlying resource
+    can be freed when the object goes away.
 
-Of course, you too can use it to do whatever you need to do in case of the
-death of an object.
+    Of course, you too can use it to do whatever you need to do in case of the
+    death of an object.
 "
 ! !