From ae4942499155b07944ff9c84dd24a8aeef81898b Mon Sep 17 00:00:00 2001 From: raulkolaric <155586454+raulkolaric@users.noreply.github.com> Date: Wed, 12 Aug 2026 15:44:51 -0300 Subject: [PATCH 1/6] docs(billing): remove duplicated word Remove the repeated 'more' from the authorization holds guidance so the sentence reads correctly. Changes: - content/billing/get-started/how-billing-works.md - Correct the duplicated word in the locked-account cross-reference. Validation: - npm run lint-content -- --paths content/billing/get-started/how-billing-works.md - git diff --check --- content/billing/get-started/how-billing-works.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/billing/get-started/how-billing-works.md b/content/billing/get-started/how-billing-works.md index 1e3849b7f8b9..3bd35e9231cf 100644 --- 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? From 9fb18d1ca37d18e4259092e44afa35cf71eb43df Mon Sep 17 00:00:00 2001 From: raulkolaric <155586454+raulkolaric@users.noreply.github.com> Date: Wed, 12 Aug 2026 15:45:31 -0300 Subject: [PATCH 2/6] docs(codeql): remove duplicated article Remove the repeated 'the' from the CodeQL pack compatibility explanation so the version comparison reads correctly. Changes: - content/code-security/reference/code-scanning/codeql/codeql-cli/codeql-query-packs.md - Correct the duplicated article in the pack compatibility section. Validation: - npm run lint-content -- --paths content/code-security/reference/code-scanning/codeql/codeql-cli/codeql-query-packs.md - git diff --check --- .../code-scanning/codeql/codeql-cli/codeql-query-packs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/code-security/reference/code-scanning/codeql/codeql-cli/codeql-query-packs.md b/content/code-security/reference/code-scanning/codeql/codeql-cli/codeql-query-packs.md index b3879fa8c473..7c9e8e7d2f10 100644 --- a/content/code-security/reference/code-scanning/codeql/codeql-cli/codeql-query-packs.md +++ b/content/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. From 2cf2aacf1f3dcf140f7315c506a5c1ec468dfa7e Mon Sep 17 00:00:00 2001 From: raulkolaric <155586454+raulkolaric@users.noreply.github.com> Date: Wed, 12 Aug 2026 15:46:04 -0300 Subject: [PATCH 3/6] docs(copilot): remove duplicated preposition Remove the repeated 'to' from the example feature specification so the sample response reads correctly. Changes: - content/copilot/tutorials/copilot-cookbook/analyze-functionality/analyze-feedback.md - Correct the duplicated preposition in the example response. Validation: - npm run lint-content -- --paths content/copilot/tutorials/copilot-cookbook/analyze-functionality/analyze-feedback.md - git diff --check --- .../copilot-cookbook/analyze-functionality/analyze-feedback.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/copilot/tutorials/copilot-cookbook/analyze-functionality/analyze-feedback.md b/content/copilot/tutorials/copilot-cookbook/analyze-functionality/analyze-feedback.md index df8b0c17102b..55878c6655af 100644 --- a/content/copilot/tutorials/copilot-cookbook/analyze-functionality/analyze-feedback.md +++ b/content/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. From fcd1b974ba00efde4ed768cdf2c7274ae9015d3e Mon Sep 17 00:00:00 2001 From: raulkolaric <155586454+raulkolaric@users.noreply.github.com> Date: Wed, 12 Aug 2026 15:46:35 -0300 Subject: [PATCH 4/6] docs(migrations): remove duplicated article Remove the repeated 'the' from the cross-repository link example so the migration guidance reads correctly. Changes: - content/migrations/elm/migrated-data-reference.md - Correct the duplicated article in the link-rewriting example. Validation: - npm run lint-content -- --paths content/migrations/elm/migrated-data-reference.md - git diff --check --- content/migrations/elm/migrated-data-reference.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/migrations/elm/migrated-data-reference.md b/content/migrations/elm/migrated-data-reference.md index 9b078348dc67..d7229df384de 100644 --- 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. From 82df4968844f8057bc13c0444dc0031dbc80dbfc Mon Sep 17 00:00:00 2001 From: raulkolaric <155586454+raulkolaric@users.noreply.github.com> Date: Wed, 12 Aug 2026 15:47:15 -0300 Subject: [PATCH 5/6] docs(copilot): simplify Terminal Chat wording Remove the repeated use of 'chat' after the Terminal Chat product name on both Windows Terminal guidance pages. Changes: - content/copilot/get-started/quickstart.md - Refer to the Terminal Chat window without repeating 'chat'. - content/copilot/how-tos/chat-with-copilot/chat-in-windows-terminal.md - Use the same corrected Terminal Chat window wording. Validation: - npm run lint-content -- --paths content/copilot/get-started/quickstart.md content/copilot/how-tos/chat-with-copilot/chat-in-windows-terminal.md - git diff --check --- content/copilot/get-started/quickstart.md | 2 +- .../how-tos/chat-with-copilot/chat-in-windows-terminal.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/copilot/get-started/quickstart.md b/content/copilot/get-started/quickstart.md index 8e36954bb820..fc2480555f97 100644 --- 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 Enter. +1. In the Terminal Chat window, type `how do i list all markdown files in my directory` then press Enter. {% 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 index 82283117c4d1..d1c2e32ec159 100644 --- 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 Enter. +In the Terminal Chat window, type a question (for example, `how do i list all markdown files in my directory`) then press Enter. {% data variables.product.prodname_copilot_short %}'s answer is displayed below your question. From 7eefb618f02be8fc86a7c307ddfd203b242e6d2e Mon Sep 17 00:00:00 2001 From: raulkolaric <155586454+raulkolaric@users.noreply.github.com> Date: Wed, 12 Aug 2026 15:48:35 -0300 Subject: [PATCH 6/6] docs(migrations): simplify Azure storage wording Remove the repeated use of 'storage' from Azure Blob Storage account references across migration guidance. Changes: - content/migrations/using-github-enterprise-importer/migrate-from-gitlab/configure-storage.md - Simplify the Azure Blob Storage account heading. - Normalize the file's missing end-of-file newline. - content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md - Simplify the Azure Blob Storage account heading. - content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md - Simplify the Azure Blob Storage account heading. - data/reusables/enterprise-migration-tool/blob-storage-management-console.md - Simplify the shared Azure Blob Storage account reference. Validation: - npm run lint-content -- --paths content/migrations/using-github-enterprise-importer/migrate-from-gitlab/configure-storage.md content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md data/reusables/enterprise-migration-tool/blob-storage-management-console.md - rg -n -F 'setting-up-an-azure-blob-storage-storage-account' content data - rg -n -F 'Azure Blob Storage storage account' content data/reusables - git diff --check --- .../migrate-from-gitlab/configure-storage.md | 4 ++-- ...rom-github-enterprise-server-to-github-enterprise-cloud.md | 2 +- ...tories-from-bitbucket-server-to-github-enterprise-cloud.md | 2 +- .../blob-storage-management-console.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/migrations/using-github-enterprise-importer/migrate-from-gitlab/configure-storage.md b/content/migrations/using-github-enterprise-importer/migrate-from-gitlab/configure-storage.md index 2ee3f8be63b2..d550385b3992 100644 --- a/content/migrations/using-github-enterprise-importer/migrate-from-gitlab/configure-storage.md +++ b/content/migrations/using-github-enterprise-importer/migrate-from-gitlab/configure-storage.md @@ -35,7 +35,7 @@ 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 %} @@ -43,4 +43,4 @@ If you are using external blob storage, you will need to set this up. ### 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). \ No newline at end of file +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/content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md index 49a20210f01b..a90e9e718532 100644 --- a/content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md +++ b/content/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-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/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md index 52a093d9ebc1..9e3f31a20eb8 100644 --- a/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md +++ b/content/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/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 index 04cd6b0704a1..6db69e37df21 100644 --- 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**.