Timestamp.st
changeset 21699 b8eea1f574cf
parent 21388 c2cb27ae6231
child 21999 1f634836c816
--- a/Timestamp.st	Wed Apr 12 19:05:38 2017 +0200
+++ b/Timestamp.st	Wed Apr 12 19:05:40 2017 +0200
@@ -53,7 +53,7 @@
 
 documentation
 "
-    This class represents time values in milliSeconds starting some time in the past.
+    This class represents time values in milliseconds starting some time in the past.
     When printing and accessing values like #hour,
     the timestamp will be interpreted in the local timezone
     (as opposed to UtcTimestamp, which presents itself in UTC,
@@ -65,7 +65,7 @@
     the OperatingSystem bases its time upon - it is simply keeping the value(s)
     as returned from the OS.
     For conversion, these values are given back to the OS, which will know
-    how to convert these times. This has the advantage, that timestamps on files
+    how to convert these times. This has the advantage that timestamps on files
     (such as last-access-time or last-modification-time) can be handled transparently -
     especially when performing comparisons.
 
@@ -80,16 +80,16 @@
     instances of Timestamp can.
 
     Notice: this class was once called AbsoluteTime. Einstein told us in 1905, that talking
-    about a absolute time is not a good idea (at least in our universe). So the class
+    about an absolute time is not a good idea (at least in our universe). So in 2004 the class
     has been renamed to Timestamp which makes us more compatible to other ST dialects (e.g. VW)
-    AbsoluteTime is still kept as an alias for backward compatibility.
+    AbsoluteTime was kept as an alias for backward compatibility and was finally removed in 2017.
 
     Also Note:
-        On UNIX, osTime can only hold dates between 1970-01-01T00:00:00Z and 2038-01-19T00:00:00Z
+        On UNIX, osTime can only hold dates between 1970-01-01T00:00:00Z and 2038-01-19T03:14:07Z
         However, timestamp instances can now hold negative osTime values (which are timestamps
         before 1.1.1970 and greater than 4294967295 (2^32-1) for timestamps after 2038-01-19.
 
-        For dates before 1582 (when calendars were changed from Julian to Grgorian),
+        For dates before 1582 (when calendars were changed from Julian to Gregorian),
         the so called 'proleptic gregorian calendar' is used. This assumes leap years to continue in
         the past as if a gregorian calendar was used. Thus, 0000 is considered a leap year.