From c4271b1ff764f25724a2e00880c46019ceaa8114 Mon Sep 17 00:00:00 2001 From: Tana M Berry Date: Wed, 30 Apr 2025 17:53:59 -0500 Subject: [PATCH] argh --- 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 bfe39257e7..033e9a656d 100644 --- a/website/docs/add-secure-apps/providers/oauth2/device_code.md +++ b/website/docs/add-secure-apps/providers/oauth2/device_code.md @@ -1,6 +1,6 @@ # Device code flow -The device code flow is also known as device flow or device authorization grant flow. This type of authentication flow is useful for devices with limited input capabilities and/or devices without browsers. The Request for Comments (RFC) 8628) abstract for this flow states: +The device code flow is also known as _device flow_ or _device authorization grant flow_. This type of authentication flow is useful for devices with limited input capabilities and/or devices without browsers. The Request for Comments (RFC) 8628) abstract for this flow states: > 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.