Object.st
branchjv
changeset 20342 219a5a47e8b1
parent 20223 c5f855bca10b
parent 20253 da66d4066959
child 20344 152b525b5c63
--- a/Object.st	Sat Aug 13 06:52:18 2016 +0200
+++ b/Object.st	Tue Aug 23 09:54:28 2016 +0100
@@ -692,7 +692,6 @@
 ! !
 
 
-
 !Object methodsFor:'accessing'!
 
 _at:index
@@ -4260,7 +4259,7 @@
 error
     "{ Pragma: +optSpace }"
 
-    "report error that an error occured.
+    "report error that an error occurred.
      The error is reported by raising the Error exception,
      which is non-proceedable.
      If no handler has been setup, a debugger is entered."
@@ -4838,7 +4837,7 @@
                 Smalltalk fatalAbort:'no debugger'
             ].
 
-            "ok, an error occured while in the graphical debugger;
+            "ok, an error occurred while in the graphical debugger;
              lets try MiniDebugger"
             ^ MiniDebugger
         ].
@@ -5165,7 +5164,7 @@
 fpExceptionInterrupt
     "{ Pragma: +optSpace }"
 
-    "a floating point exception occured - this one
+    "a floating point exception occurred - this one
      has to be handled differently since it comes asynchronous
      on some machines (for example, on machines with a separate FPU
      or superscalar architectures. Also, errors from within primitive code
@@ -5299,7 +5298,7 @@
 signalInterrupt:signalNumber
     "{ Pragma: +optSpace }"
 
-    "unix signal occured - some signals are handled as Smalltalk Exceptions
+    "unix signal occurred - some signals are handled as Smalltalk Exceptions
      (SIGPIPE), others (SIGBUS) are rather fatal...
      In any case, IF a smalltalk-signal has been connected to the OS signal, that one is raised.
      Otherwise, a dialog is shown, asking the user on how to handle the signal.