Pass through second half of StackMachine

latex/cpdt.bib

@@ -129,3 +129,10 @@
   volume = {76(2-3)},
   year = {1988}
 }
+
+@article{GADT,
+  author = {Hongwei Xi and Chiyan Chen and Gang Chen},
+  title = {Guarded Recursive Datatype Constructors},
+  booktitle = {Proceedings of the 30th ACM SIGPLAN Symposium on Principles of Programming Languages},
+  year = {2003}
+}

src/Intro.v

@@ -167,7 +167,7 @@ Some readers have suggested that I give multiple recommended reading orders in t
 
 Readers with no prior Coq experience can ignore the preceding discussion!  I hope that my heavy reliance on proof automation early on will seem like the most natural way to go, such that you may wonder why others are spending so much time entering sequences of proof steps manually.
 
-Coq is a very complex system, with many different commands driven more by pragmatic concerns than by any overarching aesthetic principle.  When I use some construct for the first time, I try to give a one-sentence intuition for what it accomplishes, but I leave the details to the Coq reference manual%~\cite{CoqManual}%.  I expect that readers interested in complete understandings will be consulting that manual frequently; in that sense, this book is not meant to be completely standalone.
+Coq is a very complex system, with many different commands driven more by pragmatic concerns than by any overarching aesthetic principle.  When I use some construct for the first time, I try to give a one-sentence intuition for what it accomplishes, but I leave the details to the Coq reference manual%~\cite{CoqManual}%.  I expect that readers interested in complete understandings will be consulting that manual frequently; in that sense, this book is not meant to be completely standalone.  I often use constructs in code snippets without first introducing them at all, but explanations should always follow in the prose paragraphs immediately after the offending snippets.
 *)
 
 (** ** On the Tactic Library *)