Fix incorrect references and broken links

diff --git a/Documentation/user/changing-defaults.itely b/Documentation/user/changing-defaults.itely
index a6fa5a48335bf345407e4b40d45310708af822f9..6180240af190e0dbd0abe5bd357f87e7cc7809ed 100644 (file)
--- a/Documentation/user/changing-defaults.itely
+++ b/Documentation/user/changing-defaults.itely
@@ -488,8 +488,8 @@ example which removes @code{Time_signature_engraver} and
 In the second staff there are no time signature or clef symbols.  This
 is a rather crude method of making objects disappear since it will affect
 the entire staff.  This method also influences the spacing, which may or
-may not be desirable.  A more
-sophisticated method of blanking objects is shown in @rlearning{Common tweaks}.
+may not be desirable.  More sophisticated methods of blanking objects
+are shown in @rlearning{Visibility and color of objects}.
 
 The next example shows a practical application.  Bar lines and time
 signatures are normally synchronized across the score.  This is done
@@ -1163,7 +1163,7 @@ can be modified.
 
 We have been talking of @emph{the} @code{Fingering} object, but actually it
 does not amount to much.  The initialization file (see
-@rlearning{Default files})
+@rlearning{Other sources of information})
 @file{scm/@/define@/-grobs@/.scm} shows the soul of the @q{object},
 
 @example

diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely
index 4ecad4b10537d24aa89da4fc0624c0320ba7a0c0..b849bcba002a5b7f89c38c540b2685843b94d27f 100644 (file)
--- a/Documentation/user/input.itely
+++ b/Documentation/user/input.itely
@@ -333,7 +333,7 @@ In order to use this feature, LilyPond must be invoked with
 @code{-dclip-systems}.  The clips are output as EPS files, and are
 converted to PDF and PNG if these formats are switched on as well.
 
-For more information on output formats, see @rprogram{Invoking LilyPond}.
+For more information on output formats, see @rprogram{Invoking lilypond}.
 
 
 @node Including LilyPond files

diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely
index 5cda80ffeb655ba5f2ab453728cfc4ebec119f02..5c4d3e88978c5efac18e76f53735bfd5ca0b7487 100644 (file)
--- a/Documentation/user/introduction.itely
+++ b/Documentation/user/introduction.itely
@@ -861,7 +861,7 @@ section explains how to upgrade input files from previous versions of
 LilyPond.
 
 @item
-@emph{@rprogram{lilypond-book}},
+@emph{@rprogram{LilyPond-book}},
 explains the details behind creating
 documents with in-line music examples, like this manual.
 

diff --git a/Documentation/user/percussion.itely b/Documentation/user/percussion.itely
index c3e598814fb31463d35146b6693c99f241e55be6..f358e4f6130aef4b3766e1f7f8e0a1b05d549688 100644 (file)
--- a/Documentation/user/percussion.itely
+++ b/Documentation/user/percussion.itely
@@ -126,7 +126,7 @@ down = \drummode { bassdrum4 snare8 bd r bd sn4 }
 @end lilypond
 
 The above example shows verbose polyphonic notation.  The short
