Minor fixes from mailist.

diff --git a/Documentation/user/basic-notation.itely b/Documentation/user/basic-notation.itely
index eadb2b71a620c8fdba07fb6c08df77260f6d8aa1..d3f61f2bc8a980d3b80934aa62f775682a247696 100644 (file)
--- a/Documentation/user/basic-notation.itely
+++ b/Documentation/user/basic-notation.itely
@@ -991,6 +991,8 @@ articulations, just like simple notes
 For more information about chords, see @ref{Chord names}.
 
 
+@c  I don't like having this here, but I can't think of
+@c  anywhere else to put it.  :(   -gp
 @node Stems
 @subsection Stems
 

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 049407ebcbf0617199364a9e3cbd3b55a5563d06..292df275e41759c7ec109abd582b3122f7614ea4 100644 (file)
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -1280,20 +1280,20 @@ of the manual.
 @subsection Version number
 
 @cindex versioning
-The @code{\version} statement marks for which version of LilyPond the file
-was written.  To mark a file for version 2.10.1, place
+The @code{\version} statement records the version of LilyPond that was
+used to write the file:
 
 @example
 \version "2.11.23"
 @end example
 
 @noindent
-at the top of your LilyPond file.
+by convention, this is placed at the top of your LilyPond file.
 
-These annotations make future upgrades of LilyPond go more
-smoothly.  Changes in the syntax are handled with a special program,
-@file{convert-ly} (see @rprogram{Updating files with convert-ly}), and it uses
-@code{\version} to determine what rules to apply.
+These annotations make future upgrades of LilyPond go more smoothly.
+Changes in the syntax are handled with a special program,
+@file{convert-ly} (see @rprogram{Updating files with convert-ly}), and
+it uses @code{\version} to determine what rules to apply.
 
 
 @node Adding titles