Rephrase Technology milestones for 2021 according to review suggestions

* The three suggested milstones of the HIFIS Software Technology team
needed to be rephrased.

_roadmap/software/2021-02-01-tasks.md

@@ -5,18 +5,11 @@ service: software
 ---
 
 ## Helmholtz-wide GitLab on new Ansible-managed Infrastructure
-The [GitLab pilot service](https://gitlab.hzdr.de) will be deployed to a
-new Ansible-managed infrastructure.
-[Ansible](https://www.ansible.com/) is a well-established configuration
-management tool.
-Maintenance and further developments of the Helmholtz-wide GitLab will be done
-with this tool.
-Other research centres are then able to use the so called
-[Ansible playbook](https://gitlab.hzdr.de/hifis-software-deployment/gitlab)
-to set up and run their own GitLab instance on dedicated servers in their own
-infrastructure with ease.
+The [GitLab service](https://gitlab.hzdr.de) will be deployed to a
+new [Ansible-managed infrastructure](https://gitlab.hzdr.de/hifis-software-deployment/gitlab)
+providing an enhanced maintainability and scalability.
 Access to this Helmholtz-wide GitLab will be granted to all people affiliated
-with the Helmholtz Association and partners to foster cross-centre
-collaboration in research software projects.
-If users encounter any issues, they can report them in the respective
-[issue-tracker](https://gitlab.hzdr.de/fwcc/HZDR-GitLab).
+with the Helmholtz Association and partners to foster cross-center
+collaboration.
+If users encounter any issues, they can report them via
+[the HIFIS helpdesk](mailto:support@hifis.net?subject=%5BGitLab%5D%3A%20Add%20Request%20description).

_roadmap/software/2021-06-01-tasks.md

@@ -5,16 +5,12 @@ service: software
 ---
 
 ## CI as a Service as a Pilot Service
+We consider Continuous Integration (CI) an important aspect in a
+modern software engineering workflow.
+Easy-to-use CI resources should be available for all Helmholtz scientists.
 Beside the [Helmholtz-wide GitLab](https://gitlab.hzdr.de) many Helmholtz
-centres run their own GitLab instances on dedicated infrastructure in their
-centre.
-This is also the case for GitLab's Continuous Integration (CI) runners,
-i.e. servers that are running CI pipelines, they are hosted by each centre
-separately.
-In order to bundle these resources and enable research software projects
-that are hosted on these GitLab instances to do Continuous Integration,
-CI will be offered as a service.
-CI runners that will be available for the Helmholtz-wide GitLab will then
-also be available to other GitLab instances of other centres.
-In order to start with these services a few pilot centres will be selected that
-will host these CI runners as a service at the beginning.
+centers run their own GitLab instances on dedicated infrastructure in their
+center.
+In order to bundle resources and enable research software projects
+to easily use CI for their projects, CI will be offered as a service.
+In this milestone we would like to set up CI as a Service and test it with a few pilot centers.

_roadmap/software/2021-12-01-tasks.md

@@ -5,11 +5,11 @@ service: software
 ---
 
 ## Conceptualize Binder / ShinyR Integration into GitLab
-There are tools like [Binder](https://mybinder.org/)
-and [ShinyR](https://shiny.rstudio.com/)
-available that enable research software developers to publish their Jupyter
-notebooks or R scripts in interactive web-apps.
-This functionality will be integrated into the
-[Helmholtz-wide GitLab](https://gitlab.hzdr.de).
+Allowing scientists or reviewers to easily interact with computational environments
+can be considered a key aspect for reproducible and easy-to-use research software.
+Integrating tools like [Binder](https://mybinder.org/) or [ShinyR](https://shiny.rstudio.com/)
+into the [Helmholtz-wide GitLab](https://gitlab.hzdr.de)
+will allow scientists to easily make their research software product available
+to others without the need for installing and configuring tools locally.
 First and foremost, a concept will be elaborated on how this integration
 could be realized.