diff --git a/README b/README
index 31366b65..aad35161 100644
--- a/README
+++ b/README
@@ -6,10 +6,13 @@ ELinks is an advanced and well-established feature-rich text mode web
 customizable and can be extended via scripts. It is very portable and runs
 on a variety of platforms.
 
-The ELinks official website is available at http://elinks.or.cz/.
-Please see the SITES file for mirrors or other recommended sites.
-If you want to install ELinks on your computer, see the
-INSTALL file for further instructions.
+The ELinks official website is available at
+
+	http://elinks.or.cz/
+
+Please see the SITES file for mirrors or other recommended sites.  If you
+want to install ELinks on your computer, see the INSTALL file for further
+instructions.
 
 A good start point is documentation files available in doc/, especially the
 file named index.txt.
@@ -24,35 +27,40 @@ document.
 If you want to add a new language or update the translation for an existing
 one, please read po/README document.
 
-If you want to write some documentation, well you're welcomed ;)
+If you want to write some documentation, well, you're welcome! ;)
 
 
 
-History
-~~~~~~~
+Historical notes
+~~~~~~~~~~~~~~~~
 
-Initially, ELinks was a development version of Links (Lynx-like text WWW browser),
-with more liberal features policy and development style.
-
-Its purpose was to provide an alternative to Links, and to test and tune various
-new features, but still provide good rock-solid releases inside stable branches.
-If you are more interested, you can examine the Links website at
-http://links.sf.net/.
+Initially, ELinks was a development version of Links (Lynx-like text WWW
+browser), with more liberal features policy and development style.  Its purpose
+was to provide an alternative to Links, and to test and tune various new
+features, but still provide good rock-solid releases inside stable branches.
 
 Why not contribute to Links instead?  Well, first I made a bunch of patches for
-the original Links, but a significant number of them got refused  because
-Mikulas did not like them, as he just wouldn't have any use for them himself.
-He wants to keep Links with a relatively closed feature set and merge only new
-features which he himself needs.  It has advantages that the tree is very narrow
-and the code is small and contains very little bloat.  ELinks, on the contrary,
-aims to provide a full-featured web browser, superior to both lynx and w3m and
-with the possibilities of Konqueror and similar browsers. However, to prevent
-drastic bloating of the code, the development is driven in the course of
-modularization and separation of add-on modules (like cookies, bookmarks, ssl,
-lua etc).
+the original Links, but Mikulas wasn't around to integrate them, so I started
+releasing my fork. When he came back, a significant number of them got refused
+because Mikulas did not like them, as he just wouldn't have any use for them
+himself.  He wants to keep Links with a relatively closed feature set and merge
+only new features which he himself needs.  It has advantages that the tree is
+very narrow and the code is small and contains very little bloat.
 
-For more about ELinks history, see http://elinks.or.cz/history.html
+ELinks, on the contrary, aims to provide a full-featured web browser, superior
+to both lynx and w3m and with the power (but not slowness and memory usage) of
+Mozilla, Konqueror and similar browsers. However, to prevent drastic bloating
+of the code, the development is driven in the course of modularization and
+separation of add-on modules (like cookies, bookmarks, ssl, scripting etc).
 
+For more details about ELinks history, please see
+
+	http://elinks.or.cz/history.html
+
+If you are more interested in the history and various Links clones and versions,
+you can examine the website at
+
+	http://links.sf.net/