Continuous-Integration-and-Continuous-Deployment.md

@@ -30,13 +30,11 @@ Depending on their domain, they carry different prefixes:
 * `SSH_` for the review app hosted on [www3.tuhh.de]()
 * `TUHH_` for the deployment on the web server of the institute
 
-Sensible variables (none of them are sensible at the moment) can only be accessed for jobs running on the protected branches `master` and `dev`.
-
-Depending on their suffix they are used at certain parts of the corresponding jobs in the pipeline.
+Sensible variables can only be accessed for jobs running on the protected branches `master` and `dev`. Depending on their suffix, they are used at certain parts of the corresponding jobs in the pipeline.
 
 ## `*_{PRIVATE_KEY,USER,HOST}`
 
-These Variables are used e.g. in `ssh` or `rsync` commands like
+These variables are used e.g. in `ssh` or `rsync` commands like
 
 ```bash
 echo "$REVIEW_SSH_PRIVATE_KEY" | tr -d '\r' | ssh-add -
@@ -82,7 +80,7 @@ The first two stages are testing stages:
 
 #### `docker-test` and `testing`
 
-First all [Docker]() images are tested (or built). The testing stage consists of the following functionality tests: Each time a bash-script with prefix `test_` is executed. All scripts reside in `/bin` and exit with exit code `1` if something goes wrong. In case of a failing test, subsequent states of the pipeline stall.
+First, all [Docker]() images are tested (or built). The testing stage consists of the following functionality tests: Each time a bash-script with prefix `test_` is executed. All scripts reside in `/bin` and exit with exit code `1` if something goes wrong. In case of a failing test, subsequent states of the pipeline stall.
 
 Check the code documentation provided by the scripts for further information.