release: 1.3.107

[lilypond.git] / Documentation / user / tutorial.itely

diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely
index 2a6e64e63ab4b80acdf411b6eb4a39609c253d3f..cc4b30e881f399801cd43ffdd9aeb9f6ec69113a 100644 (file)
--- a/Documentation/user/tutorial.itely
+++ b/Documentation/user/tutorial.itely
@@ -18,16 +18,16 @@
 LilyPond prints music from a specification that you, the user, supply.
 You have to give that specification using a @emph{language}.  This
 document is a gentle introduction to that language, which is called
-Mudela, an acronym of Music Definition Language.
+Lilypond, an acronym of Music Definition Language.
 
-This tutorial will demonstrate how to use Mudela by presenting
+This tutorial will demonstrate how to use Lilypond by presenting
 examples of input along with resulting output.  We will use English
 terms for notation.  In case you are not familiar with those, you may
 consult the glossary that is distributed with LilyPond.
 
 The examples discussed are included in the distribution, in the
 subdirectory @file{input/tutorial/}.  It is recommended that you
-experiment with writing Mudela input yourself, to get a feel for
+experiment with writing Lilypond input yourself, to get a feel for
 how LilyPond behaves.
 
 @node The first tune,  , , Tutorial
@@ -38,7 +38,7 @@ To demonstrate what LilyPond input looks like, we start off with a
 full fledged, yet simple example. It is a convoluted version
 of the famous menuet in J. S. Bach's @emph{Klavierbuechlein}.
 
-@mudela[verbatim]
+@lilypond[verbatim]
 % lines preceded by a percent are comments which
 % are ignored by Lilypond.
 \include "paper16.ly"
@@ -69,7 +69,7 @@ of the famous menuet in J. S. Bach's @emph{Klavierbuechlein}.
        linewidth = 14.0 \cm;
    }
 }
-@end mudela
+@end lilypond
 
 Enter it (or copy it, the filename is @file{menuet.ly}), compile it
 with LilyPond and view the output.  Details of this procedure may vary
@@ -123,7 +123,7 @@ that size, which is done.
         \score @{
  
 @end example 
-  A mudela file combines music with directions for outputting that
+  A lilypond file combines music with directions for outputting that
 music.  The music is combined with the output directions by putting
 them into a @code{\score} block.
 @example 
@@ -219,7 +219,7 @@ processing the music, LilyPond will verify that bar checks are found at
 the start of a measure.  This can help you track down errors.
 
  So far, no notes were chromatically altered.  Here is the first one
-that is: @code{fis}. Mudela by default uses Dutch note names, and
+that is: @code{fis}. Lilypond by default uses Dutch note names, and
 ``Fis'' is the Dutch note name for ``F sharp''.  However, there is no
 sharp sign in the output. The program keeps track of key signatures,
 and will only print accidentals if they are needed.
@@ -394,7 +394,7 @@ may differ, since the titling in this document is not generated by
 @center @strong{The river is flowing}
 @center Traditional 
 
-@mudela[center]
+@lilypond[center]
 \header {
         title = "The river is flowing";
         composer = "Traditional (?)";
@@ -435,7 +435,7 @@ accompaniment =\chords {
         \midi  { \tempo 4=72;}
         \paper { linewidth = 10.0\cm; }
 }
-@end mudela
+@end lilypond
 
 Again, we will dissect the file line by line.
 @example 
@@ -706,7 +706,7 @@ Our third subject is a piece of piano music.  The fragment in the input
 file is a piano reduction of the G major Sinfonia by Giovanni Battista
 Sammartini.  It was composed around 1740. 
 
-@mudela[verbatim]
+@lilypond[verbatim]
 
 \version "1.3.60";
 \include "paper16.ly";
@@ -766,7 +766,7 @@ bassvoices = \notes \relative c' {
           indent = 0.0;
           linewidth = 15.0 \cm; }
 }
-@end mudela
+@end lilypond
 
 If it looks like incomprehensible gibberish to you@dots{} Then you are
 right.  The author has doctored this example to have as many quirks in
@@ -774,10 +774,10 @@ one system as possible.
 @example 
 \version "1.3.61";
 @end example 
-Lilypond and the Mudela language is still under development, therefore
+Lilypond and the Lilypond language is still under development, therefore
 it is useful to indicate the Lilypond version of the file. Lilypond 
 will check the version number and warn you when the syntax has
-changed. Also, the @code{convert-mudela} program will be able to 
+changed. Also, the @code{convert-ly} program will be able to 
 update most of the syntax changes automatically.
 @example 
 viola = \notes \relative c'  \context Voice = viola @{