Improve docs by removing typos and grammatical errors (github#28391)

Co-authored-by: Laura Coursen <[email protected]>

content/codespaces/managing-codespaces-for-your-organization/choosing-who-owns-and-pays-for-codespaces-in-your-organization.md

@@ -2,7 +2,7 @@
 title: Choosing who owns and pays for codespaces in your organization
 shortTitle: 'Billing and ownership'
 intro: 'You can choose whether codespaces are paid for and owned by your organization or by your members.'
-permissions: 'Organization owners can change an organization''s billing details and control who owns and pays for codespaces.'
+permissions: "Organization owners can change an organization's billing details and control who owns and pays for codespaces."
 versions:
   fpt: '*'
   ghec: '*'
@@ -16,9 +16,9 @@ product: 'Organizations on {% data variables.product.prodname_team %} and {% dat
 
 ## Overview
 
-If you're the owner of an organization on a {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %} plan, you can pay for your members' and collaborators' usage of {% data variables.product.prodname_github_codespaces %}. Paying for usage will allow people to use {% data variables.product.prodname_github_codespaces %} to work in your repositories without having to do so at their own expense, and will give your organization more control over the codespaces created from your repositories.
+If you're the owner of an organization on a {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %} plan, you can pay for your members' and collaborators' usage of {% data variables.product.prodname_github_codespaces %}. Paying for usage will allow people to use {% data variables.product.prodname_github_codespaces %} to work in your repositories without having to do so at their own expense and will give your organization more control over the codespaces created from your repositories.
 
-To pay for usage, you must do all of the following things.
+To pay for usage, you must do all of the following things:
 
 - Allow at least some of your members and collaborators to use {% data variables.product.prodname_github_codespaces %} in your organization's private {% ifversion ghec %}and internal {% endif %}repositories. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/enabling-or-disabling-github-codespaces-for-your-organization#enabling-or-disabling-github-codespaces)."
 - Choose for codespaces created from your organization's repositories to be **organization-owned**. For more information, see "[Choosing who owns and pays for codespaces](#choosing-who-owns-and-pays-for-codespaces)."
@@ -34,7 +34,7 @@ For organizations on a {% data variables.product.prodname_team %} or {% data var
 
 If an organization chooses for codespaces to be **user-owned**, a user who creates a codespace from a repository in the organization always pays for the codespace. The user's access to create codespaces depends on the visibility of the repository and your organization's access settings.
 
-If an organization chooses for codespaces to be **organization-owned**, the organization will pay for a codespace if all the following things are true.
+If an organization chooses for codespaces to be **organization-owned**, the organization will pay for a codespace if all the following things are true:
 
 {% data reusables.codespaces.when-an-org-pays %}
 
@@ -43,7 +43,7 @@ For more information about enabling {% data variables.product.prodname_github_co
 {% ifversion ghec %}
 {% note %}
 
-**Note:** If you own an {% data variables.enterprise.prodname_emu_org %}, and do not allow {% data variables.product.prodname_github_codespaces %} to be billed to your organization, members with {% data variables.enterprise.prodname_managed_users %} will not be able to use {% data variables.product.prodname_github_codespaces %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)."
+**Note:** If you own an {% data variables.enterprise.prodname_emu_org %} and do not allow {% data variables.product.prodname_github_codespaces %} to be billed to your organization, members with {% data variables.enterprise.prodname_managed_users %} will not be able to use {% data variables.product.prodname_github_codespaces %}. For more information, see "[AUTOTITLE](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-user-accounts)."
 
 {% endnote %}
 {% endif %}

content/codespaces/managing-your-codespaces/managing-secrets-for-your-codespaces.md

@@ -19,7 +19,7 @@ topics:
 
 ## About secrets for {% data variables.product.prodname_github_codespaces %}
 
-You can add secrets to your personal account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as secrets.
+You can add secrets to your personal account that you want to use in your codespaces. For example, you may want to store and access the following sensitive information as secrets:
 
 - Access tokens to cloud services
 - Service principals
@@ -34,7 +34,7 @@ You can choose which repositories should have access to each secret. Then, you c
 
 {% data reusables.codespaces.secrets-naming %} For example, a secret created at the repository level must have a unique name in that repository.
 
-  {% data reusables.codespaces.secret-precedence %}
+{% data reusables.codespaces.secret-precedence %}
 
 ### Limits for secrets
 
@@ -47,7 +47,7 @@ Secrets are limited to 48 KB in size.
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.codespaces-tab %}
 1. To the right of "Codespaces secrets", click **New secret**.
-1. Under "Name", type a name for your secret.
+1. Under "Name," type a name for your secret.
 {% data reusables.user-settings.codespaces-secret-value %}
 {% data reusables.user-settings.codespaces-secret-repository-access %}
 1. Click **Add secret**.
@@ -58,10 +58,10 @@ You can update the value of an existing secret, and you can change which reposit
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.codespaces-tab %}
-1. Under "Codespaces secrets", to the right of the secret you want to edit, click **Update**.
-1. Under "Value", click the link "**enter a new value**."
+1. Under "Codespaces secrets," to the right of the secret you want to edit, click **Update**.
+1. Under "Value," click the link "**enter a new value**."
 
-   ![Screenshot of the "Codespaces / Update secret" page. The "enter a new value" link in highlighted with a dark orange outline.](/assets/images/help/codespaces/codespaces-secret-update-value-text.png)
+   ![Screenshot of the "Codespaces / Update secret" page. The "enter a new value" link is highlighted with a dark orange outline.](/assets/images/help/codespaces/codespaces-secret-update-value-text.png)
 
 {% data reusables.user-settings.codespaces-secret-value %}
 {% data reusables.user-settings.codespaces-secret-repository-access %}
@@ -75,7 +75,7 @@ You can update the value of an existing secret, and you can change which reposit
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.codespaces-tab %}
-1. Under "Codespaces secrets", to the right of the secret you want to delete, click **Delete**.
+1. Under "Codespaces secrets," to the right of the secret you want to delete, click **Delete**.
 1. Read the warning, then click **OK**.
 
 ## Using secrets

