Index: anr/section-4.1.tex
===================================================================
--- anr/section-4.1.tex	(revision 126)
+++ anr/section-4.1.tex	(revision 132)
@@ -51,10 +51,10 @@
 \xcoach generated by a plugin into the GNU C compiler (GCC). 
 This allows on the one hand to insure that all the tools will
-accept the same C++ description and on the other hand to make possible
+accept the same C++ description and on the other hand make possible
 their chaining. The front-end tools read a \xcoach description and generate
 a new \xcoach description that exibits more parallelism or implement
-specific instructions for ASIP. The back-end tools read a \xcoach
-description and generate a \xcoachplus description. This is a \xcoach
-description anotated with hardware information (scheduling, binding) required by
+specific instructions for ASIP. The back-end tools read an \xcoach
+description and generate an \xcoachplus description. This is an \xcoach
+description annotated with hardware information (scheduling, binding) required by
 the VHDL and systemC drivers.
 Furthermore, the back-end tools uses a macro-cell library (functional and memory
@@ -71,8 +71,8 @@
 \parlf
 The project is split into 8 tasks numbered from 1 to 8. There are described
-bellow and detailled in section \ref{task-description}.
+below and detailled in section \ref{task-description}.
 \begin{description}
 \item[Task-1: \textit{Project management}]
-    This task relies to the monitoring of the COACH project.
+    This task relates to the monitoring of the COACH project.
 \item[Task-2: \textit{\Backbone}] This task tackles the fundamental points of the
 	project such as the defintion of the COACH inputs and outputs,
@@ -80,5 +80,5 @@
     the design flow.
 \item[task-3: \textit{System generation}] This task addresses the prototyping and
-    the generation of digital system. Apart from HAS that belong to the task 3
+    the generation of digital system. Apart from HAS that belong to task 3
     and 4, its components are those presented figure~\ref{archi-csg}
     (e.g.  \verb!CSG!, operating systems).
@@ -93,5 +93,5 @@
     frequency.
 \item[Task-6: \textit{PC/FPGA communication middleware}]
-    This task pools the features dedicated to HPC. The main are the
+    This task pools the features dedicated to HPC. These are mainly the
     partitioning validation (see figure~\ref{archi-hpc}), the sytem drivers for
     both PC and FPGA-SoC sides, the hardware communication components and
@@ -99,13 +99,13 @@
 \item[Task-7: \textit{Industrial demonstrators}]
     This task groups the demonstrators of the COACH project.
-    Most of them are industrial applications that will be developped with the COACH
-    framework.
-    Others consist in integrating COACH framework as a driver of industrial proprietary
-    design tools.
+    Most of them are industrial applications that will be developped within
+    the COACH framework.
+    Others consist in integrating the COACH framework as a driver of 
+    industrial proprietary design tools.
 \item{Task 8: \textit{Dissemination}}
-    This task relies to the diffusion of the project results.
+    This task concerns the diffusion of the project results.
     It mainly consists of the production of 4 COACH releases (\verb!T0+12!, \verb!T0+18!,
     \verb!T0+24! and \verb!T0+36!)
-    and the publication on a WEB site of a tutorial.
+    and the publication of a tutorial on a WEB site.
 \end{description}
 %
@@ -117,18 +117,18 @@
 Figure~\ref{dependence-task} presents the tasks dependencies.
 "$T_N \longrightarrow T_M$" means that $T_N$ impacts the $T_M$. 
-The more bold is the arrow, the more important is the impact.
+The more bold the arrow, the more important is the impact.
 The graph shows:
 \begin{itemize}
-\item Even that $T4$ and $T5$ functionalities are complementary, their
-developments are independent (thanks to \xcoach internal format).
+\item Notwithstanding that $T4$ and $T5$ functionalities are complementary, 
+their developments are independent (thanks to the \xcoach internal format).
 \item $T3$ slightly depends on $T4$ and $T5$. Indeed, $T3$ may works
-without $T4$ and $T5$ if we limit to digital systems without hardware
-accellerators. 
-\item $T3$ strongly impacts $T6$ but, $T3$ does not depend at all on
-$T6$. So demonstrators ($T7$) of embedded system would not be impacted if
+without $T4$ and $T5$ if we limit ourselves to digital systems without hardware
+accelerators. 
+\item $T3$ strongly impacts $T6$ but $T3$ does not depend at all on
+$T6$. Hence demonstrators ($T7$) of embedded system would not be impacted if
 $T6$ would fail.  
-\item $T2$ drives all the tasks ($T3$, $T4$, $T5$, $T6$) at the heart of
+\item $T2$ drives all the tasks ($T3$, $T4$, $T5$, $T6$) and is at the heart of
 the COACH project.
-\item The demonstrators developped in $T7$, of course, strongly depends on the achievements 
+\item The demonstrators developped in $T7$, of course strongly depends on the achievements 
 of the previous tasks ($T2$, $T3$, $T4$, $T5$, $T6$).
 \item $T8$ and $T1$ respectively depends on and impacts all the other tasks.
