diff --git a/NEWPROPOSAL/FULLPROP.tex b/NEWPROPOSAL/FULLPROP.tex
index b02e449eecfce158224ef1e2a9b8fcc3cdbe7c21..7f98c1507fa1e4b8a97a3ed1d1cf82fc4985606b 100644
--- a/NEWPROPOSAL/FULLPROP.tex
+++ b/NEWPROPOSAL/FULLPROP.tex
@@ -801,9 +801,9 @@ This annotation system will again be modular, in that any hardware platform may
 This will make the \dzxc system extensible in principle to any sufficiently well-characterised quantum computing platform.
 
 Annotation systems representing the hardware implementation are to be provided by the development environment, using a standardised interface, as developed in \ref{task:backendapi}.
-As a way to demonstrate and to prototype this hardware-dependent annotation layer,  we will study concrete hardware platforms quantum computers based on different technologies: optically linked ion traps (NQIT) in Task~\ref{task:NQIT-model}, and quantum dots (Grenoble) in Task~\ref{task:qdot-model}.
+As a way to demonstrate and to prototype this hardware-dependent annotation layer,  we will study concrete hardware platforms quantum computers based on different technologies: quantum dots (Grenoble) in Task~\ref{task:qdot-model}, and optically linked ion traps (NQIT) in Task~\ref{task:NQIT-model}.
 In both cases we will interact strongly with the experimental groups working on these
-models, who are close colleagues of our consortium members (N.~de Beaudrap for NQIT, and D.~Horsman for Grenoble).
+models, who are close colleagues of our consortium members (D.~Horsman for Grenoble, and N.~de Beaudrap for NQIT).
 Since these architectures are dissimilar, tackling both is an ideal demonstration of our approach. 
 The completion of this phase will allow quantum programs
 generated by the \dzxc system
@@ -860,7 +860,7 @@ We will promote these cross-disciplinary interactions by a number of our planned
 \subsection{Expected impacts}
 \label{sec:expected-impacts}
 
-\newt{Co-Op ZX} significantly advances the state-of-the-art across \newt{six of the seven} expected impacts.% the seventh is out of project scope.
+\newt{The \dzxc system} significantly advances the state-of-the-art across \newt{six of the seven} expected impacts.% the seventh is out of project scope.
 
 \KILL{\texttt{\bfseries \color{red!70!black} [Some of these may need shortening a bit, particularly as we add material for the new Expected Impacts.]}}
 
@@ -931,7 +931,18 @@ All of these are needed to develop the deep compilation system, \newt{so develop
 This \newt{system} opens the prospect of an acceleration in the development of quantum algorithms in a way which can then \newt{easily be adapted} to many different hardware platforms.
 For example, algorithm and protocol designers will not need to interface directly with quantum technologies: the \newt{\dzxc system} does all the compilation and optimisation necessary. This will allow the
 integration of quantum computing into mainstream Computer Science, and so the easy importing of tools (for example, techniques for optimisation or verification) that have been developed over many years. 
-By aiding the development of intuitively accessible programming languages, \newt{the \dzxc system} will also make quantum technologies accessible to a broader range of users and developers. End-users outside quantum physics and computer science will be able to build protocols for use in their own field that do not require them to understand the physical action of the hardware.  
+By aiding the development of intuitively accessible programming
+languages, \newt{the \dzxc system} will also make quantum technologies
+accessible to a broader range of users and developers. End-users
+outside quantum physics and computer science will be able to build
+protocols for use in their own field that do not require them to
+understand the physical action of the hardware.  
+
+The \dzxc system will not be a closed system: our commitment to open
+APIs (See \ref{task:trans1} and \ref{task:backendapi}) and our open
+test suite (~\ref{task:testBench}) will enable users from outside the
+project to integrate new tools and techniques with \dzxc and engage
+the wider community.
 
 The advent of quantum computation, and the diverse set of skills needed to bring an idea from algorithm to implementation, has shown the limitations of traditional subject boundaries. The breadth of expertise of this consortium, and its thematic focus on developing a common language and methodology from quantum technologies will help overcome these limitations within the project and in the wider community.
 
@@ -1200,7 +1211,7 @@ collaboration is a strong point of this project.
 
 \begin{WP}{A quantum compiler stack}{1M}{36M}{wp:frontend}
 \WPleaderLOR
-\WPeffort{12}{14}{32}{12}{12}{3}
+\WPeffort{12}{20}{32}{12}{12}{3}
 \begin{WPaim}
   This WP develops elements of \zx as an abstract intermediate
   compiler language.  We provide interface between \zx and known
@@ -1432,7 +1443,7 @@ We develop practical logical and algorithmic techniques for transforming  ``abst
     \WPdeliverable{M24}{An extended \zx language which expresses
       topological and quantitative properties, with associated
       reasoning techniques.} 
-  \WPdeliverable{M24}{\newt{Setting the state-of-the-art for all forms circuit optimization}.}
+  \WPdeliverable{M24}{\newt{Setting the state-of-the-art for all forms of circuit optimization}.}
         \WPdeliverable{M24}{\newt{Optimization techniques for a variety of computational models}.}
  % \WPdeliverable{M24}{Routines for adding error-correction to \zx programs}
     \WPdeliverable{M24}{Routines for adding error-correction to ZX programs.}
@@ -1481,7 +1492,7 @@ Also machine-dependent error correction here?
     (M15--M30; Responsible: \partnerref{partner:loria}; Involved: \partnerref{partner:grenoble},\partnerref{partner:oxford},\partnerref{partner:gdansk})}{%
     Develop algorithms which, given a collection of constraints
     representing a machine model
-    (c.f.~\ref{task:annotate1}, \ref{task:annotate2}), re-writes \dzxc terms
+    (c.f.~\ref{task:annotate1}, \ref{task:annotate2}), re-writes \zx terms
     to a form which can be executed on that machine model.
 %\BREM{      Develop a specification system for the operations and constraints of a hardware system, in order to specify how to transform a ``logical'' \azx term to a procedure to realise that transformation on a specific machine.}
       }
@@ -1572,12 +1583,12 @@ Staton, Carette.}
     & \ref{wp:admin} 
     & \textbf{TOTAL} \\\hline
 1. Grenoble   &  12 & 12 & 12 & 12 & 3  & 51 \\\hline
-2. LORIA      & 14 & 12 & 9  & 9  & 3  & 47 \\\hline
+2. LORIA      & 20 & 12 & 9  & 9  & 3  & 53 \\\hline
 3. Oxford     & 32 & 14 & 30 & 12 & 2  & 90 \\\hline
 4. CQC        &  12 & 4  & 12 &  6 & 1  & 28 \\\hline
 5. Gdansk     &  12& 30 & 12 & 6 & 4  & 71 \\\hline
 6. Nijmegen   &  3 & 6  & 12 & 0 & 2  & 23 \\\hline
-\textbf{TOTAL}& 85 & 78 & 87 & 45 & 11 & 317   \\\hline 
+\textbf{TOTAL}& 91 & 78 & 87 & 45 & 11 & 317   \\\hline 
   \end{tabular}
 \end{center}}
 
diff --git a/NEWPROPOSAL/Front-Page.pdf b/NEWPROPOSAL/Front-Page.pdf
index 1a007783a7e7d7f6075530bc5bd64efda3bbb36d..1c077765600f82c9995542ecc36b37c5f2e653a8 100644
Binary files a/NEWPROPOSAL/Front-Page.pdf and b/NEWPROPOSAL/Front-Page.pdf differ