Todd's editorial pass at the 2.3.5 subproject descriptions.

Introduction.tex

@@ -83,7 +83,7 @@ \subsection{ECP ST Project Restructuring}\label{subsect:ProjectRestructuring}
 	\item 40 ST SC-funded L4 subprojects to 30.
 	\begin{itemize}
 	\item \pmr – 13 to 9, \tools - 6 to 6, \mathlibs - 7 to 6, \dataviz - 10 to 7, \ecosystem - 4 to 3.
-	\item Includes 2 new L4 subprojects in SW Ecosystem.
+	\item Includes 2 new L4 subprojects in \ecosystem.
 	\end{itemize}
 	\item 15 ST NNSA-funded projects transferred to new NNSA ST L3. Consolidated from 15 to 3 L4 subprojects.
 	\item No more small subprojects.

abstract.tex

@@ -27,7 +27,7 @@
 
 \textbf{\dataviz:} ECP ST has a large collection of data management and visualization products that provide essential capabilities for compressing, analyzing, moving and managing data.  These tools are becoming even more important as the volume of simulation data we produce grows faster than our ability to capture and interpret it.   See Section~\ref{subsect:dataviz}.
 
-\textbf{\ecosystem:} This technical area of ECP ST provides important enabling technologies such as Spack~\cite{gamblin+:sc15}, a from-source build and package manager, and container environments for high-performance computers.  This area also provides the critical resources and staffing that will enable ECP ST to perform continuous integration testing, and product releases.  Finally, this area engages with software and system vendors, and DOE facilities staff to assure coordinated planning and support of ECP ST products.   See Section~\ref{subsect:ecosystem}.
+\textbf{\ecosystem:} This technical area of ECP ST provides important enabling technologies such as Spack~\cite{gamblin+:sc15}, a from-source build and package manager, container environments for high-performance computers, and a toolkit of reusable components for scientific workflow management systems.  This area also provides the critical resources and staffing that will enable ECP ST to perform continuous integration testing, and product releases.  Finally, this area engages with software and system vendors, and DOE facilities staff to assure coordinated planning and support of ECP ST products.   See Section~\ref{subsect:ecosystem}.
 
 \textbf{\nnsa:} This technical area brings into one L3 area all of the NNSA-funded work in ECP ST for easier coordination with other project work at the NNSA labs.  Introducing this L3 enables continued integrated planning with the rest of ECP ST while permitting flexible coordination within the NNSA labs.   See Section~\ref{subsect:nnsa}.
 

projects/2.3.5-Ecosystem/2.3.5.01-Ecosystem-SDK/2.3.5.01-Ecosystem-SDK.tex

