More appreciation.

diff --git a/doc/mad-manual.xml b/doc/mad-manual.xml
index 411166457529dce1e1f2e9c2136d9150620a321d..4b078c5335b46acc71e869d1c99cd14a3d10d6ef 100644 (file)
--- a/doc/mad-manual.xml
+++ b/doc/mad-manual.xml
@@ -83,8 +83,8 @@ language features that at this date the infant discipline of computer
 science had yet to separate itself from applied mathematics.  All
 the impedimenta of mathematical notation are present not just in the
 formulas, but in the language syntax descriptions where script letters
-are used as metavariables.  The whole is written in the rather clotted
-prose one finds in mathematical papers.</para>
+are used as metavariables.  The whole is written in the rather stilted
+over-formal prose one typically finds in mathematical papers.</para>
 
 <para>Certain phrasings in the manual suggest that the authors
 thought of flowcharts as the primary notation for programs, and
@@ -93,7 +93,7 @@ made sense at the time; programming notations were clumsy and
 primitive, and the typical complexity of programs was very low.  
 By five years later (roughly three or four Moore's-Law doublings)
 flowcharting was going out of fashion, probably for the simple
-reasin that flowcharts were getting too large to draw and read!</para>
+reason that flowcharts were getting too large to draw and read!</para>
 
 <para>There are some significant respects in which MAD was actually
 rather advanced for its period.  The multiline WHENEVER statement
@@ -105,13 +105,21 @@ illustrates, MAD even supported what was later called
 <quote>higher-order programming</quote> &mdash; passing around
 function-valued variables!</para>
 
+<para>On the other hand, there are some features of MAD which make one
+truly wonder what the designers were thinking &mdash; the handling of
+array indexing, for example.  If 1962 weren't a couple of years too
+early to attribute that to an LSD overdose it would make a tempting
+hypothesis.</para>
+
 <para>In most of the respects we've described, however, MAD is very
-typical of its time.  This will become apparent from a look at the
-Retrocomputing Museum implementation of CORC/CUPL, which is rather
-similar (though less powerful).  This entire family of languages
-became extinct in the 1970s, snuffed out like dinosaurs by the 
-meteoritic impact of time-shared computing and teletypewriter-like
-interactive terminals.</para>
+representative of its time.  This will become apparent from a look at
+the Retrocomputing Museum implementation of CORC/CUPL, which is rather
+similar (though less powerful).  MAD's grammar &mdash; ad-hoc and
+festooned with many more keywords than a modern language would employ
+&mdash; is very typical.  This entire family of languages became
+extinct in the 1970s, snuffed out like dinosaurs by the meteoritic
+impact of time-shared computing and teletypewriter-like interactive
+terminals.</para>
 
 </sect1>
 
@@ -2134,7 +2142,7 @@ is to appear.  Specifications for reading or punching cards and
 printing of information are identical, whith the following exceptions:</para>
 
 <para>(a) A card has only 72 available
-columns<footnote><para>Actually, 80 columns may be usd, provided the
+columns<footnote><para>Actually, 80 columns may be used, provided the
 proper computer hardware configuration is available.  The use of 72
 columns is always safe, however, and strongly
 recommended. </para></footnote> while a line of print has 120