diff --git a/doc/papers/2011/europar/lofar.pdf b/doc/papers/2011/europar/lofar.pdf
index 80cc6d9faaea993ef4bf8bdfe469ce9efea93da5..933790a29f9d453fe224acfb4b15b894ec7e3657 100644
Binary files a/doc/papers/2011/europar/lofar.pdf and b/doc/papers/2011/europar/lofar.pdf differ
diff --git a/doc/papers/2011/europar/lofar.tex b/doc/papers/2011/europar/lofar.tex
index 51466b7cc890525a0fb2717c6cf54666c4477bcb..d0982bf4d61c68182ff38311c57adf7823b6530f 100644
--- a/doc/papers/2011/europar/lofar.tex
+++ b/doc/papers/2011/europar/lofar.tex
@@ -202,7 +202,7 @@ Once an output core has received and reordered all of its data, the data are sen
 \section{Performance Analysis}
 \label{Sec:performance}
 
-We will focus our performance analysis on the most challenging cases that are of astronomical interest. In all cases, we respect the real-time nature of our system by limiting the load such that there is at most 0.1\% of data loss, but typically much less. Almost all variance occurs in the networks within the BG/P due to clashes caused by scheduling intricacies. We present measurements for a single BG/P rack.
+We will focus our performance analysis on the most challenging cases that are of astronomical interest. In all cases, we respect the real-time nature of our system by limiting the load such that there is at most 0.1\% of data loss, but typically, data loss is much rarer. Almost all variance occurs in the networks within the BG/P due to clashes caused by scheduling intricacies. We present measurements for a single BG/P rack.
 
 \subsection{Overall Performance}