Index: doc/theses/mike_brooks_MMath/background.tex
===================================================================
--- doc/theses/mike_brooks_MMath/background.tex	(revision c536f9de18ab65ac4eee22b4aef39a6ac8a37de8)
+++ doc/theses/mike_brooks_MMath/background.tex	(revision 502ded0c74289414ef90b7ae2e4fa7ea3dfde332)
@@ -895,5 +895,5 @@
 		head objects are discussed in \VRef{toc:lst:issue:ident}.
 		In (a), the field \lstinline{req.x} names a list direction;
-		these are discussed in \VRef{toc:lst:issue:simultaneity}.
+		these are discussed in \VRef{s:Axis}.
 		In (b) and (c), the type \lstinline{node} represents a system-internal type,
 		which is \lstinline{std::_List_node} in the GNU implementation.
@@ -947,5 +947,5 @@
 		head objects are discussed in \VRef{toc:lst:issue:ident}.
 		In \protect\subref*{f:Intrusive}, the field \lstinline{req.d} names a list direction;
-		these are discussed in \VRef{toc:lst:issue:simultaneity}.
+		these are discussed in \VRef{s:Axis}.
 		In \protect\subref*{f:WrappedRef} and \protect\subref*{f:WrappedValue}, the type \lstinline{node} represents a
 		library-internal type, which is \lstinline{std::_List_node} in the GNU implementation
@@ -964,5 +964,5 @@
 In wrapped value, the @req@ is copied, which increases storage usage, but allows independent simultaneous changes;
 however, knowing which of the @req@ object is the \emph{true} object becomes complex.
-\see*{\VRef{toc:lst:issue:simultaneity} for further discussion.}
+\see*{\VRef{s:Axis} for further discussion.}
 
 The implementation of @LIST_ENTRY@ uses a trick to find the links and the node containing the links.
@@ -1021,6 +1021,6 @@
 
 
-\subsection{Simultaneity: Single \vs Multi-Static \vs Dynamic}
-\label{toc:lst:issue:simultaneity}
+\subsection{Axis: Single \vs Multi-Static \vs Dynamic}
+\label{s:Axis}
 
 \begin{figure}
@@ -1042,5 +1042,5 @@
 \end{figure}
 
-\newterm{Simultaneity} deals with the question:
+\newterm{Axis} deals with the question:
 In how many different lists can a node be stored, at the same time?
 \VRef[Figure]{fig:lst-issues-multi-static} shows an example that can traverse all requests in priority order (field @pri@) or navigate among requests with the same request value (field @rqr@).
@@ -1107,5 +1107,5 @@
 \end{c++}
 
-Simultaneity cannot be done with multiple inheritance, because there is no mechanism to either know the order of inheritance fields or name each inheritance.
+Axis cannot be done with multiple inheritance, because there is no mechanism to either know the order of inheritance fields or name each inheritance.
 Instead, a special type is require that contains the link fields and points at the node.
 \begin{cquote}
@@ -1180,5 +1180,5 @@
 \begin{figure}
 	\centering
-	\includegraphics{lst-issues-ident.pdf}
+	\includegraphics[width=\textwidth]{lst-issues-ident.pdf}
 	\caption{
 		Comparison of headed and ad-hoc list identities, for various list lengths.
@@ -1220,5 +1220,5 @@
 \begin{figure}
 	\centering
-	\includegraphics{lst-issues-end.pdf}
+	\includegraphics[width=0.55\textwidth]{lst-issues-end.pdf}
 	\caption{
 		LQ sub-object-level representation of links and ends.
@@ -1262,5 +1262,5 @@
 
 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 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 @wsanf@/@wprintf@.
+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.
 For wide string literals prefixed by the letter @u@ or @U@, the array elements have type @char16_t@ or @char32_t@, respectively, and are initialized with wide characters corresponding to the multi-byte character sequence, \eg @u"abc@$\mu$@"@, @U"abc@$\mu$@"@.