From e50639d5cfc9991500d36d0cdaea3308c0bb7bd7 Mon Sep 17 00:00:00 2001 From: Heikki Junes Date: Wed, 15 Sep 2004 22:52:11 +0000 Subject: [PATCH] Expand 's to is. --- ChangeLog | 3 +++ Documentation/user/changing-defaults.itely | 2 +- Documentation/user/examples.itely | 10 +++++----- Documentation/user/invoking.itexi | 2 +- Documentation/user/tutorial.itely | 6 +++--- 5 files changed, 13 insertions(+), 10 deletions(-) diff --git a/ChangeLog b/ChangeLog index f6a0bae4f5..51c7a85793 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,8 @@ 2004-09-16 Heikki Junes + * Documentation/user/{changing-defaults,examples,invoking, + tutorial}.itely: Expand 's to is. + * Documentation/user/notation.itely: Capitalize only first letter. * Documentation/user/programming-interface.itely: Capitalize Scheme. diff --git a/Documentation/user/changing-defaults.itely b/Documentation/user/changing-defaults.itely index c282487256..549447a735 100644 --- a/Documentation/user/changing-defaults.itely +++ b/Documentation/user/changing-defaults.itely @@ -1044,7 +1044,7 @@ has the following aspects @itemize @bullet @item Its size is independent of the horizontal spacing, unlike slurs or beams. -@item It is a piece of text. Granted, it's usually a very short text. +@item It is a piece of text. Granted, it is usually a very short text. @item That piece of text is typeset with a font, unlike slurs or beams. @item Horizontally, the center of the symbol should be aligned to the diff --git a/Documentation/user/examples.itely b/Documentation/user/examples.itely index 3bc2355f77..2582e3f00a 100644 --- a/Documentation/user/examples.itely +++ b/Documentation/user/examples.itely @@ -48,7 +48,7 @@ it quicker. How often is ``every so often''? It depends on the complexity of the music. For very simple music, perhaps just once or twice. For very complex music, every bar. -@item One bar per line. If there's anything complicated, either in the music +@item One bar per line. If there is anything complicated, either in the music itself or in the output you desire, it's often good to write only one bar per line. Saving screen space by cramming eight bars per line just isn't worth it if you have to `debug' your files. @@ -206,7 +206,7 @@ harmonies = \chordmode { @section Piano templates @subsection Solo piano -Here's a simple piano staff. +Here is a simple piano staff. @lilypond[verbatim,raggedright] @@ -241,7 +241,7 @@ lower = \relative c { @subsection Piano and melody with lyrics -Here's a typical song format: one staff with the melody and lyrics, with +Here is a typical song format: one staff with the melody and lyrics, with piano accompaniment underneath. @lilypond[verbatim,raggedright] @@ -300,7 +300,7 @@ lower = \relative c { @section Small ensembles @subsection SATB vocal score -Here's a standard four-part SATB vocal score. With larger ensembles, +Here is a standard four-part SATB vocal score. With larger ensembles, it's often useful to include a section which is included in all parts. For example, the time signature and key signatures are almost always the same for all parts. @@ -783,7 +783,7 @@ chant = \relative c' { @subsection Bagpipe music -Here's an example of bagpipe music. It demonstrates a big strength of +Here is an example of bagpipe music. It demonstrates a big strength of LilyPond, compared to graphical score editors: in LilyPond, you can very easily reuse small segments of music without writing them out completely. This template defines a large number of small segments diff --git a/Documentation/user/invoking.itexi b/Documentation/user/invoking.itexi index 92ed451dd4..7fdf1ef142 100644 --- a/Documentation/user/invoking.itexi +++ b/Documentation/user/invoking.itexi @@ -289,7 +289,7 @@ has already been reported. You could also try doing a few searches on the mailing list for the bug. Sometimes the bug will have already been reported and a fix or workaround is already known. -Here's an example of a good bug report: +Here is an example of a good bug report: @verbatim diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index 132070a455..2a39da5bf1 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -632,8 +632,8 @@ for complex music like polyphonic scores. Note that this example only has one staff, whereas the previous example had three seperate staves. That is because this example begins with a single note. To determine the number of staves, -LilyPond looks at the first element. If it's a single note, there's one -staff; if there's a simultaneous expression, there's more than one staff. +LilyPond looks at the first element. If it is a single note, there is one +staff; if there is a simultaneous expression, there is more than one staff. @lilypond[fragment,quote,verbatim,relative=2] { @@ -748,7 +748,7 @@ c-3 e-5 b-2 a-1 Articulations and fingerings are usually placed automatically, but you can specify a direction using @samp{^} (up) or @samp{_} (down). You can -also use multiple articulations on the same note. In most cases, it's +also use multiple articulations on the same note. In most cases, it is best to let LilyPond determine the articulation directions. @lilypond[fragment,quote,verbatim,relative=2] -- 2.39.2