-polyphonic notation, described in @rlearning{I'm seeing Voices},
+polyphonic notation, described in @rlearning{I'm hearing Voices},
 can also be used if the @internalsref{DrumVoice}s are instantiated
 by hand first.  For example,
 

diff --git a/Documentation/user/running.itely b/Documentation/user/running.itely
index 91510f12d0f86d81dfcf0447531fb9c7b1bc9319..33395322b14f347e05950c60a089588b2175d3c7 100644 (file)
--- a/Documentation/user/running.itely
+++ b/Documentation/user/running.itely
@@ -17,17 +17,17 @@ This chapter details the technicalities of running LilyPond.
 
 @menu
 * Normal usage::                
-* Command-line usage::          
-* Error messages::              
-* Updating files with convert-ly::  
-* Reporting bugs::              
+* Command-line usage::
+* Error messages::
+* Updating files with convert-ly::
+* Reporting bugs::
 @end menu
 
 
 @node Normal usage
 @section Normal usage
 
-Most users run LilyPond through a GUI; see @ruser{First steps} if
+Most users run LilyPond through a GUI; see @rlearning{First steps} if
 you have not read this already.
 
 
@@ -49,7 +49,13 @@ Describing how to use this part of an operating system is outside the
 scope of this manual; please consult other documentation on this topic
 if you are unfamiliar with the command-line.
 
+@menu
+* Invoking lilypond::
+* Command line options::
+* Environment variables::
+@end menu
 
+@node Invoking lilypond
 @subsection Invoking lilypond
 
 @cindex Invoking LilyPond
@@ -79,13 +85,13 @@ GUILE is not reset after processing a @code{.ly} file, so be careful
 not to change any system defaults from within Scheme.}
 
 In addition, the value of @code{output-suffix} will be inserted between
-the basename and the number.  An input file containing 
+the basename and the number.  An input file containing
 
 @example
 #(define output-suffix "violin")
-\book @{ @dots{} @} 
+\book @{ @dots{} @}
 #(define output-suffix "cello")
-\book @{ @dots{} @} 
+\book @{ @dots{} @}
 @end example
 
 @noindent
@@ -93,7 +99,7 @@ will output @var{base}@file{-violin.ps} and
 @var{base}@file{-cello-1.ps}.
 
 
-
+@node Command line options
 @subsection Command line options
 
 The following options are supported:
@@ -155,7 +161,7 @@ Running @code{lilypond -dhelp} will print all of the @code{-d} options
 available.
 
 @item paper-size
-This option sets the default paper-size, 
+This option sets the default paper-size,
 @example
 -dpaper-size=\"letter\"
 @end example
@@ -366,7 +372,7 @@ Show the warranty with which GNU LilyPond comes. (It comes with
 @strong{NO WARRANTY}!)
 @end table
 
-
+@node Environment variables
 @subsection Environment variables
 
 
@@ -636,7 +642,7 @@ bug by following the directions on
 
 @uref{http://lilypond.org/web/devel/participating/bugs}
 
-Please construct submit @ruser{Minimal examples}, of bug reports.  We do not
+Please construct and submit minimal examples of bugs in reports.  We do not
 have the resources to investigate reports which are not as small as possible.
 
 

diff --git a/Documentation/user/templates.itely b/Documentation/user/templates.itely
index 1aa874466b2b04ec2388ace63fdf45e0f969d7a4..77fc6ca41de34822cd362271764f7c4f115223ee 100644 (file)
--- a/Documentation/user/templates.itely
+++ b/Documentation/user/templates.itely
@@ -205,7 +205,7 @@ violin concerto as TchaikovskyPI, whereas perhaps you wish to print
 @appendixsec lilypond-book templates
 
 These templates are for use with @code{lilypond-book}.  If you're not familiar
-with this program, please refer to @rprogram{lilypond-book}.
+with this program, please refer to @rprogram{LilyPond-book}.
 
 @appendixsubsec LaTeX
 

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 0bd1a99c4ff0d4517d0de97d0e54fd1cbe565b54..ac3ab74558cbef06974295fca2ea17d34739fbd9 100644 (file)
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -1151,7 +1151,7 @@ of bar lines.
 
 @seealso
 
-Notation Reference: @ruser{Piano music}, 
+Notation Reference: @ruser{Keyboard instruments},
 @ruser{Displaying staves}.
 
 

diff --git a/Documentation/user/tweaks.itely b/Documentation/user/tweaks.itely
index 62a0caaba686b6dc4fc45da7e9d8b430242e35b2..dbaa7f766fdd26c5927a6a2a2144987a3c5b7160 100644 (file)
--- a/Documentation/user/tweaks.itely
+++ b/Documentation/user/tweaks.itely
@@ -2793,7 +2793,7 @@ But how do we merge notes in different voices together?  The
 index in the Notation Reference does not mention merging,
 but a search of the text for @q{merge} quickly leads us to
 the overrides for merging differently headed and differently
-dotted notes in @ruser{Collision Resolution}.  In our
+dotted notes in @ruser{Collision resolution}.  In our
 example we need to merge both types of note for the duration
 of the polyphonic section in bar 3, so using the information
 in the Notation Reference we add

diff --git a/Documentation/user/working.itely b/Documentation/user/working.itely
index 8077bb3a6068051f0ca8b6a16c35b7c448513d04..0e29d7bf6916d66dac27ac97eb59235e7224966e 100644 (file)
--- a/Documentation/user/working.itely
+++ b/Documentation/user/working.itely
@@ -79,8 +79,8 @@ quite frustrating to try to remember which version of LilyPond you were
 using a few years ago.  @command{convert-ly} requires you to declare
 which version of LilyPond you used.
 
-@item @strong{Include checks}: @ruser{Bar and barnumber checks},
-@ruser{Octave check}.  If you include checks every so often, then
+@item @strong{Include checks}: @ruser{Bar and bar number checks},
+@ruser{Octave checks}.  If you include checks every so often, then
 if you make a mistake, you can pinpoint it quicker.  How often is
 @q{every so often}?  It depends on the complexity of the music.
 For very simple music, perhaps just once or twice.  For very