From 3b6de494c958f29fe5e86e41cb86bac078ae2ec1 Mon Sep 17 00:00:00 2001
From: Dametto Luca <45915503+LucaTheHacker@users.noreply.github.com>
Date: Sat, 26 Apr 2025 10:09:15 +0200
Subject: [PATCH] Improved RFC reference

Replaced "abilities" with "capabilities" to better reflect RFC wording, added extended summary from RFC to ensure complete and clear understanding.

Signed-off-by: Dametto Luca <45915503+LucaTheHacker@users.noreply.github.com>
---
 .../add-secure-apps/providers/oauth2/device_code.md   | 11 ++++++++++-
 1 file changed, 10 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 3870bbf178..b7dfce2dc2 100644
--- a/website/docs/add-secure-apps/providers/oauth2/device_code.md
+++ b/website/docs/add-secure-apps/providers/oauth2/device_code.md
@@ -2,7 +2,16 @@
 
 (Also known as device flow and [RFC 8628](https://datatracker.ietf.org/doc/html/rfc8628))
 
-This type of authentication flow is useful for devices with limited input abilities and/or devices without browsers.
+This type of authentication flow is useful for devices with limited input capabilities and/or devices without browsers.
+
+> The OAuth 2.0 device authorization grant is designed for Internet-connected
+> devices that either lack a browser to perform a user-agent-based
+> authorization or are input constrained to the extent that
+> requiring the user to input text in order to authenticate during the
+> authorization flow is impractical. It enables OAuth clients on such
+> devices (like smart TVs, media consoles, digital picture frames, and
+> printers) to obtain user authorization to access protected resources
+> by using a user agent on a separate device.
 
 ### Requirements