X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=Documentation%2Fuser%2Fancient.itely;h=c6ae58e19ba9c5786e65fc6fb581d24164918cee;hb=1423508c355989fa26a8cfe5985b0d6e1ab0a538;hp=6774268c76d21a762c3e911c0c1c75f502b159ae;hpb=d664f5a7153ec2b1a1c4c9fba2d2174bf3140695;p=lilypond.git

diff --git a/Documentation/user/ancient.itely b/Documentation/user/ancient.itely
index 6774268c76..c6ae58e19b 100644
--- a/Documentation/user/ancient.itely
+++ b/Documentation/user/ancient.itely
@@ -7,7 +7,7 @@
     version that you are working on.  See TRANSLATION for details.
 @end ignore
 
-@c \version "2.11.61"
+@c \version "2.12.0"
 
 @node Ancient notation
 @section Ancient notation
@@ -71,7 +71,7 @@ Three styles are available for typesetting Gregorian chant:
 @item @emph{Editio Vaticana} is a complete style for
 Gregorian chant, following the appearance of the Solesmes
 editions, the official chant books of the Vatican since 1904.
-Lilypond has support for all the notational signs used in this
+LilyPond has support for all the notational signs used in this
 style, including ligatures, @emph{custodes}, and special signs
 such as the quilisma and the oriscus.
 
@@ -1456,7 +1456,7 @@ in the above table is accordingly extrapolated.  This way,
 infinitely many different ligatures can be created.
 
 Note that the use of these signs in the music itself follows
-certain rules, which are not checked by Lilypond.  E.g., the
+certain rules, which are not checked by LilyPond.  E.g., the
 @emph{quilisma} is always the middle note of an ascending
 ligature, and usually falls on a half-tone step, but it is
 perfectly possible, although incorrect, to make a single-note
@@ -1492,7 +1492,7 @@ shows the code fragment that produces this ligature, using
 @tab
 @b{Output}
 @tab
-@b{Lilypond@*
+@b{LilyPond@*
 code}
 
 @c TODO: \layout block is identical in all of the below examples.
@@ -2290,7 +2290,7 @@ with head prefixes in arbitrary order.
 
 Working with ancient music frequently involves particular tasks
 which differ considerably from the modern notation for which
-Lilypond is designed.  In the rest of this section, a number of
+LilyPond is designed.  In the rest of this section, a number of
 typical scenarios are outlined, with suggestions of solutions.
 These involve: