Doc: Clarify \relative inside \repeat issue.

[lilypond.git] / Documentation / notation / changing-defaults.itely

diff --git a/Documentation/notation/changing-defaults.itely b/Documentation/notation/changing-defaults.itely
index c9062ecdf3e47c69b113101758acb1fb983ccc06..e743ac1683e5f20269f6f0eaf084c9a7d1c9c8ab 100644 (file)
--- a/Documentation/notation/changing-defaults.itely
+++ b/Documentation/notation/changing-defaults.itely
@@ -1468,7 +1468,7 @@ or crashes, or both.
 
 
 @node The set command
-@subsection The @code{\set} command
+@subsection The @code{@bs{}set} command
 
 @cindex properties
 @funindex \set
@@ -2208,7 +2208,7 @@ The default order in which contexts are laid out and the
 @qq{accepts} list can be changed, see @ref{Aligning contexts}.
 
 @seealso
-Learning Manual:
+Usage Manual:
 @rprogram{An extra staff appears}.
 
 
@@ -2979,7 +2979,7 @@ The locations of the end-points of the spanner are computed
 on-the-fly for every graphic object, but it is possible to
 override these:
 
-@c FIXME Complete
+@c TODO Complete
 @lilypond[relative=2,ragged-right,verbatim,fragment]
 e2 \glissando f
 \once \override Glissando #'(bound-details right Y) = #-2
@@ -3079,7 +3079,7 @@ Learning Manual:
 
 Notation Reference:
 @ref{Explaining the Internals Reference},
-@ref{Modifying properties},
+@ref{Modifying properties}.
 
 Installed Files:
 @file{scm/@/define@/-grobs@/.scm}.
@@ -3411,7 +3411,7 @@ e
 @node Vertical grouping of grobs
 @subsection Vertical grouping of grobs
 
-@c FIXME Expand this section
+@c TODO Expand this section
 
 The VerticalAlignment and VerticalAxisGroup grobs work together.
 VerticalAxisGroup groups together different grobs like Staff, Lyrics,
@@ -3612,7 +3612,11 @@ where
 
 Common variable types are described in @ref{Common argument types}.
 A more complete description of variable types is found in
-@rextend{Music function syntax}.
+@rextend{Music function syntax}.  The complete list of defined variable
+types is found in the @var{type-p-name-alist} entry of
+@file{scm/lily.scm}.
+
+@c TODO -- find an automatic way of documenting the type-p-name-alist
 
 The @code{parser} and @code{location} arguments are mandatory,
 and are used in some advanced situations as described in