Some minor typos in the essay (web/about/automated-engraving)

[Matthias Kilian]

Hi,

I just found some stone-aged diffs on my disk that sort-of correct
some typos in the fine essay "Obsessed with putting ink on paper"
on the LilyPond website.

Since I'm not a native speaker, feel free to ignore and/or change
some or all of them.

Ciao,
        Kili


Index: site/about/automated-engraving/benchmarking.html
===================================================================
RCS file: 
/cvsroot/lilypond/newweb/site/about/automated-engraving/benchmarking.html,v
retrieving revision 1.6
diff -u -r1.6 benchmarking.html
--- site/about/automated-engraving/benchmarking.html    24 Mar 2004 00:06:03 
-0000      1.6
+++ site/about/automated-engraving/benchmarking.html    20 Mar 2005 20:45:36 
-0000
@@ -7,7 +7,7 @@
 emulation of printed matter will give a good result.  We suggested in
 the introduction to compare program output with existing hand-engraved
 scores.  It is exactly this technique that we use to perfect LilyPond
-output.  In a way, this a benchmarking technique: the performance of
+output.  In a way, this is a benchmarking technique: the performance of
 the program, in terms of quality, is measured in relation to a known
 quantity.
 
Index: site/about/automated-engraving/engraving.html
===================================================================
RCS file: 
/cvsroot/lilypond/newweb/site/about/automated-engraving/engraving.html,v
retrieving revision 1.5
diff -u -r1.5 engraving.html
--- site/about/automated-engraving/engraving.html       22 Sep 2003 12:14:48 
-0000      1.5
+++ site/about/automated-engraving/engraving.html       20 Mar 2005 20:45:36 
-0000
@@ -30,7 +30,7 @@
 
 <li> Finally, engraving is about selecting proper distance and
 blackness for scores. <img align=right src="@address@hidden"> The
-quality of the end result must judged visually. This is virtually
+quality of the end result must be judged visually. This is virtually
 impossible to capture in formal rules.
 
 </ul>
Index: site/about/automated-engraving/formatting-architecture.html
===================================================================
RCS file: 
/cvsroot/lilypond/newweb/site/about/automated-engraving/formatting-architecture.html,v
retrieving revision 1.4
diff -u -r1.4 formatting-architecture.html
--- site/about/automated-engraving/formatting-architecture.html 22 Sep 2003 
12:14:48 -0000      1.4
+++ site/about/automated-engraving/formatting-architecture.html 20 Mar 2005 
20:45:36 -0000
@@ -4,7 +4,7 @@
 
 <p>
 
-Remember the music notation problem? The solution of it left us with a
+Remember the music notation problem? Its solution left us with a
 bunch of objects. The formatting architecture is built on these
 objects. Each object carries variables:
 
@@ -23,7 +23,7 @@
 
 
 <li>Some variables have a preset value. For example, the thickness of
- many lines ---a characteristic of typographical style--are preset
+ many lines &ndash; a characteristic of typographical style &ndash; are preset
  variables. Changing them gives a different typographical impression:
  
  <p align=center>
@@ -34,7 +34,7 @@
 variables containing procedures. These procedure perform the actual
 formatting, and by substituting different ones, we can change
 behavior. In the following example, the rule that note head objects
-use to produce their symbol is changed during the music fragment:
+use to draw their symbol is changed during the music fragment:
 
 <p align=center>
 <img src="@address@hidden">
Index: site/about/automated-engraving/implementing-notation.html
===================================================================
RCS file: 
/cvsroot/lilypond/newweb/site/about/automated-engraving/implementing-notation.html,v
retrieving revision 1.4
diff -u -r1.4 implementing-notation.html
--- site/about/automated-engraving/implementing-notation.html   22 Sep 2003 
12:14:48 -0000      1.4
+++ site/about/automated-engraving/implementing-notation.html   20 Mar 2005 
20:45:36 -0000
@@ -44,7 +44,7 @@
 <img address@hidden@engraver-stem.png>
 <p>
 This engraver is notified of any note head coming along.  Every time
-one (or more, for a chord) note heads is seen, a stem object is
+one (or more, for a chord) note head is seen, a stem object is
 created, and attached to the note head.
 
 <li>
Index: site/about/automated-engraving/implementing-typography.html
===================================================================
RCS file: 
/cvsroot/lilypond/newweb/site/about/automated-engraving/implementing-typography.html,v
retrieving revision 1.6
diff -u -r1.6 implementing-typography.html
--- site/about/automated-engraving/implementing-typography.html 29 Feb 2004 
14:44:33 -0000      1.6
+++ site/about/automated-engraving/implementing-typography.html 20 Mar 2005 
20:45:36 -0000
@@ -9,7 +9,7 @@
 
 How do we go about implementing typography?  Answering the "music
 notation" problem left us with a bunch of graphic objects
-representings note heads, the staff, stems, etc.
+representing note heads, the staff, stems, etc.
 
 
 <p>
Index: site/about/automated-engraving/software.html
===================================================================
RCS file: 
/cvsroot/lilypond/newweb/site/about/automated-engraving/software.html,v
retrieving revision 1.6
diff -u -r1.6 software.html
--- site/about/automated-engraving/software.html        27 Jan 2004 23:43:29 
-0000      1.6
+++ site/about/automated-engraving/software.html        20 Mar 2005 20:45:36 
-0000
@@ -64,10 +64,10 @@
 
 <p>
 
-This is one example may seem contrived, but in fact, it's not.  All
+This example may seem contrived, but in fact, it's not.  All
 major producers of notation software claim to follow engraving
 standards, but we have not seen any that gets the basics right; all of
-them make systemic mistakes.  If you want to assess the output of your
+them make systematic mistakes.  If you want to assess the output of your
 favorite program, then buy a decent hand-made score from a respectable
 publisher, and try to reproduce one page of it. Then compare them: