Index: doc/theses/mike_brooks_MMath/background.tex
===================================================================
--- doc/theses/mike_brooks_MMath/background.tex	(revision fe6047c9f454f4896c388e4012c6958cf83004c7)
+++ doc/theses/mike_brooks_MMath/background.tex	(revision 67748f9d43312e16fd6b273fc259f1f13dde2eff)
@@ -626,6 +626,6 @@
     void f( int n, float[][n]  );   $\C{// array of VLAs}$
 \end{cfa}
-as a repeat, without an error about conflicting types for @f@.
-Yet, entirely different stride calculations would occur in a function body whose parameters were declared in each of the two styles.
+without an error about conflicting types for @f@.
+Yet, entirely different stride calculations occur in the function body for each of the two parameter styles.
 
 \begin{figure}
@@ -794,4 +794,5 @@
 
 \subsection{Arrays Could be Values}
+\label{s:ArraysCouldbeValues}
 
 All arrays have a know runtime size at their point of declaration.
Index: doc/theses/mike_brooks_MMath/uw-ethesis-frontpgs.tex
===================================================================
--- doc/theses/mike_brooks_MMath/uw-ethesis-frontpgs.tex	(revision fe6047c9f454f4896c388e4012c6958cf83004c7)
+++ doc/theses/mike_brooks_MMath/uw-ethesis-frontpgs.tex	(revision 67748f9d43312e16fd6b273fc259f1f13dde2eff)
@@ -139,5 +139,5 @@
 Often, the array is part of the programming language, while linked lists are built from (recursive) pointer types, and strings from arrays and/or linked lists.
 For all three types, languages and/or their libraries supply varying degrees of high-level mechanisms for manipulating these objects at the bulk and component levels, such as copying, slicing, extracting, and iterating among elements.
-Unfortunately, typical solutions for the the key types in C cause 60\%--70\% of the reported software vulnerabilities involving memory errors; 70\%--80\% of hacker attack vectors target these types.
+Unfortunately, typical solutions for the these key types in C cause 60\%--70\% of the reported software vulnerabilities involving memory errors; 70\%--80\% of hacker attack-vectors target these types.
 Therefore, hardening these three C types goes a long way to make the majority of C programs safer.