Fix nitpicks in user manual

- fix index entries
- replace "grace section" with "grace expression"
- add some comments for nitpicks I am not sure about

diff --git a/Documentation/user/basic-notation.itely b/Documentation/user/basic-notation.itely
index 40b089878f186c945e10f375a8f6acbef1135e43..832465ecb104f29d10e913739221b2c34cb5e84a 100644 (file)
--- a/Documentation/user/basic-notation.itely
+++ b/Documentation/user/basic-notation.itely
@@ -2347,16 +2347,17 @@ behavior can be changed by setting @code{breakable}.
 @cindex kneed beams
 @cindex auto-knee-gap
 
-
-@refbugs
-
 Kneed beams are inserted automatically when a large gap is detected
 between the note heads.  This behavior can be tuned through the
 @code{auto-knee-gap} object.
 
+
+@refbugs
+
 Automatically kneed cross-staff beams cannot be used together with
 hidden staves.  See @ref{Hiding staves}.
 
+@c Is this still true with skyline spacing stuff? -J.Mandereau
 Beams do not avoid collisions with symbols around the notes, such as
 texts and accidentals.
 
@@ -2396,6 +2397,8 @@ c4 \grace c16 c4
 Unlike @code{\acciaccatura} and @code{\appoggiatura}, the
 @code{\grace} command does not start a slur.
 
+@cindex timing, internal
+
 Internally, timing for grace notes is done using a second, @q{grace}
 timing.  Every point in time consists of two rational numbers: one
 denotes the logical time, one denotes the grace timing.  The above
@@ -2467,9 +2470,9 @@ The same effect can be achieved manually by doing
 By adjusting the duration of the skip note (here it is a half-note),
 the space between the main-note and the grace is adjusted.
 
-A @code{\grace} section will introduce special typesetting settings,
+A @code{\grace} music expression will introduce special typesetting settings,
 for example, to produce smaller type, and set directions.  Hence, when
-introducing layout tweaks, they should be inside the grace section,
+introducing layout tweaks, they should be inside the grace expression,
 for example,
 
 @lilypond[quote,ragged-right,fragment,verbatim,relative=2]
@@ -2484,12 +2487,12 @@ for example,
 @end lilypond
 
 @noindent
-The overrides should also be reverted inside the grace section.
+The overrides should also be reverted inside the grace expression.
 
-The layout of grace sections can be changed throughout the music using
-the function @code{add-grace-property}.  The following example
-undefines the @code{Stem} direction for this grace, so
-that stems do not always point up.
+The layout of grace expressions can be changed throughout the music
+using the function @code{add-grace-property}.  The following example
+undefines the @code{Stem} direction for this grace, so that stems do not
+always point up.
 
 @example
 \new Staff @{
@@ -2540,7 +2543,7 @@ Program reference: @internalsref{GraceMusic}.
 
 @refbugs
 
-A score that starts with a @code{\grace} section needs an explicit
+A score that starts with a @code{\grace} expression needs an explicit
 @code{\new Voice} declaration, otherwise the main note and the grace
 note end up on different staves.
 
@@ -2634,6 +2637,7 @@ c\fermata c^\fermata c_\fermata
 @cindex organ pedal marks
 @cindex turn
 @cindex open
+@cindex stopped
 @cindex flageolet
 @cindex reverseturn
 @cindex trill
@@ -2643,7 +2647,6 @@ c\fermata c^\fermata c_\fermata
 @cindex prallmordent
 @cindex prall, up
 @cindex prall, down
-@cindex mordent
 @cindex thumb marking
 @cindex segno
 @cindex coda
@@ -2966,6 +2969,7 @@ typeset with the command @code{pitchedTrill},
 f\stopTrillSpan
 @end lilypond
 
+@noindent
 The first argument is the main note.  The pitch of the second
 is printed as a stemless note head in parentheses.
 
@@ -3063,6 +3067,8 @@ in both staves and set
 >>
 @end lilypond
 
+@c TODO: cross-voice arpeggio example?
+@c such an example is already in LSR -J.Mandereau
 
 @refcommands
 
@@ -3124,7 +3130,6 @@ for repetitions.
 @subsection Repeat types
 
 @cindex repeats
-@funindex \repeat
 
 The following types of repetition are supported
 
@@ -3158,6 +3163,7 @@ declared within a @code{Voice} context.
 @cindex volta
 @cindex prima volta
 @cindex seconda volta
+@funindex \repeat
 
 LilyPond has one syntactic construct for specifying different types of
 repeats.  The syntax is

diff --git a/Documentation/user/putting.itely b/Documentation/user/putting.itely
index e1e2b0b2b118f30020c10bc864e4c881278e6d0b..f715c8c0c1153f592baf1106220bb3fb4d11ec02 100644 (file)
--- a/Documentation/user/putting.itely
+++ b/Documentation/user/putting.itely
@@ -293,7 +293,7 @@ often placed above the @code{\score}.  That's just
 another shorthand that LilyPond accepts.
 
 @cindex variables
-@cindex indentifiers
+@cindex identifiers
 
 Another great shorthand is the ability to define
 variables.  All the templates use this

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 5c8c2aaedf8e955df25320fe99dff0f133641121..77dd3ac415d265d8357a1d35aeebd60ef841c81b 100644 (file)
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -651,7 +651,6 @@ d4( c16) cis( d e c cis d) e( d4)
 @cindex phrasing slurs
 @subheading Phrasing slurs
 
-@cindex phrasing slurs
 Slurs to indicate longer phrasing can be entered with @code{\(} and
 @code{\)}.  You can have both legato slurs and phrasing slurs at the
 same time, but you cannot have simultaneous slurs or simultaneous