In certain cases, an engraver might need to ensure private Scheme variables
(with type SCM) do not get swept away by Guile's garbage collector: for example,
-a cache of the previous key signature which must persist persist between timesteps.
-The method @code{virtual derived_mark () const} can be used in such cases to mark
+a cache of the previous key signature which must persist between timesteps. The
+method @code{virtual derived_mark () const} can be used in such cases to mark
such objects as follows:
@example
@subsection Listening to music events
-External interfaces to to the engraver are implemented by protected
+External interfaces to the engraver are implemented by protected
macros including one or more of the following:
@itemize
}
@end lilypond
-Vertical spaces and brackets can be be included in figures:
+Vertical spaces and brackets can be included in figures:
@lilypond[verbatim,quote,ragged-right,fragment]
\figures {
\clef bass
% stems may overlap the other staff
\override Stem #'cross-staff = ##t
- % extend the stems to reach other other staff
+ % extend the stems to reach the other staff
\override Stem #'length = #12
% do not print extra flags
\override Stem #'flag-style = #'no-flag
@end example
@noindent
-is ambiguous, since it is is not clear to which @code{\repeat} the
+is ambiguous, since it is not clear to which @code{\repeat} the
@code{\alternative} belongs. This ambiguity is resolved by always
having the @code{\alternative} belong to the inner @code{\repeat}.
For clarity, it is advisable to use braces in such situations.
@knownissues
When using different time signatures in parallel, notes
-at the same moment will be be placed at the same horizontal
+at the same moment will be placed at the same horizontal
location. However, the bar lines in the different staves
will cause the note spacing to be less regular in each of the
individual staves than would be normal without the different
@funindex markup
A @code{\markup} block can exist by itself, outside of any
-any @code{\score} block, as a @qq{top-level
-expression}. This syntax is described in @ref{File structure}.
+@code{\score} block, as a @qq{top-level expression}. This syntax
+is described in @ref{File structure}.
@lilypond[verbatim,quote]
\markup {