@@ -3,7 +3,7 @@ \subsubsection{\stid{5.01} Software Development Kits} \label{subsubsect:ecosyste
 \paragraph{Overview} The ST Software Development Kit (SDK) project supports a set of activities focused on 
 \begin{itemize}
 \item establishing Community Policies aimed at increasing the interoperability between and sustainability of ST software packages, using the xSDK~\cite{xsdk:homepage} community package and installation policies~\cite{xsdk-policies:homepage} as a model.
-\item coordinating the delivery of ECP ST products through the Extreme-Scale Scientific Software Stack (E4S)~\cite{e4s:homepage}, a comprehensive and coherent set of software tools, to all interested stakeholders on behalf of ECP ST. This includes ECP applications and the broader open source community.
+\item coordinating the delivery of ECP ST products through the Extreme-Scale Scientific Software Stack (E4S)~\cite{e4s:homepage}, a comprehensive and coherent set of software tools, to all interested stakeholders on behalf of ECP ST, including ECP applications and the broader open source community.
 \end{itemize}
 
 An ECP ST SDK is a collection of related software products (called packages) where coordination across package teams will improve usability and practices and foster community growth among teams that develop similar and complementary capabilities.  SDKs have the following attributes:
@@ -74,11 +74,11 @@ \subsubsection{\stid{5.01} Software Development Kits} \label{subsubsect:ecosyste
 Current and near-term efforts include:
 
 \begin{itemize}
-\item  Defining a process for documenting and verifying compatibility with E4S  Community Policies.
+\item  Defining a process for documenting and verifying compatibility with E4S Community Policies.
 \item  Assisting with E4S deployment to computing Facilities.
 \item  Adding additional ST software to E4S.
 \item  Assisting with establishing workflows around the maintenance of multi-package CI builds at computing facilities.
-\item  Starting work on Version 2 of the E4S Community Policie.
+\item  Starting work on Version 2 of the E4S Community Policies.
 \item  Supporting SDK-specific efforts focused on the needs of each SDK, with a particular emphasis on sustainability.
 \end{itemize}
 

projects/2.3.5-Ecosystem/2.3.5.09-SW-Packaging/2.3.5.09-SW-Packaging.tex

@@ -103,14 +103,14 @@ \subsubsection{\stid{5.09} Software Packaging Technologies} \label{subsubsect:sw
 
 \begin{enumerate}
 \item Released {\tt archspec}\footnote{https://github.com/archspec/archspec/},
-      a library for lableing and distributing CPU microarchitectures, as a
+      a library for labeling and distributing CPU microarchitectures, as a
       spin-off project from Spack.
 
 \item Developed the {\tt spack containerize} command that enables users to
       easily build lightweight containers from Spack environments.
 
 \item Worked with the E4S team to get E4S packages building on the Ascent
-      machine at OLCF, onNERSC's Cori machine, and in continuous integration in
+      machine at OLCF, on NERSC's Cori machine, and in continuous integration in
       Amazon Web Services (on optimized {\tt skylake} instances).
 
 \item Continued to support ECP ST teams and conducted a survey to better

projects/2.3.5-Ecosystem/2.3.5.10-ExaWorks/2.3.5.10-ExaWorks.tex

@@ -33,7 +33,7 @@ \subsubsection{\stid{5.10} ExaWorks} \label{subsubsect:exaworks}
 grain tasks in dynamic workflows. On the non-technical side, the myriad WMSs
 that exist, lack of reusable WMS components, and the lack of clear user
 guidance when selecting a WMS has resulted in a disjoint workflows community
-that tends towards building ad hoc or bespoke solutions rather than adopting
+that tends toward building ad hoc or bespoke solutions rather than adopting
 and extending existing solutions.
 
 Specific challenges include: 
@@ -48,7 +48,7 @@ \subsubsection{\stid{5.10} ExaWorks} \label{subsubsect:exaworks}
 \end{enumerate}
 
 \paragraph{Solution Strategy}
-The phase one ExaWorks project will lay the foundation for an inherently
+The ExaWorks project will lay the foundation for an inherently
 \textit{new approach} to workflows: establishing the ExaWorks toolkit (see
 Figure~\ref{fig:arch}) by assembling shared components from existing workflow
 projects. The ExaWorks toolkit will provide a robust, well-tested, documented,
@@ -68,14 +68,14 @@ \subsubsection{\stid{5.10} ExaWorks} \label{subsubsect:exaworks}
   \caption{ExaWorks Toolkit\label{fig:arch}}
 \end{wrapfigure} 
 
-The goals of the phase one project are to instantiate the ExaWorks community, 
+The goals of the initial phase of the project are to instantiate the ExaWorks community, 
 bringing together workflow tool developers, ECP applications, and DOE compute facility representatives.  Specifically, it will:
 \begin{enumerate}
-    \item Engage the facilities to survey the state of workflow tools and capabilities and ways in which ExaWorks can enhance their capabilities
-    \item Establish an advisory board composed of representatives of DOE compute facilities, ECP applications, and workflow tools, to guide and advise ExaWorks
+    \item Engage the facilities to survey the state of workflow tools and capabilities and ways in which ExaWorks can enhance their capabilities;
+    \item Establish an advisory board composed of representatives of DOE compute facilities, ECP applications, and workflow tools, to guide and advise ExaWorks;
     \item Survey ECP applications teams to identify the tools currently being used and to identify common challenges and needs;
-    \item Assemble a functional design working group to develop a community-centered draft function design.
-    \item Collaborate with ECP applications to develp a proof-of-concept integration using a shared functional component as defined by the draft design, in an ECP application
+    \item Assemble a functional design working group to develop a community-centered draft function design; and
+    \item Collaborate with ECP applications to develop a proof-of-concept integration using a shared functional component as defined by the draft design, in an ECP application.
 \end{enumerate}
 
 \paragraph{Recent Progress}
@@ -93,7 +93,7 @@ \subsubsection{\stid{5.10} ExaWorks} \label{subsubsect:exaworks}
 
 
 \paragraph{Next Steps}
-The remainder of this phase one effort focuses on four important areas. 
+The remainder of this initial effort focuses on four important areas. 
 First, continuing to grow the ExaWorks community by engaging with ECP 
 applications, facilities, and WMS teams. 
 Second, working with these partners and stakeholders to produce a draft