Minor editing.

diff --git a/ChangeLog b/ChangeLog
index a373de07de49e8dfb8feef5b0c044b14b181e28e..4bcec916f9214b309a6b074bc68d61e8dcd26a1d 100644 (file)
--- 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 d18ea8ae7194b911d9236a582b7c1f09409872b0..294ccbdb8a93b8ce0ae242525b8e158ac59374a5 100644 (file)
--- 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