Merge pull request #2706 from buildkite/quick-docs-fixes

Minor wording tweaks to REST API authentication section.

Author: gilesgas

pages/apis/rest_api.md

@@ -48,16 +48,16 @@ The data encoding is assumed to be `application/json`. Unless explicitly stated
 
 You can authenticate with the Buildkite API using access tokens, represented by the value `$TOKEN` throughout this documentation.
 
-API access tokens allow to call the API without using your username and password. They can be created on your <a href="<%= url_helpers.user_access_tokens_url %>" rel="nofollow">API access tokens</a> page, limited to individual organizations and permissions, and revoked at any time from the web interface [or the REST API](/docs/apis/rest-api/access-token#revoke-the-current-token).
+API access tokens authenticate calls to the API and can be created from the <a href="<%= url_helpers.user_access_tokens_url %>" rel="nofollow">API access tokens</a> page. When configuring API access tokens, you can limit their access to individual organizations and permissions, and these tokens can be revoked at any time from the web interface [or the REST API](/docs/apis/rest-api/access-token#revoke-the-current-token).
 
-To authenticate using a token, set the <code>Authorization</code> HTTP header to the word <code>Bearer</code>, followed by a space, followed by the access token. For example:
+To authenticate an API call using an access token, set the <code>Authorization</code> HTTP header to the word <code>Bearer</code>, followed by a space, followed by the access token. For example:
 
 ```bash
 curl -H "Authorization: Bearer $TOKEN" \
   -X GET "https://api.buildkite.com/v2/user"
 ```
 
-Access using basic HTTP authentication is not supported.
+API access using basic HTTP authentication is not supported.
 
 ## Pagination
 

styleguides/writing-style.md

@@ -196,14 +196,14 @@ Refer to [UI elements in the Markdown syntax style guide](markdown-syntax-style.
 
 ### Lists (bullet lists and numbered steps)
 
-Capitalize the first word—no full stops at the end if it's not a full sentence. If it's a full sentence, give it a full stop/period.
-
 In general:
 
 - Use bullet lists when presenting an unordered list of individual items.
 - Use numbered steps when presenting a sequence of instructions/steps that need to be followed.
 
-See also what [Google](https://developers.google.com/style/lists#capitalization-and-end-punctuation) and [Microsoft](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists#punctuation) say about lists.
+See also what [Google](https://developers.google.com/style/lists) and [Microsoft](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists) say about lists.
+
+Capitalize the first word—no full stops at the end if it's not a full sentence. If it's a full sentence, give it a full stop/period. See also what [Google](https://developers.google.com/style/lists#capitalization-and-end-punctuation) and [Microsoft](https://learn.microsoft.com/en-us/style-guide/scannable-content/lists#punctuation) say about punctuation in list items.
 
 Refer to [Lists in the Markdown syntax style guide](markdown-syntax-style.md#lists) for details on how to write and present lists in the Buildkite docs.