Doc: minor fixes from working.itely move.

diff --git a/Documentation/learning.tely b/Documentation/learning.tely
index 3a5632f7fee781bda971f6d4a031af44d6ecac87..f521f24db244d92e89b6ae2c40c7193a83ec8773 100644 (file)
--- a/Documentation/learning.tely
+++ b/Documentation/learning.tely
@@ -30,12 +30,12 @@
 
 @c * Preface::                        Preface.
 @c * Introduction::                   What, Why, How.
+@c * Working on LilyPond projects::   Discusses real-life usage.
 @menu
 * Introduction::                   Begin here.
 * Common notation::                A tutorial introduction.
 * Fundamental concepts::           Basic concepts required for reading the rest of this manual.
 * Tweaking output::                Introduction to modifying output.
-* Working on LilyPond projects::   Discusses real-life usage.
 
 Appendices
 
@@ -143,7 +143,7 @@ of this and other documentation.
 @include learning/common-notation.itely
 @include learning/fundamental.itely
 @include learning/tweaks.itely
-@include learning/working.itely
+@c @include learning/working.itely
 
 @include learning/templates.itely
 @include learning/scheme-tutorial.itely

diff --git a/Documentation/learning/common-notation.itely b/Documentation/learning/common-notation.itely
index 20ed56cbf5b6ccd4b920524604775fd013c8e249..2f7f304e11bc024b59e8909242f5b8abca0a8aa1 100644 (file)
--- a/Documentation/learning/common-notation.itely
+++ b/Documentation/learning/common-notation.itely
@@ -890,7 +890,7 @@ Note the curly brackets delimiting both the music and the lyrics.
 It is essential that the final syllable is separated from the
 terminating curly bracket by a space or a newline, or it will be
 assumed to be part of the syllable, giving rise to an obscure
-error, see @ref{Apparent error in ../ly/init.ly}.
+error, see @rprogram{Apparent error in ../ly/init.ly}.
 
 Note also the double angle brackets @w{@code{<< ... >>}} around the
 whole piece to show that the music and lyrics are to occur at the

diff --git a/Documentation/learning/fundamental.itely b/Documentation/learning/fundamental.itely
index ba3812db3b09060ca8949cf96d85c6bf5829fa77..3d6bf5ea0183cda8639c99084db11176a48d00b4 100644 (file)
--- a/Documentation/learning/fundamental.itely
+++ b/Documentation/learning/fundamental.itely
@@ -3006,7 +3006,7 @@ padText =
 @end lilypond
 
 Using variables is also a good way to reduce work if the
-LilyPond input syntax changes (see @ref{Updating old input files}).  If
+LilyPond input syntax changes (see @rprogram{Updating old input files}).  If
 you have a single definition (such as @code{\dolce}) for all your
 input files (see @ref{Style sheets}), then if the syntax changes, you
 only need to update your single @code{\dolce} definition,