diff --git a/README.md b/README.md
index 4951d00..651fee5 100644
--- a/README.md
+++ b/README.md
@@ -6,9 +6,8 @@ Copyright (c) Miletus, Louis-Aimé de Fouquières, 2017
 MIT licence applies
 
 MAC OS users: 
-1. You will have to insert manually (not with "import") the modules.
-1. Works possibly only on the latest versions of Excel (those which handle VBA).
-1. Check date conversion starting from 1904. It might work from 2 January 1904 only.
+1. This package only works on versions of Excel that handle VBA, i.e. from 2013 on.
+1. Check date conversion starting from 1904 if you use this epoch. Package might work from 2 January 1904 only.
 
 ## Installation
 1. Create a new Excel file, save as "Excel file with macros".
@@ -24,13 +23,13 @@ MAC OS users:
 * Hit "insert function" near the input bar.
 * Choose "custom" - you can see the functions.
 * If you choose one function, the parameter list appear (sorry, no help in this version).
-* Functions are sensitive to "1904 Calendar" (by default on MacOS)
+* Functions are sensitive to "1904 Calendar" (by default on MacOS in old versions of Excel)
 
 ## MilesianCalendar
 Compute a system date with Milesian date elements, or retrieve Milesian date elements from a system date.
-### MILESIAN_IS_LONG_YEAR (Y)
+### MILESIAN_IS_LONG_YEAR (Year)
 Boolean, whether the year is long (366 days) or not. 
-* Y, the year in question.
+* Year, the year in question.
 
 A long Milesian year is just before a leap year, e.g. 2015 is a long year because 2016 is a leap year. 
 With the Milesian calendar, a proposed rule is this:
@@ -38,7 +37,7 @@ years -4001, -801, 2399, 5599 etc. are *not* long. Elsewise the Gregorian rules
 e.g. 1899 is *not* long whereas 1999 is.
 Remember that by mistake, dates 1/1/1900 to 29/2/1900 are wrong under Microsoft Windows.
 
-### MILESIAN_YEAR_BASE (Y) 
+### MILESIAN_YEAR_BASE (Year) 
 Date of the day before the 1 1m of year Y, i.e. the "doomsday".
 
 ### Other functions of this module