From: gpercival <gpercival>
Date: Sat, 30 Oct 2004 21:41:06 +0000 (+0000)
Subject: Minor editing.
X-Git-Tag: release/2.5.23~1060
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=22f442b5cebe20c4d65e8340cca4dc1553819ced;p=lilypond.git

Minor editing.
---

diff --git a/ChangeLog b/ChangeLog
index a373de07de..4bcec916f9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -6,6 +6,8 @@
 	* Documentation/user/changing-defaults.itely: clarify paper size commands,
 	add missing subsubtitle entry to Creating titles.
 
+	* Documentation/user/tutorial.itely: change 3.0 references to 2.4.
+
 2004-10-30  Han-Wen Nienhuys  <hanwen@xs4all.nl>
 
 	* scripts/convert-ly.py (conv): fixed \context Foo = mixedCaps
diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index d18ea8ae71..294ccbdb8a 100644
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -901,7 +901,7 @@ ignored.  The following fragment shows possible uses for comments
 %@}
 @end example
 
-@c  TODO   post-3.0 reorg
+@c  TODO   post-2.4 reorg
 @c   This is good info, but I wouldn't call it a comment.  IMO it should
 @c   be moved somewhere else.
 
@@ -909,10 +909,10 @@ ignored.  The following fragment shows possible uses for comments
 
 There is a special statement that is a kind of comment.  The @code{\version}
 statement marks for which version of LilyPond the file was written.
-To mark a file for version 3.0.0, use
+To mark a file for version 2.4.0, use
 
 @example
-  \version "3.0.0"
+  \version "2.4.0"
 @end example
 
 @noindent