fix-spelling-canceled (#22692)

Co-authored-by: hubwriter <[email protected]>

Author: technoph1le

content/codespaces/troubleshooting/troubleshooting-creation-and-deletion-of-codespaces.md

@@ -31,7 +31,7 @@ If you still cannot create a codespace for a repository where {% data variables.
 
 ### Codespace creation fails
 
-If the creation of a codespace fails, it's likely to be due to a temporary infrastructure issue in the cloud - for example, a problem provisioning a virtual machine for the codespace. A less common reason for failure is if it takes longer than an hour to build the container. In this case, the build is cancelled and codespace creation will fail.
+If the creation of a codespace fails, it's likely to be due to a temporary infrastructure issue in the cloud - for example, a problem provisioning a virtual machine for the codespace. A less common reason for failure is if it takes longer than an hour to build the container. In this case, the build is canceled and codespace creation will fail.
 
 {% note %}
 

content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md

@@ -28,7 +28,7 @@ At the time that you block a user from your organization:
 - The user's votes on discussions or comments in your organization's repositories are deleted
 - The user is removed as a collaborator on your organization's repositories
 - The user's contributions to your organization's repositories are no longer counted as contributions for them
-- Any pending repository or organization invitations to the blocked user are cancelled
+- Any pending repository or organization invitations to the blocked user are canceled
 
 After you've blocked a user from your organization, they cannot:
 - Cross-reference your organization's repositories in comments

content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account.md

@@ -32,8 +32,8 @@ When you block a user:
 - The user's contributions to your repositories are no longer counted as contributions for them
 - Your contributions to the blocked user's repositories are no longer counted as contributions for you
 - You are removed as a collaborator on their repositories
-- Their sponsorship of you is cancelled
-- Any pending repository or account successor invitations to or from the blocked user are cancelled
+- Their sponsorship of you is canceled
+- Any pending repository or account successor invitations to or from the blocked user are canceled
 - The user is removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by you
 - You are removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by the user
 

content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-transactions-for-your-listing.md

@@ -28,7 +28,7 @@ You can view or download the transaction data to keep track of your subscription
 * **user_id:** The id of the user with the subscription.
 * **user_type:** The type of GitHub account, either `User` or `Organization`.
 * **country:** The three letter country code.
-* **amount_in_cents:** The amount of the transaction in cents. When a value is less the plan amount, the user upgraded and the new plan is prorated. A value of zero indicates the user cancelled their plan.
+* **amount_in_cents:** The amount of the transaction in cents. When a value is less the plan amount, the user upgraded and the new plan is prorated. A value of zero indicates the user canceled their plan.
 * **renewal_frequency:** The subscription renewal frequency, either `Monthly` or `Yearly`.
 * **marketplace_listing_plan_id:** The `id` of the subscription plan.
 * **region:** The name of the region present in billing address.

content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md

@@ -54,6 +54,6 @@ For more information, see: "[Handling new purchases and free trials](/developers
 
 {% note %}
 
-**Note:** GitHub expects you to delete any private customer data within 30 days of a cancelled trial, beginning at the receipt of the cancellation event.
+**Note:** GitHub expects you to delete any private customer data within 30 days of a canceled trial, beginning at the receipt of the cancellation event.
 
 {% endnote %}

content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md

@@ -23,7 +23,7 @@ If a customer chooses to cancel a {% data variables.product.prodname_marketplace
 
 When a customer cancels a free or paid plan, your app must perform these steps to complete cancellation:
 
-1. Deactivate the account of the customer who cancelled their plan.
+1. Deactivate the account of the customer who canceled their plan.
 1. Revoke the OAuth token your app received for the customer.
 1. If your app is an OAuth App, remove all webhooks your app created for repositories.
 1. Remove all customer data within 30 days of receiving the `cancelled` event.

content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md

@@ -1,17 +1,18 @@
 ---
 title: Testing your app
-intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows.'
+intro: "GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows."
 redirect_from:
   - /apps/marketplace/testing-apps-apis-and-webhooks
   - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
   - /marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps
   - /developers/github-marketplace/testing-your-app
 versions:
-  fpt: '*'
-  ghec: '*'
+  fpt: "*"
+  ghec: "*"
 topics:
   - Marketplace
 ---
+
 ## Testing apps
 
 You can use a draft {% data variables.product.prodname_marketplace %} listing to simulate each of the billing flows. A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. Note that you can only simulate purchases for plans published in the draft listing and not for draft plans. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)."

content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md

@@ -27,7 +27,7 @@ permissions: Organization owners can remove members from an organization.
 {%- ifversion ghec %}
 -  Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization owned by the same enterprise account. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
 {%- endif %}
-- Any organization invitations sent by a removed member, that have not been accepted, are cancelled and will not be accessible.
+- Any organization invitations sent by a removed member, that have not been accepted, are canceled and will not be accessible.
 
 {% endwarning %}
 
@@ -38,7 +38,7 @@ permissions: Organization owners can remove members from an organization.
 **Warning:** When you remove members from an organization:
  - Removed members will lose access to private forks of your organization's private repositories, but may still have local copies. However, they cannot sync local copies with your organization's repositories. Their private forks can be restored if the user is [reinstated as an organization member](/articles/reinstating-a-former-member-of-your-organization) within three months of being removed from the organization. Ultimately, you are responsible for ensuring that people who have lost access to a repository delete any confidential information or intellectual property.
 - Removed members will also lose access to private forks of your organization's internal repositories, if the removed member is not a member of any other organization in your enterprise.
- - Any organization invitations sent by the removed user, that have not been accepted, are cancelled and will not be accessible.
+ - Any organization invitations sent by the removed user, that have not been accepted, are canceled and will not be accessible.
 
 {% endwarning %}
 

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

@@ -69,7 +69,7 @@ This Agreement applies to the following GitHub offerings, as further defined bel
 
 **"Professional Services"** means training, consulting, or implementation services that GitHub provides to Customer pursuant to a mutually executed SOW. Professional Services do not include Support.
 
-**"Professional Services Credits"** means the upfront payment method for purchasing Professional Services (exclusive of travel and lodging expenses) that Customer may use over a period of twelve (12) months (unless otherwise stated in an Order Form) for Professional Services. Any Professional Services Credits that remain unused at the end of twelve (12) months from the date of purchase (or as otherwise stated in an Order Form) are automatically cancelled and are non-refundable.
+**"Professional Services Credits"** means the upfront payment method for purchasing Professional Services (exclusive of travel and lodging expenses) that Customer may use over a period of twelve (12) months (unless otherwise stated in an Order Form) for Professional Services. Any Professional Services Credits that remain unused at the end of twelve (12) months from the date of purchase (or as otherwise stated in an Order Form) are automatically canceled and are non-refundable.
 
 **“Public Repository”** means a repository whose Content is visible to All Users.
 
@@ -205,7 +205,7 @@ Customer’s Affiliates are authorized to use the Products in accordance with th
 Customer may obtain additional Subscription Licenses under this Agreement by submitting a request through the Service or via its sales team. If Customer purchases the additional Subscription Licenses, Customer must pay the then-currently applicable Fees for them, prorated for the balance of the applicable Subscription Term. Upon renewal of Customer’s Subscription Licenses for another Subscription Term, GitHub will invoice all Subscription Licenses at once on an annual basis unless otherwise specified in an Order Form.
 
 ### 3. Professional Services Credits.
-If Customer uses Professional Services Credits to pay for Professional Services, then upon Customer’s receipt of an SOW, the applicable Professional Services Credits will be deducted from Customer’s Professional Services Credits balance. Customer is responsible for ensuring that its purchase order issued to GitHub for the Professional Services reflects the pricing set forth in the SOW. If there is any difference in pricing listed in the SOW and the pricing listed in Customer’s purchase order, the pricing in the SOW will control. The Parties agree that SOWs payable via Professional Services Credits do not have to be signed by either Party to be valid and enforceable. All Professional Services Credits must be used within the time set forth in the Order Form or will automatically be cancelled and are non-refundable. Customer may not apply Professional Services Credits to travel and lodging expenses, which must be invoiced separately.
+If Customer uses Professional Services Credits to pay for Professional Services, then upon Customer’s receipt of an SOW, the applicable Professional Services Credits will be deducted from Customer’s Professional Services Credits balance. Customer is responsible for ensuring that its purchase order issued to GitHub for the Professional Services reflects the pricing set forth in the SOW. If there is any difference in pricing listed in the SOW and the pricing listed in Customer’s purchase order, the pricing in the SOW will control. The Parties agree that SOWs payable via Professional Services Credits do not have to be signed by either Party to be valid and enforceable. All Professional Services Credits must be used within the time set forth in the Order Form or will automatically be canceled and are non-refundable. Customer may not apply Professional Services Credits to travel and lodging expenses, which must be invoiced separately.
 
 ### 4. Authorization
 Customer authorizes GitHub to charge the on-file credit card, PayPal account, or other approved methods of payment for Fees.
@@ -224,7 +224,7 @@ Either Party may terminate this Agreement immediately upon notice if the other P
 ### 4. Effect of Termination
 - _Order Forms._ Upon termination of this Agreement, Customer may not execute additional Order Forms (if applicable); however, this Agreement will remain in effect for the remainder of any active Order Forms. When an Order Form terminates or expires, as to that Order Form: (i) the Term will immediately end; (ii) any Subscription Licenses in the Order Form will automatically terminate, and Customer will no longer have the right to use the Service; (iii) if any Fees were owed prior to termination, Customer must pay those Fees immediately; (iv) each Party will promptly return (or, if the other party requests it, destroy) all Confidential Information belonging to the other to the extent permitted by the Service. Notwithstanding the foregoing, GitHub will make a reasonable effort to provide Customer with a copy of its lawful, non-infringing account Contents upon request; provided that Customer makes this request within 90 days of termination, suspension, or downgrade.
 
-- GitHub will retain and use Customer's information as necessary to comply with our legal obligations, resolve disputes, and enforce GitHub's agreements, but barring legal requirements, GitHub will delete Customer's full profile and the Content of its repositories within 90 days of termination or expiration (though some information may remain in encrypted backups). This information cannot be recovered once Customer's account is cancelled.
+- GitHub will retain and use Customer's information as necessary to comply with our legal obligations, resolve disputes, and enforce GitHub's agreements, but barring legal requirements, GitHub will delete Customer's full profile and the Content of its repositories within 90 days of termination or expiration (though some information may remain in encrypted backups). This information cannot be recovered once Customer's account is canceled.
 
 - GitHub will not delete Content that Customer has contributed to External Users' repositories or that External Users have forked.
 

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

@@ -234,7 +234,7 @@ You are responsible for all fees, including taxes, associated with your use of t
 It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/articles/how-do-i-cancel-my-account/) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple, no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request.
 
 ### 2. Upon Cancellation
-We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information can not be recovered once your Account is cancelled.
+We will retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information can not be recovered once your Account is canceled.
 
 We will not delete Content that you have contributed to other Users' repositories or that other Users have forked.