content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md

@@ -34,7 +34,7 @@ When you create a codespace from a template on the "Your codespaces" page, {% da
 
 ## The prebuild process
 
-To create a prebuild you set up a prebuild configuration. When you save the configuration, a {% data variables.product.prodname_actions %} workflow runs to create each of the required prebuilds; one workflow per prebuild. Workflows also run whenever the prebuilds for your configuration need to be updated. This can happen at scheduled intervals, on pushes to a prebuild-enabled repository, or when you change the dev container configuration. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
+To create a prebuild, you set up a prebuild configuration. When you save the configuration, a {% data variables.product.prodname_actions %} workflow runs to create each of the required prebuilds; one workflow per prebuild. Workflows also run whenever the prebuilds for your configuration need to be updated. This can happen at scheduled intervals, on pushes to a prebuild-enabled repository, or when you change the dev container configuration. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
 
 When a prebuild configuration workflow runs, {% data variables.product.prodname_dotcom %} creates a temporary codespace, performing setup operations up to and including any `onCreateCommand` and `updateContentCommand` commands in the `devcontainer.json` file. No `postCreateCommand` commands are run during the creation of a prebuild. For more information about these commands, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. A snapshot of the generated container is then taken and stored.
 

content/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories.md

@@ -15,7 +15,7 @@ product: '{% data reusables.gated-features.codespaces-repo %}'
 
 By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access its own repository contents. Your project may use additional resources, located elsewhere, to build the development environment.
 
-## Allowing a prebuild read access external resources
+## Allowing a prebuild read access to external resources
 
 You can configure read access to other {% data variables.product.prodname_dotcom %} repositories, with the same repository owner, by specifying permissions in the `devcontainer.json` file used by your prebuild configuration. For more information, see "[AUTOTITLE](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)."
 
@@ -27,9 +27,9 @@ You can configure read access to other {% data variables.product.prodname_dotcom
 
 When you create or edit a prebuild configuration for a `devcontainer.json` file that sets up read access to other repositories with the same repository owner, you'll be prompted to grant these permissions when you click **Create** or **Update**. For more information, see "[AUTOTITLE](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
 
-## Allowing a prebuild write access external resources
+## Allowing a prebuild write access to external resources
 
-If your project requires write access to resources, or if the external resources reside in a repository with a different owner to the repository for which you are creating a prebuild configuration, you can use a {% data variables.product.pat_generic %} to grant this access.
+If your project requires write access to resources, or if the external resources reside in a repository with a different owner than the repository for which you are creating a prebuild configuration, you can use a {% data variables.product.pat_generic %} to grant this access.
 
 You will need to create a new personal account and then use this account to create a {% data variables.product.pat_v1 %} with the appropriate scopes.
 
@@ -56,7 +56,7 @@ You will need to create a new personal account and then use this account to crea
 1. Sign back into the account that has admin access to the repository.
 1. In the repository for which you want to create {% data variables.product.prodname_github_codespaces %} prebuilds, create a new {% data variables.product.prodname_codespaces %} repository secret called `CODESPACES_PREBUILD_TOKEN`, giving it the value of the token you created and copied. For more information, see "[AUTOTITLE](/codespaces/managing-codespaces-for-your-organization/managing-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)."
 
-The {% data variables.product.pat_generic %} will be used for all subsequent prebuilds created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository.
+The {% data variables.product.pat_generic %} will be used for all subsequent prebuilds created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available for use in codespaces created from your repository.
 
 ## Further reading
 

content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md

@@ -27,7 +27,7 @@ The settings in the prebuild configuration determine which events automatically
 
 People with admin access to a repository can check the progress of prebuilds, edit, and delete prebuild configurations.
 
-To locate all repositories that are hosting a prebuild configuration, you must obtain a copy of your usage report by following the steps for “[AUTOTITLE](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)”
+To locate all repositories that are hosting a prebuild configuration, you must obtain a copy of your usage report by following the steps for "[AUTOTITLE](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
 
 ## Viewing the progress of prebuilds
 
@@ -77,7 +77,7 @@ Disabling the workflow runs for a prebuild configuration is useful if you need t
 
 {% note %}
 
-**Note**: You can find a list of the repositories that contains a prebuild by obtaining a copy of your “[usage report](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage).”
+**Note**: You can find a list of the repositories that contain a prebuild by obtaining a copy of your “[usage report](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage).”
 
 {% endnote %}
 
@@ -94,7 +94,7 @@ After you delete a prebuild configuration, workflow runs for that configuration
 
 ## Manually trigger prebuilds
 
-It may be useful to manually trigger a workflow run for a prebuild configuration. Generally this is only necessary if you are debugging a problem with the workflow for a prebuild configuration.
+It may be useful to manually trigger a workflow run for a prebuild configuration. Generally, this is only necessary if you are debugging a problem with the workflow for a prebuild configuration.
 
 1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration whose workflow you want to trigger.
 1. In the dropdown menu, click **Manually trigger**.

content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md

@@ -2,7 +2,7 @@
 title: Testing dev container configuration changes on a prebuild-enabled branch
 shortTitle: Test dev container changes
 allowTitleToDifferFromFilename: true
-intro: When you change the dev container configuration for a branch that's enabled for prebuilds you should test your changes in a codespace.
+intro: When you change the dev container configuration for a branch that's enabled for prebuilds, you should test your changes in a codespace.
 versions:
   fpt: '*'
   ghec: '*'
@@ -23,7 +23,7 @@ For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-c
 1. In the codespace, check out a test branch. For more information, see "[AUTOTITLE](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)."
 1. Make the required changes to the dev container configuration.
 1. Apply the changes by rebuilding the container. For more information, see "[AUTOTITLE](/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)."
-1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild for that branch.
+1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch or an active feature branch, triggering an update of the prebuild for that branch.
 
    {% note %}