From 8c2ba9176b3060cf9f6825a86fa5e30c950eb3b2 Mon Sep 17 00:00:00 2001
From: Dametto Luca <45915503+LucaTheHacker@users.noreply.github.com>
Date: Sat, 26 Apr 2025 10:35:35 +0200
Subject: [PATCH] "Relative vs. absolute paths" rule

Removed full link in favor of relative path

Signed-off-by: Dametto Luca <45915503+LucaTheHacker@users.noreply.github.com>
---
 website/docs/add-secure-apps/providers/oauth2/device_code.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/add-secure-apps/providers/oauth2/device_code.md b/website/docs/add-secure-apps/providers/oauth2/device_code.md
index 553d11d963..bf7d5ead05 100644
--- a/website/docs/add-secure-apps/providers/oauth2/device_code.md
+++ b/website/docs/add-secure-apps/providers/oauth2/device_code.md
@@ -15,7 +15,7 @@ This type of authentication flow is useful for devices with limited input capabi
 
 ### Requirements
 
-This device flow is only possible if the active [brand](https://docs.goauthentik.io/docs/brands) has a device code flow setup. This flow is run _after_ the user logs in, and before the user authenticates.
+This device flow is only possible if the active [brand](../sys-mgmt/brands.md) has a device code flow setup. This flow is run _after_ the user logs in, and before the user authenticates.
 
 authentik doesn't ship with a default flow for this usecase, so it is required to create a new flow for this usecase with the `Designation` of `Stage Configuration`.