diff --git a/docs.it4i/general/tools/cicd.md b/docs.it4i/general/tools/cicd.md
index 14c479c94c37af72baf9189696a59c5bb2a3060e..df6728b95ebc7ec123458d9d73754f0b6a56d733 100644
--- a/docs.it4i/general/tools/cicd.md
+++ b/docs.it4i/general/tools/cicd.md
@@ -24,7 +24,7 @@ For more information about the Jacamar CI driver, please visit [the official doc
 
 The execution of CI pipelines works as follows. First, a user in the IT4I GitLab server triggers a CI pipeline (for example, by making push to a repository, etc.). Then, the jobs, which the pipeline consists of, are sent to the corresponding runner, running in the login node. Lastly, for every CI job, the runner clones the repository (or just fetches changes to an already cloned one, if there are any), restores [cache][3], downloads [artifacts][4] (if specified), and submits the job as a Slurm job to the corresponding HPC cluster using the `sbatch` command. After each execution of a job, the runner reports the results back to the server, creates cache, and uploads artifacts (if specified).
 
-<img src="../../img/it4i-ci.svg" title="IT4I CI" width="750">
+<img src="../../../img/it4i-ci.svg" title="IT4I CI" width="750">
 
 !!! note
     The GitLab runners at Karolina and Barbora are able to submit (as a Slurm job) and execute 32 CI jobs concurrently, while the runner at Complementary systems can submit 16 jobs concurrently at most. Jobs above this limit are postponed in submission to respective slurm queue until a previous job has finished.