github · skedwards88 · Jan 2, 2024 · Dec 21, 2023 · Dec 21, 2023 · Dec 21, 2023
diff --git a/...osted-runners-with-actions-runner-controller/about-actions-runner-controller.md b/...osted-runners-with-actions-runner-controller/about-actions-runner-controller.md
@@ -108,7 +108,7 @@ You can find the definition of ARC's runner image in [this Dockerfile](https://g
 You can create your own runner image that meets your requirements. Your runner image must fulfill the following conditions.
 
 - Use a base image that can run the self-hosted runner application. For more information, see "[AUTOTITLE](/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners)."
-- The [runner binary](https://github.com/actions/runner/releases) must be placed placed under `/home/runner/` and launched using `/home/runner/run.sh`.
+- The [runner binary](https://github.com/actions/runner/releases) must be placed under `/home/runner/` and launched using `/home/runner/run.sh`.
 - If you use Kubernetes mode, the [runner container hooks](https://github.com/actions/runner-container-hooks/releases) must be placed under `/home/runner/k8s`.
 
 You can use the following example Dockerfile to start creating your own runner image.

diff --git a/...n-runners/managing-self-hosted-runners/running-scripts-before-or-after-a-job.md b/...n-runners/managing-self-hosted-runners/running-scripts-before-or-after-a-job.md
@@ -71,7 +71,7 @@ ACTIONS_RUNNER_HOOK_JOB_STARTED=/opt/runner/cleanup_script.sh
 
 ### Permission denied
 
-If you get a "permission denied" error when you attempt to run a script, make sure that the script is executable. For example, in a terminal on Linux or MacOS you can use the following command to make a file executable.
+If you get a "permission denied" error when you attempt to run a script, make sure that the script is executable. For example, in a terminal on Linux or macOS you can use the following command to make a file executable.
 
 ```bash
 chmod +x PATH/TO/FILE

diff --git a/content/actions/learn-github-actions/contexts.md b/content/actions/learn-github-actions/contexts.md
@@ -54,7 +54,7 @@ As part of an expression, you can access context information using one of two sy
 
 In order to use property dereference syntax, the property name must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`.
 
-If you attempt to dereference a non-existent property, it will evaluate to an empty string.
+If you attempt to dereference a nonexistent property, it will evaluate to an empty string.
 
 ### Determining when to use contexts
 

diff --git a/content/actions/learn-github-actions/variables.md b/content/actions/learn-github-actions/variables.md
@@ -383,7 +383,7 @@ jobs:
 
 {% endraw %}
 
-In this example, the two `if` statements check the `os` property of the `runner` context to determine the operating system of the runner. `if` conditionals are processed by {% data variables.product.prodname_actions %}, and only steps where the check resolves as `true` are sent to the runner. Here one of the checks will always be `true` and the other `false`, so only one of these steps is sent to the runner. Once the job is sent to the runner, the step is executed and the environment variable in the `echo` command is interpolated using the appropriate syntax (`$env:NAME` for PowerShell on Windows, and `$NAME` for bash and sh on Linux and MacOS). In this example, the statement `runs-on: macos-latest` means that the second step will be run.
+In this example, the two `if` statements check the `os` property of the `runner` context to determine the operating system of the runner. `if` conditionals are processed by {% data variables.product.prodname_actions %}, and only steps where the check resolves as `true` are sent to the runner. Here one of the checks will always be `true` and the other `false`, so only one of these steps is sent to the runner. Once the job is sent to the runner, the step is executed and the environment variable in the `echo` command is interpolated using the appropriate syntax (`$env:NAME` for PowerShell on Windows, and `$NAME` for bash and sh on Linux and macOS). In this example, the statement `runs-on: macos-latest` means that the second step will be run.
 
 ## Passing values between steps and jobs in a workflow
 

diff --git a/...omated-migrations/extending-github-actions-importer-with-custom-transformers.md b/...omated-migrations/extending-github-actions-importer-with-custom-transformers.md
@@ -63,10 +63,10 @@ You can create custom transformers that {% data variables.product.prodname_actio
 
 ### Example custom transformer for a build step
 
-The following example converts a build step that uses the "buildJavascriptApp" identifier to run various `npm` commands:
+The following example converts a build step that uses the "buildJavaScriptApp" identifier to run various `npm` commands:
 
 ```ruby copy
-transform "buildJavascriptApp" do |item|
+transform "buildJavaScriptApp" do |item|
   command = ["build", "package", "deploy"].map do |script|
     "npm run #{script}"
   end
@@ -78,7 +78,7 @@ transform "buildJavascriptApp" do |item|
 end
 ```
 
-The above example results in the following {% data variables.product.prodname_actions %} workflow step. It is comprised of converted build steps that had a `buildJavascriptApp` identifier:
+The above example results in the following {% data variables.product.prodname_actions %} workflow step. It is comprised of converted build steps that had a `buildJavaScriptApp` identifier:
 
 ```yaml
 - name: build javascript app
@@ -88,7 +88,7 @@ The above example results in the following {% data variables.product.prodname_ac
     npm run deploy
 ```
 
-The `transform` method uses the identifier of the build step from your source CI/CD instance in an argument. In this example, the identifier is `buildJavascriptLibrary`. You can also use comma-separated values to pass multiple identifiers to the `transform` method. For example, `transform "buildJavascriptApp", "buildTypescriptApp" { |item| ... }`.
+The `transform` method uses the identifier of the build step from your source CI/CD instance in an argument. In this example, the identifier is `buildJavaScriptLibrary`. You can also use comma-separated values to pass multiple identifiers to the `transform` method. For example, `transform "buildJavaScriptApp", "buildTypeScriptApp" { |item| ... }`.
 
 {% note %}
 

diff --git a/content/actions/security-guides/using-secrets-in-github-actions.md b/content/actions/security-guides/using-secrets-in-github-actions.md
@@ -402,7 +402,7 @@ You can use Base64 encoding to store small binary blobs as secrets. You can then
 
 1. Use `base64` to encode your file into a Base64 string. For example:
 
-   On MacOS, you could run:
+   On macOS, you could run:
 
    ```shell
    base64 -i cert.der -o cert.base64

diff --git a/...access-management/using-saml-for-enterprise-iam/mapping-okta-groups-to-teams.md b/...access-management/using-saml-for-enterprise-iam/mapping-okta-groups-to-teams.md
@@ -72,6 +72,6 @@ Enterprise owners can use the site admin dashboard to check how Okta groups are
 
 ## Viewing audit log events for mapped groups
 
-To monitor SSO activity for mapped groups, you can review the `external_group` and `external_identity` events events in the {% data variables.product.prodname_ghe_managed %} audit log.
+To monitor SSO activity for mapped groups, you can review the `external_group` and `external_identity` events in the {% data variables.product.prodname_ghe_managed %} audit log.
 
 For more information, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/audit-log-events-for-your-organization)."
diff --git a/...audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md b/...audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise.md
@@ -35,7 +35,7 @@ You can configure a retention period for audit log data for {% data variables.lo
 
 ## Managing Git events in the audit log
 
-You can enable or disable Git-related events, such as `git.clone` and `git.push`, from appearing in your audit log. For a list of the Git events are are logged, see "[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git)."
+You can enable or disable Git-related events, such as `git.clone` and `git.push`, from appearing in your audit log. For a list of the Git events are logged, see "[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git)."
 
 {% ifversion ghes %}
 If you do enable Git events, due to the large number of Git events that are logged, we recommend monitoring your instance's file storage and reviewing your related alert configurations. For more information, see "[AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)."

diff --git a/...-updating-your-instance/configuring-clustering/rebalancing-cluster-workloads.md b/...-updating-your-instance/configuring-clustering/rebalancing-cluster-workloads.md
@@ -26,7 +26,7 @@ You can run the following commands from any node in your cluster using the admin
 
 ## Checking the distribution of cluster jobs
 
-In some cases, such as hardware failure, the underlying software that that manages allocations will migrate tasks from the unhealthy node to a healthy node. If the unhealthy node recovers, the task may remain assigned to the recovered node, which can result in unbalanced load. The risk of job failure may increase if allocations are unbalanced and additional nodes fail. You can check the distribution of allocations using the `ghe-cluster-balance status` utility.
+In some cases, such as hardware failure, the underlying software that manages allocations will migrate tasks from the unhealthy node to a healthy node. If the unhealthy node recovers, the task may remain assigned to the recovered node, which can result in unbalanced load. The risk of job failure may increase if allocations are unbalanced and additional nodes fail. You can check the distribution of allocations using the `ghe-cluster-balance status` utility.
 
 1. To see a list of allocations, run the following command. The utility displays healthy allocations in green. If any jobs are not properly distributed, the utility displays the allocation's count in red.
 

diff --git a/...rprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise.md b/...rprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise.md
@@ -58,7 +58,7 @@ Across all organizations owned by your enterprise, you can control whether organ
 1. Under "{% octicon "law" aria-hidden="true" %} Policies", click **Code security and analysis**.
 1. Under "Dependency insights", review the information about changing the setting.
 1. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
-1. Under "Dependency insights", select the the dropdown menu and click a policy.
+1. Under "Dependency insights", select the dropdown menu and click a policy.
 
 {% endif %}
 

diff --git a/content/apps/oauth-apps/building-oauth-apps/authorizing-oauth-apps.md b/content/apps/oauth-apps/building-oauth-apps/authorizing-oauth-apps.md
@@ -25,7 +25,7 @@ topics:
 
 Both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %} use OAuth 2.0.
 
-{% data variables.product.prodname_github_apps %} can act on behalf of a user, similar to an {% data variables.product.prodname_oauth_app %}, or as themselves, which is beneficial for automations that do not require user input. Additionally, {% data variables.product.prodname_github_apps %} use fine grained permissions, give the user more control over which repositories the app can access, and use short-lived tokens. For more information, see "[AUTOTITLE](/apps/oauth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps)" and "[AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/about-creating-github-apps)."
+{% data variables.product.prodname_github_apps %} can act on behalf of a user, similar to an {% data variables.product.prodname_oauth_app %}, or as themselves, which is beneficial for automations that do not require user input. Additionally, {% data variables.product.prodname_github_apps %} use fine-grained permissions, give the user more control over which repositories the app can access, and use short-lived tokens. For more information, see "[AUTOTITLE](/apps/oauth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps)" and "[AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/about-creating-github-apps)."
 
 {% endnote %}
 

diff --git a/...auth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps.md b/...auth-apps/building-oauth-apps/differences-between-github-apps-and-oauth-apps.md
@@ -22,7 +22,7 @@ shortTitle: GitHub Apps & {% data variables.product.prodname_oauth_apps %}
 
 ## About {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
 
-In general, {% data variables.product.prodname_github_apps %} are preferred over {% data variables.product.prodname_oauth_apps %}. {% data variables.product.prodname_github_apps %} use fine grained permissions, give the user more control over which repositories the app can access, and use short-lived tokens. These properties can harden the security of your app by limiting the damage that could be done if your app's credentials were leaked.
+In general, {% data variables.product.prodname_github_apps %} are preferred over {% data variables.product.prodname_oauth_apps %}. {% data variables.product.prodname_github_apps %} use fine-grained permissions, give the user more control over which repositories the app can access, and use short-lived tokens. These properties can harden the security of your app by limiting the damage that could be done if your app's credentials were leaked.
 
 Similar to {% data variables.product.prodname_oauth_apps %}, {% data variables.product.prodname_github_apps %} can still use OAuth 2.0 and generate a type of OAuth token (called a user access token) and take actions on behalf of a user. However, {% data variables.product.prodname_github_apps %} can also act independently of a user. This is beneficial for automations that do not require user input. The app will continue to work even if the person who installed the app on an organization leaves the organization.
 

diff --git a/...ation/troubleshooting-ssh/error-ssh-add-illegal-option----apple-use-keychain.md b/...ation/troubleshooting-ssh/error-ssh-add-illegal-option----apple-use-keychain.md
@@ -30,7 +30,7 @@ To add your SSH private key to the ssh-agent, you can specify the path to the Ap
 
 **Notes:**
 
-- The `--apple-use-keychain` option is in Apple's standard version of `ssh-add`. In MacOS versions prior to Monterey (12.0), use `-K` instead of `--apple-use-keychain`.
+- The `--apple-use-keychain` option is in Apple's standard version of `ssh-add`. In macOS versions prior to Monterey (12.0), use `-K` instead of `--apple-use-keychain`.
 - {% data reusables.ssh.add-ssh-key-to-ssh-agent %}
 
 {% endnote %}

diff --git a/...ling-for-github-advanced-security/about-billing-for-github-advanced-security.md b/...ling-for-github-advanced-security/about-billing-for-github-advanced-security.md
@@ -58,7 +58,7 @@ You can determine how many licenses you'll need for {% data variables.product.pr
 {% ifversion ghec %}
 If you use {% data variables.product.prodname_ghe_cloud %} with an enterprise account and pay with a credit card, you can purchase a {% data variables.product.prodname_GH_advanced_security %} license or start a free trial from your enterprise account settings. For more information, see "[AUTOTITLE](/billing/managing-billing-for-github-advanced-security/signing-up-for-github-advanced-security)" and "[AUTOTITLE](/billing/managing-billing-for-github-advanced-security/setting-up-a-trial-of-github-advanced-security)."
 
-You can not purchase {% data variables.product.prodname_GH_advanced_security %} or start a {% data variables.product.prodname_GH_advanced_security %} trial if you are currently on a {% data variables.product.prodname_ghe_cloud %} trial.
+You cannot purchase {% data variables.product.prodname_GH_advanced_security %} or start a {% data variables.product.prodname_GH_advanced_security %} trial if you are currently on a {% data variables.product.prodname_ghe_cloud %} trial.
 
 If you pay by invoice, contact {% data variables.contact.contact_enterprise_sales %} to discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise.
 

diff --git a/...advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages.md b/...advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages.md
@@ -45,7 +45,7 @@ topics:
 For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you can use default setup, which analyzes your code and automatically configures your {% data variables.product.prodname_code_scanning %}, or advanced setup, which generates a workflow file you can edit. {% ifversion codeql-swift-advanced-setup %}Default setup can analyze all compiled languages supported by {% data variables.product.prodname_codeql %}.{% endif %} For more information about advanced setup, see "[AUTOTITLE](/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/configuring-advanced-setup-for-code-scanning#configuring-advanced-setup-for-code-scanning-with-codeql)."
 
 {% ifversion code-scanning-default-setup-self-hosted-310 or default-setup-self-hosted-runners-GHEC %}
-You can use default setup with self-hosted runners for all {% data variables.product.prodname_codeql %}-supported languages{% ifversion codeql-swift-advanced-setup %} except Swift{% endif %}. Default setup will always run the `autobuild` action, so you should configure your self-hosted runners to make sure they can run all necessary commands for C/C++, C#, and Java analysis. Analysis of Javascript/Typescript, Go, Ruby, Python, and Kotlin code does not currently require special configuration.
+You can use default setup with self-hosted runners for all {% data variables.product.prodname_codeql %}-supported languages{% ifversion codeql-swift-advanced-setup %} except Swift{% endif %}. Default setup will always run the `autobuild` action, so you should configure your self-hosted runners to make sure they can run all necessary commands for C/C++, C#, and Java analysis. Analysis of JavaScript/TypeScript, Go, Ruby, Python, and Kotlin code does not currently require special configuration.
 {% endif %}
 
 {% elsif code-scanning-without-workflow %}

diff --git a/...ode-scanning/troubleshooting-code-scanning/fewer-lines-scanned-than-expected.md b/...ode-scanning/troubleshooting-code-scanning/fewer-lines-scanned-than-expected.md
@@ -1,7 +1,7 @@
 ---
 title: CodeQL scanned fewer lines than expected
 shortTitle: Fewer lines scanned than expected
-intro: 'If {% data variables.product.prodname_codeql %} analyzed less code than than you expected, you may need to use a custom build command.'
+intro: 'If {% data variables.product.prodname_codeql %} analyzed less code than you expected, you may need to use a custom build command.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'

diff --git a/...-of-the-codeql-cli/specifying-command-options-in-a-codeql-configuration-file.md b/...-of-the-codeql-cli/specifying-command-options-in-a-codeql-configuration-file.md
@@ -45,7 +45,7 @@ To apply the same options to more than one command you can:
 {% note %}
 
 **Notes:**
-- `config` files only accept spaces between between option flags and values—{% data variables.product.prodname_codeql %} will throw an error if you use `=` to specify an option value.
+- `config` files only accept spaces between option flags and values—{% data variables.product.prodname_codeql %} will throw an error if you use `=` to specify an option value.
 - If you specify an option in the command line, this overrides the `config` value defined for that option.
 - If you want to specify more than one option for a `<command>`, `<subcommand>` or globally, use one line per option.
 

diff --git a/...pendabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md b/...pendabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md
@@ -446,7 +446,7 @@ encoding@^0.1.11:
 
 If the `yarn.lock` file doesn't list the private registry as the dependency source, you can set up Yarn Classic according to the standard package manager instructions.
 
-1. Define the private registry configuration in the the `dependabot.yml` file.
+1. Define the private registry configuration in the `dependabot.yml` file.
 1. You can then either:
     - Manually set the private registry to the `.yarnrc` file by adding the registry to a `.yarnrc.yml` file in the project root with the key registry, or
     - Perform the same action by running `yarn config set registry <private registry URL>` in your terminal.
@@ -505,7 +505,7 @@ Finally, we recommend you run `yarn login` to verify that your configuration is
 
 If the `yarn.lock` file doesn't list the private registry as the dependency source, you can set up Yarn Berry according to the standard package manager instructions.
 
-1. Define the private registry configuration in the the `dependabot.yml` file.
+1. Define the private registry configuration in the `dependabot.yml` file.
 1. You can then either:
     - Manually set the private registry to the `.yarnrc` file by adding the registry to a `.yarnrc.yml` file in the project root with the key `npmRegistryServer`, or
     - Perform the same action by running `yarn config set npmRegistryServer <private registry URL>` in your terminal.

diff --git a/content/code-security/getting-started/securing-your-organization.md b/content/code-security/getting-started/securing-your-organization.md
@@ -104,7 +104,7 @@ On this view, you can use checkboxes to select specific repositories, or you can
 {% endif %}
 
 {% ifversion ghec or ghes %}
-If you have a limited number of licenses for {% data variables.product.prodname_GH_advanced_security %}, you may want to prioritize repositories that contain critical projects, or that have the highest commit frequencies. For more information, see "[AUTOTITLE](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)." {% ifversion ghec %}When you use the "Security coverage" view, you can can see the number of active committers for the repositories you select, and therefore the number of {% data variables.product.prodname_GH_advanced_security %} licenses that enabling a feature will consume.{% endif %}
+If you have a limited number of licenses for {% data variables.product.prodname_GH_advanced_security %}, you may want to prioritize repositories that contain critical projects, or that have the highest commit frequencies. For more information, see "[AUTOTITLE](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security)." {% ifversion ghec %}When you use the "Security coverage" view, you can see the number of active committers for the repositories you select, and therefore the number of {% data variables.product.prodname_GH_advanced_security %} licenses that enabling a feature will consume.{% endif %}
 {% endif %}
 
 {% data reusables.security-overview.settings-limitations %}