Removes duplicate headers for accessibility audit (github#34474)

Author: subatoi

content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md

@@ -44,7 +44,7 @@ Direct the user to the following URL in their browser:
 
 When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
 
-#### Parameters
+#### Input parameters for `GET {% data variables.product.oauth_host_code %}/login/oauth/authorize`
 
 Name | Type | Description
 -----|------|------------
@@ -78,7 +78,7 @@ Make a request to the following endpoint to receive an access token:
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-#### Parameters
+#### Input parameters for `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`
 
 Name | Type | Description
 -----|------|------------
@@ -87,7 +87,7 @@ Name | Type | Description
 `code` | `string`   | **Required.** The code you received as a response to Step 1.
 `redirect_uri` | `string` | The URL in your application where users will be sent after authorization. This must be an exact match to {% ifversion fpt or ghes or ghec %} one of the URLs you provided as a **Callback URL** {% else %} the URL you provided in the **User authorization callback URL** field{% endif %} when setting up your GitHub App and can't contain any additional parameters.
 
-#### Response
+#### Response from `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`
 
 By default, the response takes the following form. The response parameters `expires_in`, `refresh_token`,  and `refresh_token_expires_in` are only returned when you enable expiring user-to-server access tokens.
 

content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md

@@ -46,7 +46,7 @@ The web application flow to authorize users for your app is:
 
 When your GitHub App specifies a `login` parameter, it prompts users with a specific account they can use for signing in and authorizing your app.
 
-#### Parameters
+#### Input parameters for `GET {% data variables.product.oauth_host_code %}/login/oauth/authorize`
 
 Name | Type | Description
 -----|------|--------------
@@ -65,7 +65,7 @@ Exchange this `code` for an access token:
 
     POST {% data variables.product.oauth_host_code %}/login/oauth/access_token
 
-#### Parameters
+#### Input parameters for `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`
 
 Name | Type | Description
 -----|------|--------------
@@ -74,7 +74,7 @@ Name | Type | Description
 `code` | `string` | **Required.** The code you received as a response to Step 1.
 `redirect_uri` | `string` | The URL in your application where users are sent after authorization.
 
-#### Response
+#### Response from `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`
 
 By default, the response takes the following form:
 
@@ -143,14 +143,14 @@ Before you can use the device flow to authorize and identify users, you must fir
 
 Your app must request a user verification code and verification URL that the app will use to prompt the user to authenticate in the next step. This request also returns a device verification code that the app must use to receive an access token and check the status of user authentication.
 
-#### Input Parameters
+#### Input parameters for `POST {% data variables.product.oauth_host_code %}/login/device/code`
 
 Name | Type | Description
 -----|------|--------------
 `client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your app.
 `scope` | `string` | The scope that your app is requesting access to.
 
-#### Response
+#### Response from `POST {% data variables.product.oauth_host_code %}/login/device/code`
 
 By default, the response takes the following form:
 
@@ -182,7 +182,7 @@ Accept: application/xml
 </OAuth>
 ```
 
-#### Response parameters
+#### Response parameters for `POST {% data variables.product.oauth_host_code %}/login/device/code`
 
 Name | Type | Description
 -----|------|--------------
@@ -208,15 +208,15 @@ The user must enter a valid code within 15 minutes (or 900 seconds). After 15 mi
 
 Once the user has authorized, the app will receive an access token that can be used to make requests to the API on behalf of a user.
 
-#### Input parameters
+#### Input parameters for `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`
 
 Name | Type | Description
 -----|------|--------------
 `client_id` | `string` | **Required.** The client ID you received from {% data variables.product.product_name %} for your {% data variables.product.prodname_oauth_app %}.
 `device_code` | `string` | **Required.** The device verification code you received from the `POST {% data variables.product.oauth_host_code %}/login/device/code` request.
 `grant_type` | `string` | **Required.** The grant type must be `urn:ietf:params:oauth:grant-type:device_code`.
 
-#### Response
+#### Response from `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`
 
 By default, the response takes the following form:
 

content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md

@@ -26,17 +26,17 @@ Here are guidelines about the fields you'll need to fill out in the **Listing de
 
 Your listing's name will appear on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace). The name is limited to 255 characters and can be different from your app's name. Your listing cannot have the same name as an existing account on {% data variables.location.product_location %}, unless the name is your own user or organization name.
 
-### Very short description
+### Very short description of listing
 
 The community will see the "very short" description under your app's name on the [{% data variables.product.prodname_marketplace %} homepage](https://github.com/marketplace).
 
 ![{% data variables.product.prodname_marketplace %} app short description](/assets/images/marketplace/marketplace_short_description.png)
 
-#### Length
+#### Length of "Very short description"
 
 We recommend keeping short descriptions to 40-80 characters. Although you are allowed to use more characters, concise descriptions are easier for customers to read and understand quickly.
 
-#### Content
+#### Content of "Very short description"
 
 - Describe the app’s functionality. Don't use this space for a call to action. For example:
 
@@ -52,7 +52,7 @@ We recommend keeping short descriptions to 40-80 characters. Although you are al
 
   **DON'T:** Skycap is a container-native continuous integration tool
 
-#### Formatting
+#### Formatting of "Very short description"
 
 - Always use sentence-case capitalization. Only capitalize the first letter and proper nouns.
 
@@ -142,19 +142,19 @@ Clicking **Read more...**, displays the "Detailed description."
 
 Follow these guidelines for writing these descriptions.
 
-### Length
+### Length of "Introductory description" and "Detailed description"
 
 We recommend writing a 1-2 sentence high-level summary between 150-250 characters in the required "Introductory description" field when [listing your app](/marketplace/listing-on-github-marketplace/). Although you are allowed to use more characters, concise summaries are easier for customers to read and understand quickly.
 
 You can add more information in the optional "Detailed description" field. You see this description when you click **Read more...** below the introductory description on your app's landing page. A detailed description consists of 3-5 [value propositions](https://en.wikipedia.org/wiki/Value_proposition), with 1-2 sentences describing each one. You can use up to 1,000 characters for this description.
 
-### Content
+### Content of "Introductory description" and "Detailed description"
 
 - Always begin introductory descriptions with your app's name.
 
 - Always write descriptions and value propositions using the active voice.
 
-### Formatting
+### Formatting of "Introductory description" and "Detailed description"
 
 - Always use sentence-case capitalization in value proposition titles. Only capitalize the first letter and proper nouns.