\lilypond@{ YOUR LILYPOND CODE @}
@end example
-Additionally, @code{\lilypondversion} displays the the current version
+Additionally, @code{\lilypondversion} displays the current version
of lilypond.
Running @command{lilypond-book} yields a file that can be further
processed with @LaTeX{}.
@@lilypondfile[options,go,here]@{@var{filename}@}
@end example
-Additionally, @code{@@lilypondversion} displays the the current version
+Additionally, @code{@@lilypondversion} displays the current version
of lilypond.
When @command{lilypond-book} is run on it, this results in a Texinfo
<lilypondfile @var{option1} @var{option2} ...>@var{filename}</lilypondfile>
@end example
-Additionally, @code{<lilypondversion/>} displays the the current version
+Additionally, @code{<lilypondversion/>} displays the current version
of lilypond.
quotes), quoting the source in the verbatim block will start after the
last occurrence of such a comment; similarly, quoting the source verbatim
will stop just before the first occurrence of a comment containing
-@samp{end verbatim}, it there is any. In the following source file
+@samp{end verbatim}, if there is any. In the following source file
example, the music will be interpreted in relative mode, but the
verbatim quote will not show the @code{relative} block, i.e.
extension @command{lilypond-book} uses for the output file, and if the
input file is in the same directory as @command{lilypond-book} working
directory, you must use @code{--output} option to make
-@command{lilypond-book} running, otherwise the will exit with an error
+@command{lilypond-book} running, otherwise it will exit with an error
message like @qq{Output would overwrite input file}.
Text can be included with the volta bracket. The text can be a
number or numbers or markup text, see @ref{Formatting text}. The
simplest way to use markup text is to define the markup first,
-then include the the markup in a Scheme list.
+then include the markup in a Scheme list.
@lilypond[verbatim,quote]
voltaAdLib = \markup { 1. 2. 3... \text \italic { ad lib. } }
@end example
Don't forget the @code{#'} preceding the
-property name and and @code{#} preceding the new value!
+property name and a @code{#} preceding the new value!
The final question is, @q{Where should this command be
placed?} While you are unsure and learning, the best
cross voices:
@cindex Stem, example of overriding
-@cindex transparent propery, example
+@cindex transparent property, example
@lilypond[quote,fragment,relative=2,verbatim]
<<
@c it might be better to present it first - vv
You can define melismata entirely in the lyrics, by entering @code{_}
-for every extra note that has to be added to the the melisma.
+for every extra note that has to be added to the melisma.
@c FIXME: clarify: __ is used to crate a lyric extender,
@c _ is used to add a note to a melisma, so both __ and _ are needed.