diff --git a/docs/add-ons/security.md b/docs/add-ons/security.md
index 5516ab86..f7eb89f9 100644
--- a/docs/add-ons/security.md
+++ b/docs/add-ons/security.md
@@ -33,6 +33,4 @@ As a developer, follow the following best practices to make your add-on secure:
 
 ## Use Home Assistant User backend
 
-Instead of allowing users to set new login credential in plain text config, use the Home Assistant [Auth backend][hassio-api-auth]. You can enable the access to API with `auth_api: true`. Now you are able to send the login credential to auth backend and validate it again Home Assistant.
-
-[supervisor-api-auth]: /api/supervisor/endpoints.md#auth
+Instead of allowing users to set new login credential in plain text config, use the Home Assistant [Auth backend](/docs/api/supervisor/endpoints#auth). You can enable the access to API with `auth_api: true`. Now you are able to send the login credential to auth backend and validate it again Home Assistant.