From: James Lowe <james.lowe@datacore.com>
Date: Mon, 12 Dec 2011 20:56:27 +0000 (+0000)
Subject: Doc: NR trivial word change for footnotes
X-Git-Tag: release/2.15.22-1~13
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=ab8ce7efcdc5af77452197ab62b4e875c790a5f5;p=lilypond.git

Doc: NR trivial word change for footnotes

Requested by George Xu to state more explicitly that
top level markups as treated as grobs.

Single word change in two places. Pushing without review.
---

diff --git a/Documentation/notation/input.itely b/Documentation/notation/input.itely
index 9df1a8a9d1..2293b20f32 100644
--- a/Documentation/notation/input.itely
+++ b/Documentation/notation/input.itely
@@ -1042,7 +1042,7 @@ indicator and so footnotes are created during compilation.
 
 Of the two commands used to create automatic footnotes, use
 @code{\autoFootnoteGrob} for individual grobs (i.e. note heads, stems,
-slurs, dynamics including @code{\markup} when using @code{TextScripts});
+slurs, dynamics and @code{\markup} when using @code{TextScripts});
 and @code{\autoFootnote} for annotating chorded notes.
 
 Both commands take three arguments; the @var{Layout Object} to be
@@ -1143,8 +1143,7 @@ required:
 
 There are two commands used to create manual footnotes; @code{\footnote}
 for top-level @code{\markup} and chorded notes; and @code{\footnoteGrob}
-for individual grobs (including @code{\markup} when using
-@code{TextScripts}).
+for individual grobs (and @code{\markup} when using @code{TextScripts}).
 
 When annotating grobs, the @code{\footnote} command takes four
 arguments; the @var{Layout Object} to be annotated, the @var{(x . y)}