Merge branch 'main' into repo-sync

Author: shati-patel

content/actions/reference/workflow-syntax-for-github-actions.md

@@ -24,7 +24,7 @@ The `actions-sync` tool can only download actions from {% data variables.product
 
 ### Prerequisites
 
-* Before using the the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)."
+* Before using the `actions-sync` tool, you must ensure that all destination organizations already exist on your enterprise instance. The following example demonstrates how to sync actions to an organization named `synced-actions` on an enterprise instance. For more information, see "[Creating a new organization from scratch](/github/setting-up-and-managing-organizations-and-teams/creating-a-new-organization-from-scratch)."
 * You must create a personal access token (PAT) on your enterprise instance that can create and write to repositories in the destination organizations. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
 
 ### Example: Using the `actions-sync` tool

content/admin/github-actions/manually-syncing-actions-from-githubcom.md

@@ -1,6 +1,6 @@
 ---
 title: Setting up the tool cache on self-hosted runners without internet access
-intro: 'To use the the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.'
+intro: 'To use the included `actions/setup` actions on self-hosted runners without internet access, you must first populate the runner''s tool cache for your workflows.'
 redirect_from:
   - /enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access
 versions:

content/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md

@@ -21,4 +21,4 @@ versions:
 5. Click **Remove restrictions**.
   ![Remove restrictions button](/assets/images/help/settings/settings-third-party-remove-restrictions.png)
 6. After you review the information about disabling third-party application restrictions, click **Yes, remove application restrictions**.
-  ![Remove confirmation button button](/assets/images/help/settings/settings-third-party-confirm-disable.png)
+  ![Remove confirmation button](/assets/images/help/settings/settings-third-party-confirm-disable.png)

content/github/setting-up-and-managing-organizations-and-teams/disabling-oauth-app-access-restrictions-for-your-organization.md

@@ -194,7 +194,7 @@ Customer’s Affiliates are authorized to use the Products in accordance with th
 
 #### 1. Pricing; Fees
 
-**Payment Terms** Our pricing is available at [github.com/pricing](https://github.com/pricing) (unless otherwise negotiated by the parties and stated in an Order Form). Customer agrees to pay the Fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. Customer must pay the Fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If Customer fails to pay any Fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable Order Form or SOW. Customer is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement.
+**Payment Terms** Our pricing is available at [github.com/pricing](https://github.com/pricing) (unless otherwise negotiated by the parties and stated in an Order Form). Customer agrees to pay the Fees in full, up front without deduction or setoff of any kind, in U.S. Dollars. Customer must pay the Fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable, except as otherwise provided in this Agreement. If Customer fails to pay any Fees on time, GitHub reserves the right, in addition to taking any other action at law or equity, to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law, whichever is less, and to charge all expenses of recovery, and (ii) terminate the applicable Order Form or SOW. Customer is solely responsible for all taxes, fees, duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement.
 
 **Usage-Based Billing** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to purchase paid Service features beyond the quantity included in your plan, you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears, provided that for invoiced customers, paid Service features are billed in advance. See [GitHub Additional Product Terms for details](/github/site-policy/github-additional-product-terms).
 

content/github/site-policy/github-corporate-terms-of-service.md

@@ -85,7 +85,7 @@ This Agreement is a legal agreement between you (“you”) and GitHub, Inc. (
 
 13. **Proprietary Rights**
 
-  You agree that GitHub and its licensors own all right, title and interest in and to the API, the Pre-release Materials, and all other GitHub products and services; all information and data relating to their configurations and combinations; and all modifications to and derivative works of any of the foregoing. You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other other GitHub products and services.
+  You agree that GitHub and its licensors own all right, title and interest in and to the API, the Pre-release Materials, and all other GitHub products and services; all information and data relating to their configurations and combinations; and all modifications to and derivative works of any of the foregoing. You agree not to remove, alter, cover or obfuscate any copyright or other proprietary rights notices we place on or embed in the API, the Pre-release Materials, or any other GitHub products and services.
 
 14. **Government Users**
 

content/github/site-policy/github-registered-developer-agreement.md

@@ -48,7 +48,7 @@ Before you can sponsor a developer, you must have a verified email address. For
 Before you can sponsor an organization, you must have a verified email address. For more information, see "[Verifying your email address](/github/getting-started-with-github/verifying-your-email-address)."
 
 1. On {% data variables.product.product_name %}, navigate to the page of the organization you want to sponsor.
-2. Next to the the organization's name, click **Sponsor**.
+2. Next to the organization's name, click **Sponsor**.
   ![Sponsor button](/assets/images/help/sponsors/sponsor-org-button.png)
 {% data reusables.sponsors.select-a-tier %}
 {% data reusables.sponsors.select-sponsorship-billing %}

content/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-an-open-source-contributor.md

@@ -27,13 +27,13 @@ You access all of this information from your Sponsors dashboard.
 
 ### Viewing recent sponsorship activity
 
-1. Go to your your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard).
+1. Go to your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard).
 1. In the left sidebar, click **Activity**.
   ![Activity tab](/assets/images/help/sponsors/activity-tab.png)
 
 ### Exporting your sponsorship data
 
-1. Go to your your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard).
+1. Go to your Sponsors dashboard, see [Viewing your Sponsors dashboard](#viewing-your-sponsors-dashboard).
 {% data reusables.sponsors.navigate-to-sponsors-tab %}
 1. Click **Export all**.
   ![Export all button](/assets/images/help/sponsors/export-all.png)

content/github/supporting-the-open-source-community-with-github-sponsors/viewing-your-sponsors-and-sponsorships.md

@@ -218,7 +218,7 @@ When introducing a list, avoid phrasing like “the following” or “these”,
 
 ## Procedural steps
 
-Procedures give readers a set of sequential steps to follow to complete a task. Always use numbered lists for procedures. Give readers all of the prerequisites or conceptual conceptual information they’ll need to complete the task before the procedure, rather than including it within a specific step.
+Procedures give readers a set of sequential steps to follow to complete a task. Always use numbered lists for procedures. Give readers all of the prerequisites or conceptual information they’ll need to complete the task before the procedure, rather than including it within a specific step.
 
 Each step must include an action. You can also choose to include whether a step is optional, explain the reason or result of the step, and orient the reader by describing the location of the action, before guiding them to complete the action.