Doc: NR 4.1.2: Reorganize nodes; link to 4.4.1.

[lilypond.git] / Documentation / notation / editorial.itely

diff --git a/Documentation/notation/editorial.itely b/Documentation/notation/editorial.itely
index a673cdd184bd9e53472b6f857be551a310237184..c83383359c698b30c5fdbc64a49967a88208340e 100644 (file)
--- a/Documentation/notation/editorial.itely
+++ b/Documentation/notation/editorial.itely
@@ -7,7 +7,7 @@
     Guide, node Updating translation committishes..
 @end ignore
 
-@c \version "2.12.0"
+@c \version "2.13.36"
 
 @node Editorial annotations
 @section Editorial annotations
@@ -149,7 +149,7 @@ Internals Reference:
 @funindex finger
 
 Fingering instructions can be entered using
-@var{note}-@var{digit}:
+@samp{@var{note}-@var{digit}}:
 
 @lilypond[verbatim,quote,relative=2]
 c4-1 d-2 f-4 e-3
@@ -311,10 +311,11 @@ e
 
 The full range of colors defined for X11 can be accessed by using
 the Scheme function @code{x11-color}.  The function takes one
-argument; this can be a symbol in the form @var{'FooBar} or a
-string in the form @var{"FooBar"}.  The first form is quicker to
-write and is more efficient.  However, using the second form it is
-possible to access X11 colors by the multi-word form of its name.
+argument; this can be a symbol in the form @code{'@var{FooBar}} or
+a string in the form @code{"@var{FooBar}"}.  The first form is
+quicker to write and is more efficient.  However, using the second
+form it is possible to access X11 colors by the multi-word form of
+its name.
 
 If @code{x11-color} cannot make sense of the parameter then the
 color returned defaults to black.
@@ -412,7 +413,7 @@ c2 \parenthesize <c e g>
 c2 <c \parenthesize e g>
 @end lilypond
 
-Non-note objects may be parenthesized as well. For articulations,
+Non-note objects may be parenthesized as well.  For articulations,
 a hyphen is needed before the @code{\parenthesize} command.
 
 @lilypond[verbatim,quote,relative=2]