Merge with master

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

diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely
index 975f4bdb87aaced4740590276f919b873462d9f1..33a62a44b8d15f7b6b921a150ee76821116cba7b 100644 (file)
--- a/Documentation/user/introduction.itely
+++ b/Documentation/user/introduction.itely
@@ -389,7 +389,7 @@ separately.  Such plug-ins are called @code{engraver}s, by analogy
 with craftsmen who translate musical ideas to graphic symbols.
 
 In the following example, we see how we start out with a plug-in for
-note heads, the @code{Note_heads_engraver}
+note heads, the @code{Note_heads_engraver}.
 
 @lilypond[quote,ragged-right]
 \include "engraver-example.ily"
@@ -481,7 +481,7 @@ the @code{Clef_engraver} defines a reference point for the staff
 @end lilypond
 
 @noindent
-and the @code{Stem_engraver} adds stems
+and the @code{Stem_engraver} adds stems.
 
 @lilypond[quote,ragged-right]
 \include "engraver-example.ily"
@@ -649,14 +649,14 @@ and representation take up less than 10% of the source code.
 We have written LilyPond as an experiment of how to condense the art
 of music engraving into a computer program.  Thanks to all that hard
 work, the program can now be used to perform useful tasks.  The
-simplest application is printing notes
+simplest application is printing notes.
 
 @lilypond[quote,relative=1,fragment]
 \time 2/4 c4 c g'4 g a4 a g2
 @end lilypond
 
 @noindent
-By adding chord names and lyrics we obtain a lead sheet:
+By adding chord names and lyrics we obtain a lead sheet.
 
 @lilypond[quote,ragged-right]
 <<
@@ -667,7 +667,7 @@ By adding chord names and lyrics we obtain a lead sheet:
 @end lilypond
 
 Polyphonic notation and piano music can also be printed.  The following
-example combines some more exotic constructs
+example combines some more exotic constructs.
 
 @lilypondfile[quote,ragged-right]{screech-boink.ly}
 
@@ -915,7 +915,7 @@ vary from system to system.  On occasion, this manual refers to
 initialization and example files.  Throughout this manual, we refer to
 input files relative to the top-directory of the source archive.  For
 example, @file{input/@/test/@/bla@/.ly} may refer to the file
-@file{lilypond@/-2.8.0/@/input/@/test/@/bla@/.ly}.  On binary packages
+@file{lilypond@/2.x.y/@/input/@/test/@/bla@/.ly}.  On binary packages
 for the Unix platform, the documentation and examples can typically be
 found somewhere below @file{/usr/@/share/@/doc/@/lilypond/}.
 Initialization files, for example @file{scm/@/lily@/.scm}, or