Patch 0005 from John

Fix nitpicks in Tutorial

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 4e1d289d4097307d973ea54445af7418054ee774..f31c98af414ddc2545741b4e740a4807cddfaa9f 100644 (file)
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -1500,7 +1500,7 @@ example from Handel's @notation{Judas Maccabæus}:
 @end lilypond
 
 Scores any more complex than this simple example are better
-produced by separating out the staff structure from the notes and
+produced by separating out the score structure from the notes and
 lyrics with variables.  These are discussed in @ref{Organizing
 pieces with variables}.
 
@@ -1625,7 +1625,7 @@ 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}, and it uses @code{\version} to
+program, @command{convert-ly}, and it uses @code{\version} to
 determine what rules to apply.  For details, see
 @rprogram{Updating files with convert-ly}.
 
@@ -1636,7 +1636,7 @@ determine what rules to apply.  For details, see
 The title, composer, opus number, and similar information are
 entered in the @code{\header} block.  This exists outside of the
 main music expression; the @code{\header} block is usually placed
-underneath the @ref{Version number}.
+underneath the version number.
 
 @example
 \version @w{"@version{}"}