From: John Mandereau <john.mandereau@gmail.com>
Date: Thu, 26 Jun 2008 06:43:27 +0000 (+0200)
Subject: Nits in tutorial
X-Git-Tag: release/2.11.50-1~21
X-Git-Url: https://git.donarmstrong.com/lilypond.git?a=commitdiff_plain;h=657ee139307f6175a177a328684a6a29133c37a3;p=lilypond.git

Nits in tutorial
---

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 44dde8643a..7580936dc8 100644
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -177,7 +177,7 @@ You will see something resembling:
 
 @example
 lilypond test.ly
-GNU LilyPond 2.12.0
+GNU LilyPond @version{}
 Processing `test.ly'
 Parsing...
 Interpreting music...
@@ -504,7 +504,7 @@ comments:
   are ignored, since they are in a
   block comment.
 
-  g g f f e e d d c2
+  f f e e d d c2
 %@}
 @end example
 
@@ -518,7 +518,7 @@ LilyPond input must be surrounded by @{ @} marks or a
 @w{@code{\relative c'' @{ ... @}}}, as we saw in @ref{Working on
 input files}.  For the rest of this manual, most examples will
 omit this.  To replicate the examples, you may copy and paste the
-displayed input but you @strong{must} add the
+displayed input, but you @strong{must} add the
 @w{@code{\relative c'' @{ @}}} like this:
 
 @example
@@ -560,7 +560,6 @@ cut-&-pastable section} to the bottom of the file.
 
 @seealso
 
-
 There are more tips for constructing input files in
 @ref{Suggestions for writing LilyPond input files}.  But it might be
 best to read through the rest of the tutorial first.