Index: doc/theses/mike_brooks_MMath/background.tex
===================================================================
--- doc/theses/mike_brooks_MMath/background.tex	(revision 74accc60ee92c4ea0615b1e4ccdb031dd58af74b)
+++ doc/theses/mike_brooks_MMath/background.tex	(revision 037dc57ad1a06c496591a80d9ddae32adb53676e)
@@ -1185,7 +1185,7 @@
 This macro-induced phenomenon led to an invalid pointer dereference (safety violation), at a run-time well after the removal at issue (costly to resolve).
 
-Instead, language function calls (even with inlining) handle argument mistakes locally at the call, giving a very specific error message.  In the world of \CC templates, concepts were introduced to deal with this problem.  Furthermovre, language function calls use (only) C-language semantics for argument evaluation, instead of applealing to reasoning about how the semantics might play out in an invisible substitution result.
-
-So, avoiding a macro-centric implementation helps uers avoid and diagnose critical mistakes.
+Instead, language function calls (even with inlining) handle argument mistakes locally at the call, giving a very specific error message.  In the world of \CC templates, concepts were introduced to deal with this problem.  Furthermore, language function calls use (only) C-language semantics for argument evaluation, instead of appealing to reasoning about how the semantics might play out in an invisible substitution result.
+
+So, avoiding a macro-centric implementation helps users avoid and diagnose critical mistakes.
 
 % example of poor error message due to LQ's preprocessed integration