diff --git a/docs.it4i/general/tools/cicd.md b/docs.it4i/general/tools/cicd.md
index dbe1a293fc87ae8e27d2cb3f28cd76d896dbe81e..9520925de9388ed9d5ca4aefc4ed72f74ee31b62 100644
--- a/docs.it4i/general/tools/cicd.md
+++ b/docs.it4i/general/tools/cicd.md
@@ -12,7 +12,7 @@ IT4Innovations maintains a GitLab server (code.it4i.cz), which has built-in supp
 
 Detailed documentation about GitLab CI/CD is available [here][1].
 
-### Karolina, Barbora, and Complementary systems
+### Karolina, Barbora, and Complementary Systems
 
 For all the users, a unified solution is provided to let them execute their CI jobs at Karolina, Barbora, and Complementary systems without the need to create their own project runners. For each of the HPC clusters, a GitLab instance runner has been deployed. The runners are running in the login nodes and are visible to all the projects of the IT4I GitLab server. These runners are shared by all users.
 
@@ -31,7 +31,7 @@ The execution of CI pipelines works as follows. First, a user in the IT4I GitLab
 
 To begin with, a CI pipeline of a project must be defined in a YAML file. The most common name of this file is `.gitlab-ci.yml` and it should be located in the repository top level. For detailed information, see [tutorial][3] on how to create your first pipeline. Additionally, [CI/CD YAML syntax reference][4] lists all possible keywords, that can be specified in the definition of CI/CD pipelines and jobs.
 
-### Execution of CI pipelines at the HPC clusters
+### Execution of CI Pipelines at the HPC Clusters
 
 Every CI job in the project CI pipeline, intended to be submitted as a Slurm job to one of the HPC clusters, must have 3 following keywords specified in its definition.