Index: doc/theses/mubeen_zulfiqar_MMath/background.tex
===================================================================
--- doc/theses/mubeen_zulfiqar_MMath/background.tex	(revision a6e8f64afb15bd1b90d957d0d96b2c8ba7b16b46)
+++ doc/theses/mubeen_zulfiqar_MMath/background.tex	(revision 52a532aeea4c5d07aed521ab8bb032f1a50074f7)
@@ -212,5 +212,6 @@
 a memory allocator can only affect the latter two.
 
-\paragraph{\newterm{Program-induced false-sharing}} occurs when one thread passes an object sharing a cache line to another thread, and both threads modify the respective objects.
+\paragraph{\newterm{Program-induced false-sharing}}
+occurs when one thread passes an object sharing a cache line to another thread, and both threads modify the respective objects.
 \VRef[Figure]{f:ProgramInducedFalseSharing} shows when Thread$_1$ passes Object$_2$ to Thread$_2$, a false-sharing situation forms when Thread$_1$ modifies Object$_1$ and Thread$_2$ modifies Object$_2$.
 Changes to Object$_1$ invalidate CPU$_2$'s cache line, and changes to Object$_2$ invalidate CPU$_1$'s cache line.
@@ -236,9 +237,13 @@
 \end{figure}
 
-\paragraph{\newterm{Allocator-induced active false-sharing}} occurs when objects are allocated within the same cache line but to different threads.
+\paragraph{\newterm{Allocator-induced active false-sharing}}
+\label{s:AllocatorInducedActiveFalseSharing}
+occurs when objects are allocated within the same cache line but to different threads.
 For example, in \VRef[Figure]{f:AllocatorInducedActiveFalseSharing}, each thread allocates an object and loads a cache-line of memory into its associated cache.
 Again, changes to Object$_1$ invalidate CPU$_2$'s cache line, and changes to Object$_2$ invalidate CPU$_1$'s cache line.
 
-\paragraph{\newterm{Allocator-induced passive false-sharing}} is another form of allocator-induced false-sharing caused by program-induced false-sharing.
+\paragraph{\newterm{Allocator-induced passive false-sharing}}
+\label{s:AllocatorInducedPassiveFalseSharing}
+is another form of allocator-induced false-sharing caused by program-induced false-sharing.
 When an object in a program-induced false-sharing situation is deallocated, a future allocation of that object may cause passive false-sharing.
 For example, in \VRef[Figure]{f:AllocatorInducedPassiveFalseSharing}, Thread$_1$ passes Object$_2$ to Thread$_2$, and Thread$_2$ subsequently deallocates Object$_2$.