--- a/Date.st	Wed Apr 12 16:39:15 2017 +0200
+++ b/Date.st	Wed Apr 12 19:05:38 2017 +0200
@@ -41,25 +41,25 @@
 
 documentation
 "
-    Instances of Date represent dates as year, month and day encoded in the 
-    (private & hidden) instance dateEncoding. The value found there is 
-    year*100*100 + month*100 + day 
+    Instances of Date represent dates as year, month and day encoded in the
+    (private & hidden) instance dateEncoding. The value found there is
+    year*100*100 + month*100 + day
     This makes magnitude-like comparison of dates easy, and the main components
     d,m,y are easily reconstructed (assuming, that this is the stuff most used).
-    Do not depend on the internal representation - 
+    Do not depend on the internal representation -
     it is private and not guaranteed for future versions.
 
-    The old representation used days since 1st Jan. 1901 internally - 
-    with the new implementation, it is possible to reasonably represent almost 
-    any Date.  
-    (which insurance companies will like,  
+    The old representation used days since 1st Jan. 1901 internally -
+    with the new implementation, it is possible to reasonably represent almost
+    any Date.
+    (which insurance companies will like,
      since they can now represent even very old people's birthday :-)
 
-    Notice: 
+    Notice:
         no correction for pre-Gregorian dates (< 1583) is done.
-        For dates before 1582 (when calendars were changed from Julian to Grgorian),
-        the so called 'proleptic gregorian calendar' is used. 
-        This assumes leap years to continue in the past as if a gregorian calendar was used. 
+        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.
 
     The printed representation of dates is controlled by resource definitions -
@@ -67,9 +67,9 @@
 
     Compatibility notice:
         due to historic reasons, there are some methods found twice
-        with different names in this class. The old ST/X methods will vanish 
-        over time, but kept for a while to support existing applications 
-        (the info on how these methods should be named  
+        with different names in this class. The old ST/X methods will vanish
+        over time, but kept for a while to support existing applications
+        (the info on how these methods should be named
          came somewhat late from the testers...).
 
         Please do not use methods marked as obsolete.