Claire edits for headings and style

Author: clairekinde11

src/content/docs/authenticate/device-authorization-flow/api-calls.mdx

@@ -10,18 +10,18 @@ relatedArticles:
   - 1cbd91d2-c0b3-45b3-b038-319de1b2c794
 ---
 
-Once you've received an access token from the Device Authorization Flow, you can use it to call your protected APIs. This guide shows you how to validate tokens, handle scopes, and make authenticated API requests.
+Once you've received an access token from the device authorization flow, you can use it to call your protected APIs. This guide shows you how to validate tokens, handle scopes, and make authenticated API requests.
 
-## Using the access token
+## Use the access token from the device authorization flow
 
-The access token you receive from Device Authorization Flow is a standard OAuth 2.0 Bearer token. Include it in the `Authorization` header of your API requests:
+The access token you receive from the device authorization flow is a standard OAuth 2.0 Bearer token. Include it in the `Authorization` header of your API requests:
 
 ```bash
 curl -X GET https://your-api.com/protected-resource \
   -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
 ```
 
-## Token validation
+## Token validation in the device authorization flow
 
 Before processing API requests, validate the access token to ensure it's valid and hasn't expired:
 
@@ -83,7 +83,7 @@ function validateToken(token) {
 }
 ```
 
-## Scope enforcement
+## Scope enforcement for device authorization
 
 Access tokens include scopes that determine what resources the user can access. Check the required scopes before processing requests:
 
@@ -101,7 +101,7 @@ if (!hasRequiredScope(accessToken, "read:users")) {
 }
 ```
 
-## Common API patterns
+## Common API patterns for device authorization
 
 ### Protected resource endpoint
 
@@ -145,7 +145,7 @@ function authenticateToken(req, res, next) {
 }
 ```
 
-### Error handling
+### Error handling for device authorization
 
 Handle common token-related errors:
 
@@ -166,7 +166,7 @@ function handleTokenError(error) {
 }
 ```
 
-## Security best practices
+## Security best practices for device authorization
 
 ### Token storage