edits [netlify-build]

Author: stayseesong

src/connections/oauth.md

@@ -71,8 +71,8 @@ To disable your source from OAuth, turn the toggle off for **Enable OAuth**.
 You can obtain an access token once you create an OAuth application and enable a source to OAuth.  
 
 Access tokens are only valid within a region. The supported regional authorization servers are: 
-* Oregon - https://oauth2.segment.io 
-* Dublin - https://oauth2.eu1.segmentapis.com
+* Oregon - `https://oauth2.segment.io`
+* Dublin - `https://oauth2.eu1.segmentapis.com`
 
 To obtain the access token:
 
@@ -108,7 +108,7 @@ To obtain the access token:
     EXP | The expiry time in seconds. This is expected to be valid only for a short duration under a minute. 
     JTI | The unique identifer for the token. 
 
-2. Send a form-url-encoded POST request to the regional authorization server with the following parameters:
+2. Send a form-url-encoded `POST` request to the regional authorization server with the following parameters:
     
     ```
     grant_type=client_credentials
@@ -122,27 +122,7 @@ To obtain the access token:
     JWT | The signed JWT token string from Step 1.
     SCOPE | Scopes for which token is requested. See [supported scopes](#supported-scopes).
 
-3. Include the access token in the Authorization header as a Bearer token. For example:
-
-    ```
-    Authorization: Bearer <access token>
-    ```
-
-   Below is an example cURL request: 
-
-   ```
-   curl --location 'https://api.segment.io/v1/track' \
-    --header 'Content-Type: application/json' \
-    --header 'Authorization: Bearer <access token>' \
-    --data-raw '{
-        "event": "happy-path-a3ef8a6f-0482-4694-bc4d-4afba03a0eab",
-        "email": "[email protected]",
-        "messageId": "58524f3a-3b76-4eac-aa97-d88bccdf4f77",
-        "userId": "123",
-        "writeKey": "DmBXIN4JnwqBnTqXccTF0wBnLXNQmFtk"
-    }
-    ```
-
+To use the access token, see an example of how to use the access token in the [HTTP API source](). 
 
 ## Edit an OAuth application
 To edit an existing OAuth application: 

src/connections/sources/catalog/libraries/server/http-api/index.md

@@ -11,6 +11,10 @@ Segment has native [sources](/docs/connections/sources/) for most use cases (lik
 
 ### Authentication
 
+Choose between [basic authentication](#basic-authentication) and [OAuth](#oauth) to authenticate headers. 
+
+#### Basic authentication
+
 Authenticate to the Tracking API by sending your project's **Write Key** along with a request.
 Authentication uses HTTP Basic Auth, which involves a `username:password` that is base64 encoded and prepended with the string `Basic`.
 
@@ -19,6 +23,33 @@ In practice that means taking a Segment source **Write Key**,`'abc123'`, as the
 > info ""
 > Include a colon before encoding. While encoding the write key without a colon might work due to backward compatibility, this won't always be the case.  
 
+#### OAuth
+[Obtain the access token](/docs/connections/oauth/) from the Authorization Server specific to the region. 
+
+Include the access token in the Authorization header as a Bearer token to the resource server. For example:
+
+  ```
+  Authorization: Bearer <access token>
+  ```
+
+
+For example, to use the access token in the HTTP API Source, use `access_token` in the header and `write_key` in the payload. An example cURL request looks like: 
+
+```
+  curl --location 'https://api.segment.io/v1/track' \
+  --header 'Content-Type: application/json' \
+  --header 'Authorization: Bearer <access token>' \
+  --data-raw '{
+      "event": "happy-path-a3ef8a6f-0482-4694-bc4d-4afba03a0eab",
+      "email": "[email protected]",
+      "messageId": "58524f3a-3b76-4eac-aa97-d88bccdf4f77",
+      "userId": "123",
+      "writeKey": "DmBXIN4JnwqBnTqXccTF0wBnLXNQmFtk"
+  }
+```
+
+You can reuse the access token until the expiry period specified on the OAuth application. 
+
 ### Content-Type
 
 To send data to Segment's HTTP API, a content-type header must be set to `'application/json'`.