tuned;
authorwenzelm
Sat, 01 Oct 2016 20:59:09 +0200
changeset 63985 4effb93c2a09
parent 63984 6ba87450894d
child 63986 c7a4b03727ae
tuned;
README_REPOSITORY
--- a/README_REPOSITORY	Sat Oct 01 20:58:59 2016 +0200
+++ b/README_REPOSITORY	Sat Oct 01 20:59:09 2016 +0200
@@ -46,16 +46,17 @@
 Introduction
 ------------
 
-Mercurial http://www.selenic.com/mercurial belongs to the current
-generation of source code management systems that follow the so-called
-paradigm of "distributed version control".  This is a terrific name
-for plain revision control without the legacy of CVS or SVN.  See also
-http://hginit.com/ for an introduction to the main ideas.  The
-Mercurial book http://hgbook.red-bean.com/ explains many more details.
+Mercurial http://www.selenic.com/mercurial belongs to source code
+management systems that follow the so-called paradigm of "distributed
+version control".  This means plain revision control without the
+legacy of CVS or SVN (and without the extra complexity introduced by
+git).  See also http://hginit.com/ for an introduction to the main
+ideas.  The Mercurial book http://hgbook.red-bean.com/ explains many
+more details.
 
-Mercurial offers great flexibility in organizing the flow of changes,
+Mercurial offers some flexibility in organizing the flow of changes,
 both between individual developers and designated pull/push areas that
-are shared with others.  This additional power demands some additional
+are shared with others.  This additional freedom demands additional
 responsibility to maintain a certain development process that fits to
 a particular project.
 
@@ -294,7 +295,7 @@
 
   ./bin/isabelle build -a  #regular test
 
-  ./bin/isabelle build -a -o document=pdf  #test with document preparation
+  ./bin/isabelle build -a -o document=pdf  #test with document preparation (optional)
 
   ./bin/isabelle build -a -j2 -o threads=4  #test on multiple cores (example)