Update README

diff --git a/README b/README
index 3d8da5aeea070d980774a1c627910d31341f4531..aa30c75d215c43f7041e321287d179a85064219a 100644 (file)
--- a/README
+++ b/README
@@ -30,8 +30,8 @@ What do I need to run LyX?
     * Windows 7 or newer
     * Mac OS 10.13 or newer
 
-    A decent LaTeX2e installation (e.g. TeX Live for Linux, MikTeX for
-    Windows).
+    A decent LaTeX2e installation (e.g. TeXLive for Linux, TeXLive or 
+    MikTeX for Windows, MacTeX for OSX).
 
     Python (2.7 or 3.5 and newer) to convert old LyX files and for
     helper scripts.
@@ -42,7 +42,7 @@ How does the LyX version scheme work?
     number "2.x.y" indicates a stable release '2.x', maintenance
     release 'y'.  In other words, LyX 2.3.0 was the first stable
     release in the 2.3-series of LyX. At the time of writing, the
-    latest maintenance release in the 2.3-series is LyX 2.3.7.
+    latest maintenance release in the 2.3-series is LyX 2.3.8.
 
     Please note that maintenance releases are designed primarily to
     fix bugs, and that the file format will _never_ change due to a
@@ -56,8 +56,8 @@ How does the LyX version scheme work?
     series. To summarize, there are three possible types of file names
     that are of interest to normal users:
 
-       lyx-2.3.0.tar.gz     -- stable release, first in the 2.3-series
-       lyx-2.2.4.tar.gz     -- fourth maintenance release of LyX 2.2
+       lyx-2.4.0.tar.gz     -- stable release, first in the 2.4-series
+       lyx-2.3.4.tar.gz     -- fourth maintenance release of LyX 2.3
        lyx-2.4.0rc1.tar.gz  -- potentially unstable release candidate
 
     Note that the goal is not parallel development as for the Linux
@@ -71,10 +71,10 @@ How does the LyX version scheme work?
     If you get the source from Git, the version string will look like
     one of:
 
-       2.3.1dev     -- this is the stable branch on which maintenance
-               release 2.3.1 will eventually be tagged.
-       2.4.0dev     -- this is the main branch on which stable
-               release 2.4.0 will eventually be tagged.
+       2.4.1dev     -- this is the stable branch on which maintenance
+               release 2.4.1 will eventually be tagged.
+       2.5.0dev     -- this is the main branch on which stable
+               release 2.5.0 will eventually be tagged.
 
 What's new?