Index: doc/theses/mike_brooks_MMath/background.tex
===================================================================
--- doc/theses/mike_brooks_MMath/background.tex	(revision 221d40cd58b332bcac583e693b430c8d3afcf36a)
+++ doc/theses/mike_brooks_MMath/background.tex	(revision 56deb9bcc077923134511b9a3c8863201059170d)
@@ -36,6 +36,4 @@
 % Yet, the rejection presents as a GCC warning.
 % *1  TAPL-pg1 definition of a type system
-
-% reading C declaration: https://c-faq.com/decl/spiral.anderson.html
 
 
@@ -96,8 +94,6 @@
 In spite of its difficulties, I believe that the C's approach to declarations remains plausible, and am comfortable with it; it is a useful unifying principle.~\cite[p.~12]{Ritchie93}
 \end{quote}
-After all, reading a C array type is easy: just read it from the inside out, and know when to look left and when to look right!
+After all, reading a C array type is easy: just read it from the inside out following the ``clock-wise spiral rule''~\cite{Anderson94}.
 Unfortunately, \CFA cannot correct these operator priority inversions without breaking C compatibility.
-
-TODO: rephrase to acknowledge the "clockwise rule" https://c-faq.com/decl/spiral.anderson.html
 
 The alternative solution is for \CFA to provide its own type, variable and routine declarations, using a more intuitive syntax.
@@ -621,6 +617,6 @@
 In fact, the outermost type constructor (syntactically first dimension) is really the one that determines the parameter flavour.
 
-TODO: add examples of mycode/arrr/bugs/c-dependent/x.cfa:v5102,5103,
-which are shocking how much C ignores.
+\PAB{TODO: add examples of mycode/arrr/bugs/c-dependent/x.cfa:v5102,5103,
+which are shocking how much C ignores.}
 
 \begin{figure}
@@ -1261,5 +1257,5 @@
 The kind of characters in the string is denoted by a prefix: UTF-8 characters are prefixed by @u8@, wide characters are prefixed by @L@, @u@, or @U@.
 
-For UTF-8 string literals, the array elements have type @char@ and are initialized with the characters of the multi-byte character sequences, \eg @u8"\xe1\x90\x87"@ (Canadian syllabics Y-Cree OO).
+For UTF-8 string literals, the array elements have type @char@ and are initialized with the characters of the multi-byte character sequences, \eg @u8"\xe1\x90\x87"@ (Canadian syllabic Y-Cree OO).
 For wide string literals prefixed by the letter @L@, the array elements have type @wchar_t@ and are initialized with the wide characters corresponding to the multi-byte character sequence, \eg @L"abc@$\mu$@"@ and are read/printed using @wscanf@/@wprintf@.
 The value of a wide-character is implementation-defined, usually a UTF-16 character.
