Index: /anr/section-4.1.tex
===================================================================
--- /anr/section-4.1.tex	(revision 131)
+++ /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.
Index: /anr/section-4.2.tex
===================================================================
--- /anr/section-4.2.tex	(revision 131)
+++ /anr/section-4.2.tex	(revision 132)
@@ -20,8 +20,8 @@
 
 \item[Management of knowledge, Intellectual Property Right (IPR) and Results Exploitation]
-The partners will have to work under the eventual NDA constraints.
+The partners will have to work under eventual NDA constraints.
 Prior Intellectual Property remains property of the concerned partners.
 The exploitation of the results obtained in the project and by each partner involved in the consortium will
-follow the rules written the articles of the Consortium Agreement accepted and signed by
+follow the rules written in the articles of the Consortium Agreement accepted and signed by
 each partner at most 6 months after the project kick-off.
 To manage the exploitation and dissemination plan within the project, six
@@ -32,8 +32,8 @@
 will have to identify namely (and with their address, phone, fax and e-mail):
 \begin{itemize}
-  \item The financial and administrative person authorized and the legal person authorized 
-or at least the scientific and technical.
-  \item A complete and detailed list will be communicated to each partner and to public
-  Authority.
+  \item The financial and administrative person authorized and the legal 
+person authorized or at least the scientific and technical.
+
+  \item A complete and detailed list will be communicated to each partner and to the public Authority.
   \item Mailing lists used by the partners for the day to day communication.
 \end{itemize}
@@ -60,6 +60,5 @@
 For this project format and size, a 12 months review by ANR, based on a yearly progress
 report incorporating milestones reports and deliverables, seems optimum.
-The internal consortium meetings will be six monthly, including a kick-off meeting at the
-start of the project, in our eyes the most important of all, as it phases the partners for
-the start of the project on.
+The internal consortium meetings will be every six months, including a kick-off meeting at the
+start of the project, in our eyes the most important of all, as it phases the partners for the start of the project.
 \end{description}
Index: /anr/section-4.4.tex
===================================================================
--- /anr/section-4.4.tex	(revision 131)
+++ /anr/section-4.4.tex	(revision 132)
@@ -63,7 +63,7 @@
 	Partners have to agree on a convenient exchange format for all tools involved.
 	Because all the HAS tools rely on it, the \xcoach format specification is a
-    crucial step. There are no work-arround but as mentionned in
+    crucial step. There are no work-around but as mentionned in
     section~\ref{xcoach-problem} (page~\pageref{xcoach-problem}) the five academic partners have worked on it
-	for a full year and a first document already exists.
+	for a full year and a preliminary document already exists.
 %\item[\xcoachplus format (\novers{\specXcoachDoc},
 %      \novers{\specXcoachToSystemC}, \novers{\specXcoachToVhdl})]
Index: /anr/section-6.1.tex
===================================================================
--- /anr/section-6.1.tex	(revision 131)
+++ /anr/section-6.1.tex	(revision 132)
@@ -134,5 +134,5 @@
 more than 400 researchers, under the umbrella of the CNRS (Centre National de la Recherche Scientifique). 
 The \og System on Chip \fg Department of LIP6 consists of  80 people, including 40 PHD students. 
-The research focus on CAD tools and methods for VLSI and System on Chip design. 
+The research focuses on CAD tools and methods for VLSI and System on Chip design. 
 \parlf
 The annual budget is about 3 M{\texteuro}, and 1.5 M{\texteuro} are from research contracts. 
@@ -161,5 +161,5 @@
 \xilinx is the world leader in the domain of programmable logic circuits (FPGA).
 \xilinx develops on one hand several FPGA architectures (CoolRunner, Spartan and Virtex
-families) and in the other hand a software solution allowing exploiting the
+families) and on the other hand a software solution allowing exploiting the
 characteristics of these FPGA.
 \parlf
@@ -228,7 +228,7 @@
 
 Thales is international, but Europe-centered. Research \& Development activities are
-disseminated, and corporate Research and Technology is concentrated in Centres in France,
+disseminated, and corporate Research and Technology is concentrated in Centers in France,
 the United Kingdom and the Netherlands.
-The R\&T in Thales emphasizes more particularly on critical information systems,
+The R\&T in Thales is focused mostly on critical information systems,
 processing, control and cognitive systems, and autonomous systems.
 
@@ -303,5 +303,5 @@
 For manufacturing and industrialization, \navtel works with ISO certified partners.
 The company clients include the CNES, ThalÚs Alenia Space, ThalÚs Communication, EADS,
-Eutelsat, AIRBUS, Schlumberger. \navtel participates from the R\&D phase through to the
+Eutelsat, AIRBUS, Schlumberger. \navtel participates from the R\&D phase up to the
 system delivery.
 
Index: /anr/section-6.2.tex
===================================================================
--- /anr/section-6.2.tex	(revision 131)
+++ /anr/section-6.2.tex	(revision 132)
@@ -2,5 +2,5 @@
 Université Pierre et Marie Curie.
 Alain Greiner is the initiator and the main architect of the SoCLib project.
-This ANR plat-form for virtual prototyping of MPSoCs involved 6 industrial companies 
+This ANR platform for virtual prototyping of MPSoCs involved 6 industrial companies 
 (including ST Microelectronics and Thales) and ten academic laboratories 
 (5 of them are involved in the Coach project).
@@ -16,8 +16,8 @@
 From 1986 to 1990, he worked for the french BULL company, as team leader,
 in charge of designing the Basic Processing Unit for the BULL 
-DPS7000 computer, the most powerfull mainframe from the family.
+DPS7000 computer, the most powerfull mainframe of the family.
 \item
 In 1990, Alain Greiner joined UPMC, as Professor and became the head of the
-MASI laboratory in 1994. From 2000, he was the head of the Hardware Department
+MASI laboratory in 1994. From 2000, he was head of the Hardware Department
 of the LIP6 laboratory.
 \item