Merge branch 'Rmaster' into lilypond/translation

[lilypond.git] / Documentation / user / tutorial.itely

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 2bcdd07b1c6ee527ed185cf7c1aede606a0eda8b..0c2d2cfdbade111971954549a9d6bce8edc90012 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
@@ -1494,3 +1494,6 @@ used in an example, read the HTML version (if you are not already doing
 so) and click on the picture of the music.  This will display the exact
 input that LilyPond used to generate this manual.
 
+For information about the structure of the rest of the manual, see
+@ref{About this manual}.
+