partial: 1.0.1.jcn

[lilypond.git] / Documentation / MANIFESTO.pod

diff --git a/Documentation/MANIFESTO.pod b/Documentation/MANIFESTO.pod
index e14cc67f199c273b3225dbb04733f461df5389f8..58847a4d842c659ab75d8ca4997a2ac75c2a1572 100644 (file)
--- a/Documentation/MANIFESTO.pod
+++ b/Documentation/MANIFESTO.pod
@@ -19,7 +19,7 @@ TeX file.
 
 =item *
 
-We want to provide an easy-to-use interface for typesetting music in
+Providing an easy-to-use interface for typesetting music in
 its broadest sense. This interface should be intuitive from a musical
 point of view. By broadest sense we mean: it is designed for music
 printed left to right in staffs, using notes to designate rythm and
@@ -27,13 +27,13 @@ pitch.
 
 =item  *
 
-Generate high-quality output. Ideally it should be of a professional
+Generating high-quality output. Ideally it should be of a professional
 quality. We'd like to render Herbert Chlapiks words, "Fine music
 setting is not possible without a knowledgeable printer,"  untrue.
 
 =item *
 
-Make a system which is fully tweakable. It should be possible to
+Making a system which is fully tweakable. It should be possible to
 typeset a book on how not to typeset music.
 
 =back 
@@ -47,9 +47,9 @@ Further considerations while doing the programming
 
 =item *
 
-GNU LilyPond uses MusiXTeX fonts and TeX for its output. This is not a key
-issue: in a future version, GNU LilyPond might bypass TeX, but at the moment
-TeX is convenient for producing output.
+GNU LilyPond uses TeX for its output. This is not a key issue: in a
+future version, GNU LilyPond might bypass TeX, but at the moment TeX
+is convenient for producing output.
 
 =item *