haavee's changes/remarks

Some remarks have been placed inline in a highlighted box using the new \haavee{} command.

The text of the deliverable can easily be rid of those by redefining the \haavee{} command to be a no-op, effectively discarding its argument.

contents/1-intro.tex

@@ -3,7 +3,7 @@
 
 This document is \gls{ESCAPE} project deliverable D5.3: “performance assessment of the initial Science Platform prototype” \autocite{ESCAPE-GA}.
 
-\pgls{ESAP} is the primary deliverable of \gls{ESCAPE} Work Package 5.
+\pgls{ESAP} is the primary deliverable of \gls{ESCAPE} Work Package 5 (WP5).
 It serves a key part of the interface between the services delivered by \gls{ESCAPE} and the scientific community, providing mechanisms by which users can discover, access, and analyze the data, workflows, and services which the \glspl{ESFRI} affiliated with \gls{ESCAPE}, and other projects, publish to the \gls{EOSC}.
 
 At the time of writing, the \gls{ESCAPE} project is approximately at its mid-point.
@@ -18,7 +18,7 @@ For the purposes of this document, three separate, but closely related, aspects
 
 \item{To what extent does the prototype meet the requirements which were specified in \citetitle{ESCAPE-D5.2} \autocite{ESCAPE-D5.2}?}
 
-\item{To what extent does the prototype meet the needs currently being expressed by the \gls{ESCAPE}-affiliated \glspl{ESFRI}, as expressed through the use cases currently being collaged by the project?}
+\item{To what extent does the prototype meet the needs currently being expressed by the \gls{ESCAPE}-affiliated \glspl{ESFRI}, as expressed through the use cases currently being collected by the project?}
 
 \item{What other goals or desires for \pgls{ESAP} might the community express through a workshop and accompanying call for feedback?}
 
@@ -28,7 +28,7 @@ Note that none of these topics directly address “performance” as narrowly d
 In practice, \pgls{ESAP} is unlikely ever to be a limiting factor here: it acts merely as a conduit to help users interact with other systems.
 Those other systems handle bulk data storage, transport and compute; they do not place substantial load on \pgls{ESAP} itself.
 Furthermore, while the \pgls{ESAP} system itself has been designed to be scalable where appropriate, at this stage in development we have focused on prototyping and exploring capabilities, rather than raw throughput.
-In short, therefore, a raw computational performance measurement is not regarding as being significant for the terms of this report.
+In short, therefore, a raw computational performance measurement is not regarded as being significant for the terms of this report.
 
 This report is structured as follows.
 It starts by describing the vision for \pgls{ESAP} in \cref{sec:vision}.