Spelling docs (#30792)

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>

Author: jsoref

content/actions/hosting-your-own-runners/managing-self-hosted-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.

content/actions/hosting-your-own-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

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
 

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
 

content/actions/migrating-to-github-actions/automated-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 %}
 

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

content/admin/identity-and-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)."

content/admin/monitoring-activity-in-your-enterprise/reviewing-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)."

content/admin/monitoring-managing-and-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.
 

content/admin/policies/enforcing-policies-for-your-enterprise/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 %}