diff --git a/docs/Manual/Security/Starter/README.md b/docs/Manual/Security/Starter/README.md
index 90319987..0a2c83fe 100644
--- a/docs/Manual/Security/Starter/README.md
+++ b/docs/Manual/Security/Starter/README.md
@@ -11,8 +11,8 @@ the _root_ user will be created with an _empty_ password.
 
 In order to the change the password of the _root_ user, you can:
 
-- Open the ArangoDB web UI and change the password from there. [More information](../Programs/WebInterface/Users.md).
-- Open an ArangoSH shell and use the function _users.replace_. [More information](../Administration/ManagingUsers/InArangosh.md#replace).
+- Open the ArangoDB web UI and change the password from there. [More information](../../Programs/WebInterface/Users.md).
+- Open an ArangoSH shell and use the function _users.replace_. [More information](../../Administration/ManagingUsers/InArangosh.md#replace).
 
 In case you would like to automate the _root_ password change, you might use the 
 _--javascript.execute-string_ option of the _arangosh_ binary, e.g.:
@@ -27,7 +27,7 @@ where "mypwd" is the new password you want to set.
 
 If your _Starter_ deployment has authentication turned off, it is suggested to
 turn it on using a _JWT secret_ file. For more information on this topic, please
-refer to the _Starter_ [Option](../Programs/Starter/Options.md#authentication-options) page.
+refer to the _Starter_ [Option](../../Programs/Starter/Options.md#authentication-options) page.
 
 Note that you cannot easily turn authentication on/off once your deployment
 has started for the first time. It is possible to stop all _Starters_ and then