slight rewording, typo

Author: knarrff

paper.tex

@@ -58,15 +58,12 @@ \section{Introduction}
 We advocate the establishment and support of dedicated, central RSE groups in German research organisations, with clearly defined tasks, contact points, and, in particular, sustained funding, for the benefit of all researchers in their organisation.
 We provide an overview of the various task these teams have and discuss potential realization strategies, learning from already existing examples of such an RSE unit.
 
-Before we motivate the topic of this position paper further, we first introduce the terminology used throught this work.
-Depending on the national research
-environments and processes that readers are familiar with, the notion of the terms \emph{software} and \emph{research} might differ.
+We first introduce the terminology used throught this work.
+Depending on the national research environments and processes that readers are familiar with, the notion of the terms \emph{software} and \emph{research} might differ.
 The term “Research software” is also defined somewhat differently within the community.
-Therefore, to avoid ambiguities, we define them as follows:\\
+Therefore, to avoid ambiguities, we list the ones we use here:\\
 \textbf{Software:}\\
-Source code, documentation, tests, executables
-and all other artefacts that are created by humans during the development process
-that are necessary to understand its purpose.\\
+Source code, documentation, tests, executables and all other artifacts that are created by humans during the development process that are necessary to understand its purpose.\\
 \textbf{Research software:}\\
 Foundational algorithms, the software itself,
 as well as scripts and computational workflows that were created