From 5e9d78f917081510be42811a2cfa2a4a3bedd1f6 Mon Sep 17 00:00:00 2001 From: Francisco Vila Date: Wed, 19 Nov 2008 10:00:13 +0100 Subject: [PATCH] Doc: Typos. --- Documentation/user/lilypond-book.itely | 10 +++++----- Documentation/user/repeats.itely | 2 +- Documentation/user/tweaks.itely | 4 ++-- Documentation/user/vocal.itely | 2 +- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/Documentation/user/lilypond-book.itely b/Documentation/user/lilypond-book.itely index 2a426ceddd..34ebeab922 100644 --- a/Documentation/user/lilypond-book.itely +++ b/Documentation/user/lilypond-book.itely @@ -205,7 +205,7 @@ or \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{}. @@ -394,7 +394,7 @@ or @@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 @@ -465,7 +465,7 @@ To include separate files, say @var{filename} @end example -Additionally, @code{} displays the the current version +Additionally, @code{} displays the current version of lilypond. @@ -659,7 +659,7 @@ source file contain a comment containing @samp{begin verbatim} (without 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. @@ -971,7 +971,7 @@ If you use the same filename extension for the input file than the 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}. diff --git a/Documentation/user/repeats.itely b/Documentation/user/repeats.itely index 751a9cd1aa..21efda6142 100644 --- a/Documentation/user/repeats.itely +++ b/Documentation/user/repeats.itely @@ -293,7 +293,7 @@ b1 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. } } diff --git a/Documentation/user/tweaks.itely b/Documentation/user/tweaks.itely index 7fc49398fc..cdb5568f8e 100644 --- a/Documentation/user/tweaks.itely +++ b/Documentation/user/tweaks.itely @@ -578,7 +578,7 @@ at first, so we can be sure the command is working. We get: @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 @@ -3319,7 +3319,7 @@ and blanking the first up-stem in that voice, the tie appears to cross voices: @cindex Stem, example of overriding -@cindex transparent propery, example +@cindex transparent property, example @lilypond[quote,fragment,relative=2,verbatim] << diff --git a/Documentation/user/vocal.itely b/Documentation/user/vocal.itely index 85b636eeca..16274e366b 100644 --- a/Documentation/user/vocal.itely +++ b/Documentation/user/vocal.itely @@ -627,7 +627,7 @@ single syllable; such vocalises are called melismas, or melismata. @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. -- 2.39.2