diff --git a/doc/workflow/forking_workflow.md b/doc/workflow/forking_workflow.md
index 32cee3e4f3c7c3253e96eb750ba63ce8bc857a39..dee9e432140254a42637f766d189740a3b2c6cac 100644
--- a/doc/workflow/forking_workflow.md
+++ b/doc/workflow/forking_workflow.md
@@ -8,12 +8,12 @@ to. If you do have write access, we recommend using the **[Code Branching Workfl
 In order to create a fork of a project, all you need to do is click on the fork button located on the top right side
 of the screen, close to the project's URL and right next to the stars button.
 
-![Fork button](/forking/fork_button.png)
+![Fork button](forking/fork_button.png)
 
 Once you do that you will see a screen where you can choose the namespace, to where you want to add the fork. This page
 will contain the groups you have write access to. Choose one of the groups and the project will be added there.
 
-![Groups view](/forking/groups.png)
+![Groups view](forking/groups.png)
 
 After the forking is done, you can start working on the newly created repository. There you will have full Owner access,
 so you can set it up as you please.
@@ -23,11 +23,11 @@ so you can set it up as you please.
 Once you are ready to send your code back to the main project, you need to create a Merge request. Choose your forked
 project's main branch as the source and the original project's main branch as the destination and create the merge request.
 
-![Selecting branches](/forking/branch_select.png)
+![Selecting branches](forking/branch_select.png)
 
 You can then assign the Merge Request to someone so they can review your changes. After they have reviewed them, the will
 be added to the main project, if maintainer chooses to do so.
 
-![New merge request](/forking/merge_request.png)
+![New merge request](forking/merge_request.png)