Fixes for README from Joel Kulesza.

Fixes #11250.

diff --git a/README b/README
index 57642dc534dcd7f7f79b2d8fadd25b7401f8b16b..2429045018ab6a6ddf0e4c67fd908dc9ea3f657c 100644 (file)
--- a/README
+++ b/README
@@ -12,7 +12,7 @@ What is LyX?
     legendary TeX typesetting engine makes you look good.
 
     On screen, LyX looks like any word processor; its printed output
-    -- or richly cross-referenced PDF, just as readily produced --
+    --- or richly cross-referenced PDF, just as readily produced ---
     looks like nothing else. Gone are the days of industrially bland
     .docs, all looking similarly not-quite-right, yet coming out
     unpredictably different on different printer drivers. Gone are the
@@ -26,7 +26,7 @@ What is LyX?
 What do I need to run LyX?
 
     Either:
-    * a Unix-like system (including Windows with cygwin)
+    * a Unix-like system (including Windows with Cygwin)
     * Windows 2000 or newer
     * Mac OS 10.4 or newer
 
@@ -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.2.0 was the first stable
     release in the 2.2-series of LyX. At the time of writing, the
-    latest maintenance release in the 2.2-series was LyX 2.2.3.
+    latest maintenance release in the 2.2-series is LyX 2.2.4.
 
     Please note that maintenance releases are designed primarily to
     fix bugs, and that the file format will _never_ change due to a
@@ -52,16 +52,16 @@ How does the LyX version scheme work?
     users may want to give a ''release candidate'' a try. This is a
     release that should be stable enough for daily work, but yet may
     be potentially unstable. If no major bugs are found, the release
-    candiate is soon released as the first stable release in a a new
+    candidate is soon released as the first stable release in a new
     series. To summarize, there are three possible types of file names
     that are of interest to normal users:
 
-       lyx-2.2.0.tar.gz     -- stable release, first in the 2.2-series
-       lyx-2.2.3.tar.gz     -- fifth maintenance release of LyX 2.2
-       lyx-2.3.0rc1.tar.gz  -- potentially unstable release candidate
+       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.0rc1.tar.gz  -- potentially unstable release candidate
 
-    Note that the goal is not parallel development as for the linux
-    kernel --the team is too small to afford that-- but rather to
+    Note that the goal is not parallel development as for the Linux
+    kernel --- the team is too small to afford that --- but rather to
     include all the simple and safe bug fixes. This is so that the
     maintenance burden on us is not too high, and so that system
     administrators can install new releases without fear. Experience
@@ -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.2.4dev     -- this is the stable branch on which maintenance
-               release 2.2.4 will eventually be tagged.
-       2.3.0dev     -- this is the main branch on which stable
-               release 2.3.0 will eventually be tagged.
+       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.
 
 What's new?