Really minor fixes.

diff --git a/ChangeLog b/ChangeLog
index 94867e08b0bc4b9fc49e5098005330148bb19b50..55dc752c4cefb3df0d730503697a3f32afc4fcdf 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2005-05-06  Graham Percival  <gperlist@shaw.ca>
+
+       * Documentation/user/advanced-notation.itely, putting.itely,
+       tutorial.itely, global.itely, introduction.itely: really minor fixes.
+
 2005-05-06  Jan Nieuwenhuizen  <janneke@gnu.org>
 
        * mf/GNUmakefile (MFTRACE_FLAGS):

diff --git a/Documentation/user/advanced-notation.itely b/Documentation/user/advanced-notation.itely
index cd23b7a53aa5c0e9a1e89a1838f1b3eee4a39b70..5cfc3c86e9601652d3787a29913027b185f1d431 100644 (file)
--- a/Documentation/user/advanced-notation.itely
+++ b/Documentation/user/advanced-notation.itely
@@ -295,7 +295,6 @@ It is also possible to print dynamics in round parenthesis or square
 brackets.  These are often used for adding editorial dynamics.
 
 @lilypond[quote,verbatim,raggedright]
-\version "2.4.2"
 rndf = \markup{ \center-align {\line { \bold{\italic (}
   \dynamic f \bold{\italic )} }} }
 boxf = \markup{ \bracket { \dynamic f } }

diff --git a/Documentation/user/global.itely b/Documentation/user/global.itely
index 3cfaf886613608ea9a11a5de5ac50a69a04d5e56..df904fb230fc17fc18729bb34890c1b1ecbd0647 100644 (file)
--- a/Documentation/user/global.itely
+++ b/Documentation/user/global.itely
@@ -688,6 +688,8 @@ and texts are entered with a @code{\markup} block,
 @}
 @end example
 
+@cindex @code{\book}
+
 The movements and texts are combined together in a @code{\book} block,
 like
 

diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely
index 7aecfb286cba1965a63e5ba5946d6b9f4e65f05e..7d70a7108bb6c3232ccb467883159c233883d6c8 100644 (file)
--- a/Documentation/user/introduction.itely
+++ b/Documentation/user/introduction.itely
@@ -843,7 +843,7 @@ vary from system to system.  On occasion, this manual refers to
 initialization and example files.  Throughout this manual, we refer to
 input files relative to the top-directory of the source archive.  For
 example, @file{input/@/test/@/bla@/.ly} may refer to the file
-@file{lilypond@/-2.4.0/@/input/@/test/@/bla@/.ly}.  On binary packages
+@file{lilypond@/-2.6.0/@/input/@/test/@/bla@/.ly}.  On binary packages
 for the Unix platform, the documentation and examples can typically be
 found somewhere below @file{/usr/@/share/@/doc/@/lilypond/}.
 Initialization files, for example @file{scm/@/lily@/.scm}, or

diff --git a/Documentation/user/putting.itely b/Documentation/user/putting.itely
index 28f3e4a8aef579150d278a4aa9bc5a08c1cb4066..b5c6e1a249bfa4404495c62fba1e330bea78398e 100644 (file)
--- a/Documentation/user/putting.itely
+++ b/Documentation/user/putting.itely
@@ -31,7 +31,7 @@ problems:
 
 @itemize @bullet
 @item Include @code{\version} numbers in every file.  Note that all
-templates contain a @code{\version "2.4.0"} string.  We
+templates contain a @code{\version "2.6.0"} string.  We
 highly recommend that you always include the @code{\version}, no matter
 how small your file is.  Speaking from personal experience, it's
 quite frustrating to try to remember which version of LilyPond you were

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 0efc80eedfc0dd8aef7f08fcea9608948135fe04..714c2f445c9ed4b49107e80a2f821f603a549431 100644 (file)
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -904,7 +904,7 @@ ignored.  The following fragment shows possible uses for comments
 %@}
 @end example
 
-@c  TODO   post-2.4 reorg
+@c  TODO   post-2.6 reorg
 @c   This is good info, but I wouldn't call it a comment.  IMO it should
 @c   be moved somewhere else.
 
@@ -912,10 +912,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 2.4.0, use
+To mark a file for version 2.6.0, use
 
 @example
-\version "2.4.0"
+\version "2.6.0"
 @end example
 
 @noindent