semantic line breaks only

Author: knarrff

paper.tex

@@ -65,26 +65,21 @@ \section{Introduction}
 \textbf{Software:}\\
 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
+Foundational algorithms, the software itself, as well as scripts and computational workflows that were created
 during the research process or for a research purpose, across all domains of research.
-This definition is broader than in~\autocite{FAIR4RS} and is the outcome of a recent
-discussion in~\autocite{Gruenpeter2021}.\\
+This definition is broader than in~\autocite{FAIR4RS} and is the outcome of a recent discussion in~\autocite{Gruenpeter2021}.\\
 \textbf{Research software engineers:}\\
-People who
-create or improve research software and/or the structures that the software interacts with
-in the computational ecosystem of a research domain.
-They are highly skilled team members who may also choose to conduct their own research as
-part of their role.
-However, we also recognise that many RSEs have chosen specifically to focus on a technical
-role as an alternative to a traditional research role because they enjoy and wish to focus
-on the development of research software.\\
+People who create or improve research software and/or the structures that the software interacts with in the computational ecosystem of a research domain.
+They are highly skilled team members who may also choose to conduct their own research as part of their role.
+However, we also recognise that many RSEs have chosen specifically to focus on a technical role as an alternative to a traditional research role
+ because they enjoy and wish to focus on the development of research software.\\
 \textbf{Researchers:}\\
 We refer by researchers to all others involved in research or in research supporting organisations such as \eg{} libraries,
 hence those that are at most sporadically performing RSE actions.
 
 Furthermore, we will use the general term \textbf{RSE Hub} for the central RSE team throughout this paper.
-These RSE Hubs can take the form of, e.g., full RSE units, smaller RSE groups, Open Source Program Office (OSPOs), virtually across multiple units or combined under one single leader, depending on the evironment of the particular research organisation under consideration.
+These RSE Hubs can take the form of, e.g., full RSE units, smaller RSE groups, Open Source Program Office (OSPOs), virtually across multiple units or combined under one single leader,
+ depending on the evironment of the particular research organisation under consideration.
 All of these implementations are considered here, taking into account the large variety of research environments in Germany.
 
 \section{Motivation}