Index: doc/papers/concurrency/Paper.tex
===================================================================
--- doc/papers/concurrency/Paper.tex	(revision 9fb8f01d220653c3f0b46da4a12ae9e1302579b9)
+++ doc/papers/concurrency/Paper.tex	(revision 3d5701e14a6d4f307682f895f813314afe663a4d)
@@ -239,4 +239,6 @@
 \lstMakeShortInline@%
 
+\newcommand{\commenttd}[1]{{\color{red}{Thierry : #1}}}
+
 \let\OLDthebibliography\thebibliography
 \renewcommand\thebibliography[1]{
@@ -1163,5 +1165,5 @@
 % }
 % int main() {
-% 
+%
 % 	for ( int i = 0; i < 10; i += 1 ) {
 % 		printf( "%d\n", fib() );
@@ -1834,5 +1836,5 @@
 		if ( random() % 3 ) transfer( b1, b2, 7 );
 	}
-}    
+}
 int main() {
 	`Person p1 = { b1, b2 }, p2 = { b2, b1 };`
@@ -1864,5 +1866,5 @@
 		if ( random() % 3 ) transfer( b1, b2, 7 );
 	}
-}    
+}
 int main() {
 	`thread p1(person, ref(b1), ref(b2)), p2(person, ref(b2), ref(b1));`
@@ -2739,5 +2741,5 @@
 % \section{Parallelism}
 % \label{s:Parallelism}
-% 
+%
 % Historically, computer performance was about processor speeds.
 % However, with heat dissipation being a direct consequence of speed increase, parallelism is the new source for increased performance~\cite{Sutter05, Sutter05b}.
@@ -2746,8 +2748,8 @@
 % However, kernel threads are better as an implementation tool because of complexity and higher cost.
 % Therefore, different abstractions are often layered onto kernel threads to simplify them, \eg pthreads.
-% 
-% 
+%
+%
 % \subsection{User Threads}
-% 
+%
 % A direct improvement on kernel threads is user threads, \eg Erlang~\cite{Erlang} and \uC~\cite{uC++book}.
 % This approach provides an interface that matches the language paradigms, gives more control over concurrency by the language runtime, and an abstract (and portable) interface to the underlying kernel threads across operating systems.
@@ -2755,5 +2757,5 @@
 % Like kernel threads, user threads support preemption, which maximizes nondeterminism, but increases the potential for concurrency errors: race, livelock, starvation, and deadlock.
 % \CFA adopts user-threads to provide more flexibility and a low-cost mechanism to build any other concurrency approach, \eg thread pools and actors~\cite{Actors}.
-% 
+%
 % A variant of user thread is \newterm{fibres}, which removes preemption, \eg Go~\cite{Go} @goroutine@s.
 % Like functional programming, which removes mutation and its associated problems, removing preemption from concurrency reduces nondeterminism, making race and deadlock errors more difficult to generate.
