From 5d8630595d871c2bd4d280f978bfd285ea040035 Mon Sep 17 00:00:00 2001
From: Dametto Luca <45915503+LucaTheHacker@users.noreply.github.com>
Date: Sat, 26 Apr 2025 10:21:03 +0200
Subject: [PATCH] Improved UX

Marked keywords with Capital letters and proper formatting to clarify those are references to actual values/labels

Signed-off-by: Dametto Luca <45915503+LucaTheHacker@users.noreply.github.com>
---
 website/docs/add-secure-apps/providers/oauth2/device_code.md | 4 +++-
 1 file changed, 3 insertions(+), 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 f512b209c8..7eac27d16b 100644
--- a/website/docs/add-secure-apps/providers/oauth2/device_code.md
+++ b/website/docs/add-secure-apps/providers/oauth2/device_code.md
@@ -17,7 +17,9 @@ This type of authentication flow is useful for devices with limited input capabi
 
 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.
 
-authentik doesn't ship with a default flow for this usecase, so it is recommended to create a new flow for this usecase with the designation of _Stage configuration_
+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`.
+
+## 
 
 ### Device-side