Fix typo and indefinite article before HTTP/HTTPS

content/actions/reference/github-actions-importer/supplemental-arguments-and-settings.md

@@ -177,7 +177,7 @@ gh actions-importer audit --output-dir /data/out
 
 ## Using a proxy
 
-To access servers that are configured with a HTTP proxy, you must set the following environment variables with the proxy's URL:
+To access servers that are configured with an HTTP proxy, you must set the following environment variables with the proxy's URL:
 
 * `OCTOKIT_PROXY`: for any {% data variables.product.prodname_dotcom %} server.
 * `HTTP_PROXY` (or `HTTPS_PROXY`): for any other servers.

content/apps/oauth-apps/building-oauth-apps/best-practices-for-creating-an-oauth-app.md

@@ -80,7 +80,7 @@ If your app is a native client, client-side app, or runs on a user device (as op
 
 To enforce regular token rotation and reduce the impact of a compromised token, you should configure your {% data variables.product.prodname_oauth_app %} to use access tokens that expire. When your app uses access tokens that expire, you will receive a refresh token when you generate a access token. The access token expires after eight hours, and the refresh token expires after six months. You can use the refresh token to generate a new access token and a new refresh token. For more information, see [AUTOTITLE](/apps/oauth-apps/building-oauth-apps/authorizing-oauth-apps#expiring-access-tokens).
 
-To test and gradually roll out support for expiring tokens, you can opt in to receive expiring tokens for a sign-in by requesting the `offline_access` scope in addition to your other scopes. If your app supports both {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}, be prepared for the `offline_access` scope to have no effect, because the {% data variables.product.prodname_ghe_server %} instance may not yet support expiring tokens. Check for the presence of the `expires_in` field in the token response to understand if your app has recieved an expiring token.
+To test and gradually roll out support for expiring tokens, you can opt in to receive expiring tokens for a sign-in by requesting the `offline_access` scope in addition to your other scopes. If your app supports both {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}, be prepared for the `offline_access` scope to have no effect, because the {% data variables.product.prodname_ghe_server %} instance may not yet support expiring tokens. Check for the presence of the `expires_in` field in the token response to understand if your app has received an expiring token.
 
 {% endif %}
 

content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md

@@ -830,4 +830,4 @@ gh api graphql -f query='
 
 ## Using webhooks
 
-You can use webhooks to subscribe to events taking place in your project. For example, when an item is edited, {% data variables.product.github %} can send a HTTP POST payload to the webhook's configured URL which can trigger automation on your server. For more information about webhooks, see [AUTOTITLE](/webhooks/about-webhooks). To learn more about the `projects_v2_item` webhook event, see [AUTOTITLE](/webhooks/webhook-events-and-payloads#projects_v2_item).
+You can use webhooks to subscribe to events taking place in your project. For example, when an item is edited, {% data variables.product.github %} can send an HTTP POST payload to the webhook's configured URL which can trigger automation on your server. For more information about webhooks, see [AUTOTITLE](/webhooks/about-webhooks). To learn more about the `projects_v2_item` webhook event, see [AUTOTITLE](/webhooks/webhook-events-and-payloads#projects_v2_item).

content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md

@@ -66,9 +66,9 @@ Assets are commonly found in the following locations:
 
 ## Verifying the DNS configuration
 
-In some cases, a HTTPS certificate will not be able to be generated due to the DNS configuration of your custom domain. This can be caused by extra DNS records, or records not pointing to the IP addresses for {% data variables.product.prodname_pages %}.
+In some cases, an HTTPS certificate will not be able to be generated due to the DNS configuration of your custom domain. This can be caused by extra DNS records, or records not pointing to the IP addresses for {% data variables.product.prodname_pages %}.
 
-To ensure a HTTPS certificate generates correctly, we recommend the following configurations. Any additional `A`, `AAAA`, `ALIAS`, `ANAME` records with the `@` host, or `CNAME` records pointing to your `www` subdomain or other custom subdomain that you would like to use with {% data variables.product.prodname_pages %} may prevent the HTTPS certificate from generating.
+To ensure an HTTPS certificate generates correctly, we recommend the following configurations. Any additional `A`, `AAAA`, `ALIAS`, `ANAME` records with the `@` host, or `CNAME` records pointing to your `www` subdomain or other custom subdomain that you would like to use with {% data variables.product.prodname_pages %} may prevent the HTTPS certificate from generating.
 
 | Scenario | DNS record type | DNS record name | DNS record value(s) |
 |---|---|---|---|