Minor corrections

Author: dokempf

paper.tex

@@ -111,7 +111,7 @@ \subsection{Pooling: a necessary ingredient}
 Groups of RSEs with tasks spanning the entire organisation necessarily have to offer diverse knowledge.
 Obtaining this diversity of knowledge and experience can also be a challenge, but once it has been established it quickly becomes an asset to the organisation.
 RSEs in centralised groups are interdisciplinary specialists.
-They are interdisciplinary due to their broad experience by working on diverse research topics and their ability to apply a diverse set of research methodoligies.
+They are interdisciplinary due to their broad experience by working on diverse research topics and their ability to apply a diverse set of research methodologies.
 At the same time they are specialists concerning research software and how it can best improve research.
 They are assumed to be able to suggest the most appropriate tools/frameworks and design or architecture patterns for certain research challenges.
 Their diversity in skills (languages, frameworks, front/back-end, UX, management) is welcomed, especially for short-term needs in projects.
@@ -154,9 +154,9 @@ \subsubsection{Existing RSE efforts}
 The field of RSE teams in Germany is currently poorly mapped and very diverse.
 It includes groups with responsibilities across institutions like the Helmholtz HIFIS group\footnote{\url{https://events.hifis.net/category/4/}}\autocite{haupt_hifis_consulting_2021},
 but mostly groups with responsibilities local to their institution.
-Their host within institutions also differs.
-Some like the Scientific Software Center in Heidelberg\footnote{\url{https://www.ssc.uni-heidelberg.de/en}}\autocite{ulusoy_heidelberg_ssc_2024} are part of an interdisciplinary center, goverend directly researchers.
-Others like the Competence Center Digital Research (zedif) in Jena\footnote{\url{https://www.zedif.uni-jena.de/en/}} are part of the central university research support infrastructure and are goverend by the institutional leadership.
+Their anchoring within institutions also differs:
+Some like the Scientific Software Center in Heidelberg\footnote{\url{https://www.ssc.uni-heidelberg.de/en}}\autocite{ulusoy_heidelberg_ssc_2024} are part of an existing interdisciplinary research institution.
+Others like the Competence Center Digital Research (zedif) in Jena\footnote{\url{https://www.zedif.uni-jena.de/en/}} are part of the central university research support infrastructure and are goverened by the institutional leadership.
 Yet others have a project character, like Suresoft in Braunschweig\footnote{\url{https://suresoft.dev/}}~\autocite{Blech2022}.
 Another national pioneer is the Göttingen State and University Library where RSE services are part of the library service portfolio.
 
@@ -172,7 +172,7 @@ \subsubsection{Existing RSE efforts}
 While we focus on Germany in this paper, it is beneficial to review how other countries approach research software.
 In the UK, which we choose as example for being the oldest in terms of RSE, many universities started initiating dedicated RSE units about a decade ago~\autocite{Crouch2013, KDL}.
 The successful establishment of these units is a role model for similar research performing organisations worldwide.
-A range of already-existing RSE units in the UK can be seen on this (incomplete) map: \url{https://society-rse.org/community/rse-groups/}.
+A range of already existing RSE units in the UK can be seen on this (incomplete) map: \url{https://society-rse.org/community/rse-groups/}.
 In the UK, almost all grant applications include software development in their budget.
 This allocated money can then be utilised to delegate/dispatch a central RSE person or group into a research project for a few weeks or months as necessary.