--- a/ObjMem.st	Fri Dec 15 00:05:12 1995 +0100
+++ b/ObjMem.st	Fri Dec 15 13:47:55 1995 +0100
@@ -13,17 +13,17 @@
 Object subclass:#ObjectMemory
 	 instanceVariableNames:''
 	 classVariableNames:'InternalErrorHandler UserInterruptHandler TimerInterruptHandler
-                SpyInterruptHandler StepInterruptHandler
-                ExceptionInterruptHandler ErrorInterruptHandler
-                MemoryInterruptHandler SignalInterruptHandler
-                ChildSignalInterruptHandler DisposeInterruptHandler
-                RecursionInterruptHandler IOInterruptHandler
-                CustomInterruptHandler RegisteredErrorInterruptHandlers
-                InterruptLatencyMonitor AllocationFailureSignal
-                MallocFailureSignal LowSpaceSemaphore IncrementalGCLimit
-                FreeSpaceGCLimit FreeSpaceGCAmount BackgroundCollectProcess
-                BackgroundFinalizationProcess FinalizationSemaphore Dependents
-                ImageName ChangeFileName MaxInterruptLatency InterruptLatencyGoal'
+		SpyInterruptHandler StepInterruptHandler
+		ExceptionInterruptHandler ErrorInterruptHandler
+		MemoryInterruptHandler SignalInterruptHandler
+		ChildSignalInterruptHandler DisposeInterruptHandler
+		RecursionInterruptHandler IOInterruptHandler
+		CustomInterruptHandler RegisteredErrorInterruptHandlers
+		InterruptLatencyMonitor AllocationFailureSignal
+		MallocFailureSignal LowSpaceSemaphore IncrementalGCLimit
+		FreeSpaceGCLimit FreeSpaceGCAmount BackgroundCollectProcess
+		BackgroundFinalizationProcess FinalizationSemaphore Dependents
+		ImageName ChangeFileName MaxInterruptLatency InterruptLatencyGoal'
 	 poolDictionaries:''
 	 category:'System-Support'
 !
@@ -176,7 +176,7 @@
 "
     Currently, Smalltalk/X uses a two-level memory hierachy (actually, there
     are more memory regions used for stack, permanent objects, symbols etc.
-    but for the following discussion, these are not of interrest).
+    but for the following discussion, these are not of interest).
 
   newSpace:
 
@@ -201,7 +201,7 @@
     unnoticed (typically, it takes some 5 to 50ms to perform a scavenge, 
     depending on how many live objects are in the newspace).
 
-    Interrestingly, the scavenger performs better, if many garbage objects
+    Interestingly, the scavenger performs better, if many garbage objects
     are to be reclaimed, since less object-copying has to be done. Therefore,
     the best-case scavenge time is almost zero, if there is only garbage in
     the newSpace. In contrast, the worst-case is when all newSpace objects are still
@@ -545,7 +545,7 @@
     are also implemented in the Object class - thus anything can be defined
     as interrupt handler. However, the VM will not send any
     interrupt message, if the corresonding handler object is nil
-    (which means that nil is a bad choice, if you are interrested in the event).
+    (which means that nil is a bad choice, if you are interested in the event).
 
     Interrupt processing is not immediately after the event arrives: there
     are certain ``save-places'' at which this handling is performed
@@ -3218,6 +3218,6 @@
 !ObjectMemory class methodsFor:'documentation'!
 
 version
-    ^ '$Header: /cvs/stx/stx/libbasic/Attic/ObjMem.st,v 1.82 1995-12-07 22:03:22 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libbasic/Attic/ObjMem.st,v 1.83 1995-12-15 12:47:36 cg Exp $'
 ! !
 ObjectMemory initialize!