github · raulkolaric · Aug 12, 2026 · Aug 12, 2026 · Aug 12, 2026 · Aug 12, 2026
diff --git a/content/billing/get-started/how-billing-works.md b/content/billing/get-started/how-billing-works.md
@@ -72,7 +72,7 @@ You may see an authorization hold on your provided payment method upon initiatin
 
 Authorization holds are temporary and released as quickly as possible. If the authorization hold persists for longer than 10 business days, we suggest reaching out to your bank or card issuer.
 
-If the authorization is unsuccessful, the chosen service will not be activated and the account may be locked. For more more information, see [AUTOTITLE](/billing/how-tos/troubleshooting/locked-account#unlocking-an-accounts-features-due-to-a-failed-authorization-hold).
+If the authorization is unsuccessful, the chosen service will not be activated and the account may be locked. For more information, see [AUTOTITLE](/billing/how-tos/troubleshooting/locked-account#unlocking-an-accounts-features-due-to-a-failed-authorization-hold).
 
 ## How do I see what I'm billed for?
 

diff --git a/...t/code-security/reference/code-scanning/codeql/codeql-cli/codeql-query-packs.md b/...t/code-security/reference/code-scanning/codeql/codeql-cli/codeql-query-packs.md
@@ -14,7 +14,7 @@ category:
 
 ## {% data variables.product.prodname_codeql %} pack compatibility
 
-When a query pack is published, it includes pre-compiled representations of all the queries in it to increase analysis speed. However, if the version of {% data variables.product.prodname_codeql %} that performs the analysis is over 6 months newer than the the version that ran `codeql pack publish`, it may be necessary to compile the queries from source during analysis, slowing the process significantly.
+When a query pack is published, it includes pre-compiled representations of all the queries in it to increase analysis speed. However, if the version of {% data variables.product.prodname_codeql %} that performs the analysis is over 6 months newer than the version that ran `codeql pack publish`, it may be necessary to compile the queries from source during analysis, slowing the process significantly.
 
 A pack published by the _latest_ public release of {% data variables.product.prodname_codeql %} will be useable by the version of {% data variables.product.prodname_codeql %} that is used by {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_actions %}, even though that is often a slightly older release.
 

diff --git a/content/copilot/get-started/quickstart.md b/content/copilot/get-started/quickstart.md
@@ -126,7 +126,7 @@ After you've installed {% data variables.product.prodname_windows_terminal %} Ca
 
 1. Open **Terminal Chat (Experimental)** in the dropdown menu.
 
-1. In the Terminal Chat chat window, type `how do i list all markdown files in my directory` then press <kbd>Enter</kbd>.
+1. In the Terminal Chat window, type `how do i list all markdown files in my directory` then press <kbd>Enter</kbd>.
 
    {% data variables.product.prodname_copilot_short %}'s answer is displayed below your question.
 

diff --git a/content/copilot/how-tos/chat-with-copilot/chat-in-windows-terminal.md b/content/copilot/how-tos/chat-with-copilot/chat-in-windows-terminal.md
@@ -25,7 +25,7 @@ If you have access to {% data variables.product.prodname_copilot %} via your org
 
 ## Getting command explanations and suggestions
 
-In the Terminal Chat chat window, type a question (for example, `how do i list all markdown files in my directory`) then press <kbd>Enter</kbd>.
+In the Terminal Chat window, type a question (for example, `how do i list all markdown files in my directory`) then press <kbd>Enter</kbd>.
 
    {% data variables.product.prodname_copilot_short %}'s answer is displayed below your question.
 

diff --git a/...nt/copilot/tutorials/copilot-cookbook/analyze-functionality/analyze-feedback.md b/...nt/copilot/tutorials/copilot-cookbook/analyze-functionality/analyze-feedback.md
@@ -93,7 +93,7 @@ Write a feature specification for Issue #426.
 # Feature Specification for Issue #426: Shortcut for --with-token CLI option
 
 ## Description:
-Currently, the --with-token option is used to to pass in a token to commands. Typing --with-token each time is cumbersome. This feature proposes a new flag -wt as a shortcut to quickly specify the --with-token option when running various commands.
+Currently, the --with-token option is used to pass in a token to commands. Typing --with-token each time is cumbersome. This feature proposes a new flag -wt as a shortcut to quickly specify the --with-token option when running various commands.
 
 ## Problem:
 Typing --with-token repeatedly is time-consuming and inconvenient for users who frequently use this option.

diff --git a/content/migrations/elm/migrated-data-reference.md b/content/migrations/elm/migrated-data-reference.md
@@ -154,4 +154,4 @@ The following are exported during initial backfill only and are **not** updated
 
 References **within the source repository**, such as user mentions or links to issues and pull requests in the same repository, are rewritten so that they will still point to the correct resources after migration.
 
-References to **different repositories** (such as a link to an issue in the the `repo-2` repository from a pull request in `repo-1`) are **not** migrated and will point to the exact same destination after migration. This applies even if the referenced repository has already been migrated or is being migrated concurrently.
+References to **different repositories** (such as a link to an issue in the `repo-2` repository from a pull request in `repo-1`) are **not** migrated and will point to the exact same destination after migration. This applies even if the referenced repository has already been migrated or is being migrated concurrently.
diff --git a/...tions/using-github-enterprise-importer/migrate-from-gitlab/configure-storage.md b/...tions/using-github-enterprise-importer/migrate-from-gitlab/configure-storage.md
@@ -35,12 +35,12 @@ If you are using external blob storage, you will need to set this up.
 
 {% data reusables.enterprise-migration-tool.aws-credentials-cli %}
 
-### Setting up an Azure Blob Storage storage account
+### Setting up an Azure Blob Storage account
 
 {% data reusables.enterprise-migration-tool.set-up-azure-storage-account %}
 
 {% data reusables.enterprise-migration-tool.azure-credentials-cli %}
 
 ### Allowing network access
 
-If you have configured firewall rules on your storage account, ensure you have allowed access to the IP ranges for your migration destination. See [AUTOTITLE](/migrations/using-github-enterprise-importer/migrate-from-gitlab/manage-access#configure-ip-allow-lists-on-github).
+If you have configured firewall rules on your storage account, ensure you have allowed access to the IP ranges for your migration destination. See [AUTOTITLE](/migrations/using-github-enterprise-importer/migrate-from-gitlab/manage-access#configure-ip-allow-lists-on-github).
diff --git a/...rating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md b/...rating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md
@@ -430,7 +430,7 @@ When you use the CLI flag for {% data variables.product.prodname_ghos %}, the re
 
 {% data reusables.enterprise-migration-tool.set-up-aws-bucket %}
 
-### Setting up an Azure Blob Storage storage account
+### Setting up an Azure Blob Storage account
 
 {% data reusables.enterprise-migration-tool.set-up-azure-storage-account %}
 

diff --git a/...loud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md b/...loud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md
@@ -108,7 +108,7 @@ For security purposes, {% data variables.product.prodname_ghos %} is explicitly
 
 {% data reusables.enterprise-migration-tool.aws-credentials-cli %}
 
-### Setting up an Azure Blob Storage storage account
+### Setting up an Azure Blob Storage account
 
 {% data reusables.enterprise-migration-tool.set-up-azure-storage-account %}
 

diff --git a/data/reusables/enterprise-migration-tool/blob-storage-management-console.md b/data/reusables/enterprise-migration-tool/blob-storage-management-console.md
@@ -1,4 +1,4 @@
-After you set up an AWS S3 storage bucket or Azure Blob Storage storage account, configure blob storage in the {% data variables.enterprise.management_console %} of {% data variables.location.product_location_enterprise %}. For more information about the {% data variables.enterprise.management_console %}, see [Administering your instance from the Management Console]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/administering-your-instance/administering-your-instance-from-the-web-ui).
+After you set up an AWS S3 storage bucket or Azure Blob Storage account, configure blob storage in the {% data variables.enterprise.management_console %} of {% data variables.location.product_location_enterprise %}. For more information about the {% data variables.enterprise.management_console %}, see [Administering your instance from the Management Console]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/administering-your-instance/administering-your-instance-from-the-web-ui).
 
 1. From an administrative account on {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click {% octicon "rocket" aria-label="Site admin" %}.
 1. If you're not already on the "Site admin" page, in the upper-left corner, click **Site admin**.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -154,4 +154,4 @@ The following are exported during initial backfill only and are not updated

		References within the source repository, such as user mentions or links to issues and pull requests in the same repository, are rewritten so that they will still point to the correct resources after migration.

		References to different repositories (such as a link to an issue in the the `repo-2` repository from a pull request in `repo-1`) are not migrated and will point to the exact same destination after migration. This applies even if the referenced repository has already been migrated or is being migrated concurrently.
		References to different repositories (such as a link to an issue in the `repo-2` repository from a pull request in `repo-1`) are not migrated and will point to the exact same destination after migration. This applies even if the referenced repository has already been migrated or is being migrated concurrently.