Index: doc/theses/thierry_delisle_PhD/thesis/text/conclusion.tex
===================================================================
--- doc/theses/thierry_delisle_PhD/thesis/text/conclusion.tex	(revision a44514e423e42885d51a0b2fef58f0d506dd92ca)
+++ doc/theses/thierry_delisle_PhD/thesis/text/conclusion.tex	(revision e4855f684383f7bd8f4a3a1ad28663c2f6d307c7)
@@ -16,5 +16,5 @@
 For these kinds of fair workloads, adding fairness must be low-cost to hide the communication costs needed for global ready-queue progress or performance suffers.
 While I was aware of these realities, I underestimated how little performance margin there is for communication.
-Several of my attempts at building a fair scheduler compared poorly to work-stealing schedulers because of how thin the margin is.
+Several of my attempts at building a fair scheduler compared poorly to work-stealing schedulers because of the thin communication margin.
 
 Second, the kernel locking, threading, and I/O in the Linux operating system offers very little flexibility, and are not designed to facilitate user-level threading.