*** empty log message ***

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

diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely
index 098aa29173b12ecfc2816bd38e3915ce01a18ed4..f52b1fe6ee312954f5b4145d91a914e05ba862a5 100644 (file)
--- a/Documentation/user/introduction.itely
+++ b/Documentation/user/introduction.itely
@@ -58,7 +58,7 @@ Each plug-in are completely modular and independent, so each can be
 developed and improved separately.  When put together, the plug-ins
 can solve the music notation program in cooperation.  People that put
 graphics to musical ideas are called copyists or engravers, so by
-analogy, each plug-in is also @code{engraver}.
+analogy, each plug-in is also called @code{engraver}.
 
 In the following example, we see how we start out with a note head
 engraver.
@@ -423,12 +423,12 @@ require them to be twice the thickness of the staff lines. The same
 mechanism can be used to adjust a setting globally. By issuing the
 following command, the entire piece is now formatted with thicker stems:
 @example
-    \property Score.Stem \override #'thickness = #2.0 
+    \property Score.Stem \override #'thickness = #3.0 
 @end example
 
 @lilypond
 \score { \notes \relative c'' {
-    \property Score.Stem \override #'thickness = #2.0 
+    \property Score.Stem \override #'thickness = #3.0 
     \once\property Voice. DynamicLineSpanner  \override #'padding = #4.0 
 \stemUp
     a4_\f f,8
@@ -450,7 +450,7 @@ example above is calculated by the function
 this function by a more advanced one, we could issue
 @example
     \property Voice.DynamicLineSpanner \override #'Y-offset-callbacks
-       = #`(,gee-whiz-gadget)
+       = #(list gee-whiz-gadget)
 @end example
 
 @noindent
@@ -630,8 +630,8 @@ how to upgrade input files from previous versions of LilyPond.
 
 Once you are an experienced user, you can use the manual as reference:
 there is an extensive index@footnote{If you are looking for something,
-and you cannot find it by using the index, that is considered a bug.
-In that case, please file a bug report.}, but the document is also
+and you cannot find it in the manual, that is considered a bug.  In
+that case, please file a bug report.}, but the document is also
 available in
 @ifnothtml
 a big HTML page,