Linking to ^_ section.

diff --git a/Documentation/user/expressive.itely b/Documentation/user/expressive.itely
index deefe162c35eeb96b51bfcf7256cd23fced9912e..c1c17718283fb19dd56dbd7726d14049f70cdf53 100644 (file)
--- a/Documentation/user/expressive.itely
+++ b/Documentation/user/expressive.itely
@@ -69,7 +69,8 @@ c->   c-.  c-_
 
 The marks are placed automatically by default (either above or
 below the note), but their positions can be manually @q{forced}
-@c above or below notes as well.  For details, see @ref{Up and down}.
+above or below notes as well.  For details, see
+@ref{Controlling direction and placement}.
 
 @cindex espressivo
 @cindex fermata
@@ -180,7 +181,8 @@ like @code{c4\ff}.  The available dynamic marks are @code{\ppppp},
 @code{\mf}, @code{\f}, @code{\ff}, @code{\fff}, @code{\ffff},
 @code{\fp}, @code{\sf}, @code{\sff}, @code{\sp}, @code{\spp},
 @code{\sfz}, and @code{\rfz}.  The dynamic marks can be placed
-@c above or below the staff: For details, see @ref{Up and down}.
+above or below the staff: For details, see
+@ref{Controlling direction and placement}.
 
 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
 c2\ppp c\mp
@@ -387,7 +389,7 @@ Just as with ties, the direction of a slur can be specified with
 @code{\slur@emph{DIR}}, where @code{@emph{DIR}} is either
 @code{Up}, @code{Down}, or @code{Neutral} (@code{Neutral} is the
 default).  The shorthands are also available: For details, see
-@c @ref{Up and down}.
+@ref{Controlling direction and placement}.
 
 @lilypond[verbatim,quote,ragged-right,fragment,relative=2]
 c4_( c) c^( c)
@@ -454,7 +456,7 @@ normal slur.  However, they are treated as different objects.  A
 @code{\slurUp} will have no effect on a phrasing slur; instead,
 use @code{\phrasingSlurUp}, @code{\phrasingSlurDown}, and
 @code{\phrasingSlurNeutral}.  The shorthands work for phrasing
-@c slurs as well: For details, see @ref{Up and down}.
+slurs as well: For details, see @ref{Controlling direction and placement}.
 
 You cannot have simultaneous phrasing slurs.
 

diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely
index a9ad9a80ddab0f9ca99842134a2ca8eeb198c489..9a11aeb5612e6a64e1600f2cd166b568f5536ba2 100644 (file)
--- a/Documentation/user/input.itely
+++ b/Documentation/user/input.itely
@@ -511,12 +511,12 @@ sections.
 @section Common syntax issues TODO name?
 
 @menu
-* Controlling direction::       
+* Controlling direction and placement::  
 * Distances and measurements MAYBE MOVE::  
 @end menu
 
-@node Controlling direction
-@subsection Controlling direction
+@node Controlling direction and placement
+@subsection Controlling direction and placement
 
 TODO: everything
 

diff --git a/Documentation/user/policy.txt b/Documentation/user/policy.txt
index 229419de9f5f9e57a79dd070fc8147dcd5164bb9..fd2c895cbb6532c933278dc947640d3d7f39babc 100644 (file)
--- a/Documentation/user/policy.txt
+++ b/Documentation/user/policy.txt
@@ -45,8 +45,9 @@ material in the Learning Manual (particularly ``Fundamental
 Concepts''), so do not repeat that material in each section of
 this book.  Also watch out for common constructs, like ^ - _ for
 directions -- those are explained in NR 3.  In NR 1, you can
-mention that "dynamics (or whatever) may be placed above or below
-the staff, for details see @ref{Up and down}".
+write:
+Dynamics (or whatever) may be manually placed above or below the
+staff, for details see @ref{Controlling direction and placement}".
 
 Most tweaks should be added to LSR and not placed directly in the
 .itely file.  In some cases, tweaks may be placed in the main

diff --git a/Documentation/user/rhythms.itely b/Documentation/user/rhythms.itely
index 2da0f2c048527dabcd9b12641123acfb7ce5697a..b2f9977731f11178c4d93f520999fe7b0ac1c621 100644 (file)
--- a/Documentation/user/rhythms.itely
+++ b/Documentation/user/rhythms.itely
@@ -515,7 +515,7 @@ be entered using @code{\laissezVibrer}:
 @end lilypond
 
 The vertical placement of ties may be controlled; see
-@ref{Controlling direction}.
+@ref{Controlling direction and placement}.
 
 @quotation
 DELETE THIS ?