Merge pull request #40 from ocaisa/tweaks

Some typos and rephrasing

Author: boegel

isc26-EESSI/audience.tex

@@ -1,13 +1,13 @@
 %This tutorial is intended for
 \begin{itemize}
-    \item Researchers who want to empower themselves to use a uniform software stack without compromising on
+    \item Researchers looking to empower themselves with a software stack that is consistent across architectures without compromising on
           performance; %on top of what is provided centrally by the HPC support team;
     \item Developers who build and test their software across different HPC systems and the cloud;
     \item System administrators and user support teams, responsible for the operational aspects of HPC systems and concerned about
           hardware optimised scientific software installations;
 %     \item user support teams who need to provide a consistent central software stack for end users, and want to do so in
 %           a reproducible way;
     %\item Cloud and CI users, who want to use a common stack of optimised scientific software installations;
-    \item System manufacturers and integrators interested in state-of-the-art software installation tools, who want to
+    \item System manufacturers and integrators interested in state-of-the-art software installation approaches, who want to
           leverage the collective expertise incorporated in EasyBuild and EESSI.
 \end{itemize}

isc26-EESSI/description.tex

@@ -109,8 +109,8 @@ \subsection*{Motivation \& goal}
 %To provide optimized installations of scientific software stacks for a diverse set of system architectures, the EESSI
 %project consists of 3 layers, which are constructed by leveraging various established open source software projects,
 %see Figure~\ref{fig:eessi-high-level-overview}.
-To provide optimized installations of scientific software stacks for a diverse set of system architectures
-The high-level design of EESSI consists of 3 layers, which are constructed by leveraging various established open source software projects,
+In order to provide optimized installations of scientific software stacks for a diverse set of system architectures,
+the high-level design of EESSI consists of 3 layers which are constructed by leveraging various established open source software projects,
 see Figure~\ref{fig:eessi-high-level-overview}. At the time of writing, EESSI includes over 600 unique software projects
 and supports 14 different CPU microarchitectures and 3 generations of NVIDIA GPUs, which totals to over 16,000 software installations.
 % the filesystem layer to distribute the software stack; the compatibility layer to level the ground across different client operating systems; the software layer to run optimized applications and provided their dependencies.
@@ -177,9 +177,9 @@ \subsection*{EESSI Community + Recognition and Adoption}
 \subsection*{Tutorial scope and organisation}
 
 This tutorial is an introduction to EESSI, covering its motivation, goals, high-level design, and the use cases it
-enables (like portable workflows, usage a CI environment, building software on top of it, etc.).
+enables (like portable workflows, usage in a CI environment, building software on top of it, etc.).
 Through guided hands-on exercises attendees will get a thorough understanding of the basics,
-and be incentived and empowered to learn more and use it in their own daily workflow.
+and be incentivised and empowered to learn more and use it in their own daily workflow.
 
 %The main features and functionalities of EESSI are highlighted, as well as the different ways to access the software stack, such as native installation, use in an HPC
 %production setup, or without administrator privileges.