From: Trevor Daniels <t.daniels@treda.co.uk>
Date: Fri, 8 Aug 2008 17:15:53 +0000 (+0100)
Subject: Patch 0005 from John
X-Git-Tag: release/2.11.56-1~2^2~43^2~5
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=2ebc47db205df77ee0e1eb3d5f4ac4f5ebc46af8;p=lilypond.git

Patch 0005 from John

Fix nitpicks in Tutorial
---

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 4e1d289d40..f31c98af41 100644
--- 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{}"}