Claire update to edit headings and style

Author: clairekinde11

src/content/docs/authenticate/device-authorization-flow/overview.mdx

@@ -10,20 +10,18 @@ relatedArticles:
   - 28c6e830-8e82-4bf8-aab7-87ebafeb68e4
 ---
 
-Device Authorization Flow (RFC 8628) enables OAuth 2.0 authorization for devices with limited input capabilities, such as smart TVs, gaming consoles, or IoT devices. Users authenticate on a secondary device (like a phone or computer) while the primary device receives the access token.
+Kinde's device authorization flow adheres to `RFC 8628`, also known as the OAuth 2.0 Device Authorization Grant. It enables authorization for devices with limited input capabilities, such as smart TVs, gaming consoles, or IoT devices. Users authenticate on a secondary device (like a phone or computer) while the primary device receives the access token.
 
-## How it works
+## How the device authentication flow works
 
-The Device Authorization Flow follows these steps:
+1. **Device requests authorization**: The device requests a device code and user code from Kinde.
+2. **User authenticates**: The user visits a verification URI on another device and enters the user code.
+3. **Device polls for token**: The device polls the token endpoint until authorization is complete.
+4. **Access granted**: The device receives an access token and can call protected APIs.
 
-1. **Device requests authorization**: The device requests a device code and user code from Kinde
-2. **User authenticates**: The user visits a verification URI on another device and enters the user code
-3. **Device polls for token**: The device polls the token endpoint until authorization is complete
-4. **Access granted**: The device receives an access token and can call protected APIs
+## Endpoints for the device authorization flow
 
-## Endpoints
-
-### Device Authorization Endpoint
+### Device authorization endpoint
 
 **URL**: `https://<your-subdomain>.kinde.com/oauth2/device/auth`
 
@@ -51,7 +49,7 @@ The Device Authorization Flow follows these steps:
 }
 ```
 
-### Token Endpoint
+### Token endpoint
 
 **URL**: `https://<your-subdomain>.kinde.com/oauth2/token`
 
@@ -89,11 +87,11 @@ The Device Authorization Flow follows these steps:
 
 The device must poll the token endpoint at regular intervals until the user completes authentication:
 
-- **Initial interval**: Use the `interval` value from the device authorization response (typically 5 seconds)
-- **Slow down**: If you receive a `slow_down` error, increase the polling interval by 5 seconds
-- **Maximum time**: Stop polling after the `expires_in` time (typically 30 minutes)
+- **Initial interval**: Use the `interval` value from the device authorization response (typically 5 seconds).
+- **Slow down**: If you receive a `slow_down` error, increase the polling interval by 5 seconds.
+- **Maximum time**: Stop polling after the `expires_in` time (typically 30 minutes).
 
-## Error codes
+## Device authorization flow error codes
 
 | Error Code              | Description                          | Action                         |
 | ----------------------- | ------------------------------------ | ------------------------------ |
@@ -103,18 +101,18 @@ The device must poll the token endpoint at regular intervals until the user comp
 | `expired_token`         | Device code has expired              | Request a new device code      |
 | `server_error`          | Misconfigured device code            | Request a new device code      |
 
-## Security considerations
+## Security considerations for device authorization
 
-- **User code format**: User codes are formatted as `XXXXXXXX` for easy entry
-- **Verification URI**: Users should verify they're on the correct domain
-- **Token expiration**: Access tokens expire after 1 hour by default
+- **User code format**: User codes are formatted as `XXXXXXXX` for easy entry.
+- **Verification URI**: Users should verify they're on the correct domain.
+- **Token expiration**: Access tokens expire after 1 hour by default.
 
-## Audience
+## Specifying an audience in a device authorization request 
 
 If an `audience` is specified in the request, the access token will include the audience in the `aud` claim. Kinde supports requesting multiple audiences.
 
-The API must be authorized for the Device Authorization application.
+The API must be authorized for the device authorization application.
 
-## Scopes and permissions
+## Scopes and permissions for a device authorization request 
 
 If an audience is specified in the request, any scopes which are belong to that audience that are granted to the user by their role will also be granted to the device. The list of scopes will be displayed on the consent screen. If the user consents, the scopes will be included in the `scope` claim of the access token.