Skip to content

Commit d90a746

Browse files
authored
Spelling fixes for various typos (github#30890)
Signed-off-by: Josh Soref <[email protected]>
1 parent f46562a commit d90a746

File tree

47 files changed

+60
-60
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

47 files changed

+60
-60
lines changed

.github/CONTRIBUTING.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ To get an overview of the project, read the [README](README.md) file. Here are s
2020

2121
## Getting started
2222

23-
To navigate our codebase with confidence, see [the introduction to working in the docs repository](/contributing/README.md) :confetti_ball:. For more information on how we write our markdown files, see "[Using Makrdown and Liquid in GitHub Docs](https://docs.github.com/en/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs).
23+
To navigate our codebase with confidence, see [the introduction to working in the docs repository](/contributing/README.md) :confetti_ball:. For more information on how we write our markdown files, see "[Using Markdown and Liquid in GitHub Docs](https://docs.github.com/en/contributing/writing-for-github-docs/using-markdown-and-liquid-in-github-docs).
2424

2525
Check to see what [types of contributions](/contributing/types-of-contributions.md) we accept before making changes. Some of them don't even require writing a single line of code :sparkles:.
2626

.github/actions/setup-elasticsearch/action.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
name: Set up local Elasticsearch
22

3-
description: Install a local Elasticseach with version that matches prod
3+
description: Install a local Elasticsearch with version that matches prod
44

55
inputs:
66
token:

content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Use a wait timer to delay a job for a specific amount of time after the job is i
7575
Use deployment branches{% ifversion deployment-protections-tag-patterns %} and tags{% endif %} to restrict which branches{% ifversion deployment-protections-tag-patterns %} and tags{% endif %} can deploy to the environment. Below are the options for deployment branches{% ifversion deployment-protections-tag-patterns %} and tags{% endif %} for an environment:
7676

7777
{% ifversion deployment-protections-tag-patterns %}
78-
- **No restriction**: No restriction on which branch or tag can deploy to the enviornment.
78+
- **No restriction**: No restriction on which branch or tag can deploy to the environment.
7979
{%- else %}
8080
- **All branches**: All branches in the repository can deploy to the environment.
8181
{%- endif %}

content/actions/migrating-to-github-actions/automated-migrations/migrating-from-bitbucket-pipelines-with-github-actions-importer.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -284,7 +284,7 @@ The following table shows the type of properties that {% data variables.product.
284284
| `caches` | `actions/cache` | Supported |
285285
| `clone` | `actions/checkout` | Supported |
286286
| `condition` | `job.<job_id>.steps[*].run` | Supported |
287-
| `deployment` | `jobs.<job_id>.environmen` | Supported |
287+
| `deployment` | `jobs.<job_id>.environment` | Supported |
288288
| `image` | `jobs.<job_id>.container` | Supported |
289289
| `max-time` | `jobs.<job_id>.steps[*].timeout-minutes` | Supported |
290290
| `options.docker` | None | Supported |

content/admin/administering-your-instance/administering-your-instance-from-the-command-line/administering-your-instance-using-the-github-cli.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Administering your instance using the GitHub CLI
3-
intro: 'You can adminster your GitHub Enterprise Server instance using the GitHub CLI extension for GHES Manage API.'
3+
intro: 'You can administer your GitHub Enterprise Server instance using the GitHub CLI extension for GHES Manage API.'
44
versions:
55
feature: ghes-manage-api-cli-extension
66
type: how_to

content/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -973,7 +973,7 @@ This utility starts {% data variables.product.prodname_actions %} on {% data var
973973
974974
{% endnote %}
975975
976-
If your system is configured correctly, you'll see the following ouput:
976+
If your system is configured correctly, you'll see the following output:
977977

978978
```shell
979979
Actions was enabled!

content/admin/configuration/configuring-private-networking-for-hosted-compute-products/configuring-private-networking-for-github-hosted-runners.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -169,7 +169,7 @@ You will use a script to automate configuring your Azure resources.
169169

170170
You can use the following GraphQL query to retrieve your enterprise `databaseId`. You will use the enterprise `databaseId` for the value of the `DATABASE_ID` environment variable in the next step. For more information on working with GraphQL, see "[AUTOTITLE](/graphql/guides/forming-calls-with-graphql)."
171171

172-
{% data reusables.enterprise_migrations.retreive-enterprise-id-graphql %}
172+
{% data reusables.enterprise_migrations.retrieve-enterprise-id-graphql %}
173173

174174
```graphql
175175
query(

content/admin/identity-and-access-management/provisioning-user-accounts-for-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ After creating your {% data variables.product.pat_generic %} and storing it secu
7373

7474
### Configuring provisioning if you use a partner IdP
7575

76-
To use a partner IdP's application both authentication and provisioning, review the parner's instructions for configuring provisioning in the links in the following table. {% else %} For instructions about the configuration of provisioning on your IdP, click a link in the following table.
76+
To use a partner IdP's application both authentication and provisioning, review the partner's instructions for configuring provisioning in the links in the following table. {% else %} For instructions about the configuration of provisioning on your IdP, click a link in the following table.
7777

7878
{% endif %}
7979

content/admin/identity-and-access-management/provisioning-user-accounts-for-enterprise-managed-users/troubleshooting-team-membership-with-identity-provider-groups.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ If {% data variables.product.prodname_dotcom %} is unable to synchronize team me
2929
1. In the list of IdP groups, click the group you'd like to review.
3030
1. To review the synchronization error for the group, under the name of the group, click **Teams**.
3131

32-
![Screenshot of the page for a synchronized IdP group. Under the name of the group, to the right, the "Teams" tab is highlighed in dark orange.](/assets/images/help/enterprises/idp-group-sync-teams-tab.png)
32+
![Screenshot of the page for a synchronized IdP group. Under the name of the group, to the right, the "Teams" tab is highlighted in dark orange.](/assets/images/help/enterprises/idp-group-sync-teams-tab.png)
3333

3434
If a team is unable to sync membership with a group on your IdP, you'll see a description of the problem under the team's name and membership count.
3535

content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Before suspending site administrators, you must demote them to regular users. Fo
4646

4747
{% data reusables.enterprise_site_admin_settings.access-settings %}
4848
1. In the left sidebar, click **Suspended users**.
49-
1. A list of suspened users displays.
49+
1. A list of suspended users displays.
5050

5151
## Suspending a user from the site admin dashboard
5252

content/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -193,7 +193,7 @@ You can view a list of all dormant users {% ifversion ghes or ghae %} who have n
193193

194194
## Filtering by member type{% ifversion ghec %} in an {% data variables.enterprise.prodname_emu_enterprise %}{% endif %}
195195

196-
{% ifversion ghec %}If your enterprise uses {% data variables.product.prodname_emus %}, you{% elsif ghes or ghae %}You{% endif %} can filter the member list of an organization by type to determine if memberships are managed through an IdP or managed directly. Memberships managed through an IdP were added through an IdP group, and the IdP group was connected to a team within the organization. Memberships managed directly were added to the organization manually. The way a membership is mananaged in an organization determines how it must be removed. You can use this filter to determine how members were added to an organization, so you know how to remove them.{% ifversion ghec %} For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#about-organization-membership-management)."{% endif %}
196+
{% ifversion ghec %}If your enterprise uses {% data variables.product.prodname_emus %}, you{% elsif ghes or ghae %}You{% endif %} can filter the member list of an organization by type to determine if memberships are managed through an IdP or managed directly. Memberships managed through an IdP were added through an IdP group, and the IdP group was connected to a team within the organization. Memberships managed directly were added to the organization manually. The way a membership is managed in an organization determines how it must be removed. You can use this filter to determine how members were added to an organization, so you know how to remove them.{% ifversion ghec %} For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users#about-organization-membership-management)."{% endif %}
197197

198198
{% data reusables.enterprise-accounts.access-enterprise %}
199199
1. Under "Organizations", in the search bar, begin typing the organization's name until it appears in the search results.

content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ CM | `packages_stats.ecosystems.ruby_gems.registry_enabled` | Whether Rubygems i
148148
CN | `packages_stats.ecosystems.ruby_gems.published_packages_count` | Number of published Rubygems packages (private, public, and internal)
149149
CO | `packages_stats.ecosystems.ruby_gems.private_packages_count` | Number of private Rubygems packages
150150
CP | `packages_stats.ecosystems.ruby_gems.public_packages_count` | Number of public Rubygems packages
151-
CQ | `packages_stats.ecosystems.ruby_gems.internal_packages_count` | Number of internal Rubygems packaes
151+
CQ | `packages_stats.ecosystems.ruby_gems.internal_packages_count` | Number of internal Rubygems packages
152152
CR | `packages_stats.ecosystems.ruby_gems.user_packages_count` | Number of Rubygems packages owned by user accounts
153153
CS | `packages_stats.ecosystems.ruby_gems.organization_packages_count` | Number of Rubygems packages owned by organizations
154154
CT | `packages_stats.ecosystems.ruby_gems.daily_download_count` | Number of downloads of Rubygems packages

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -269,7 +269,7 @@ To get a list of IP address ranges that {% data variables.product.prodname_dotco
269269

270270
- The port on which the application accepts data.<br>
271271

272-
If you're using Splunk Cloud and haven't changed the port configration, `Port` should be `443`.
272+
If you're using Splunk Cloud and haven't changed the port configuration, `Port` should be `443`.
273273

274274
If you're using the free trial version of Splunk Cloud, `Port` should be `8088`.
275275

content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -295,7 +295,7 @@ The unauthenticated git protocol on port 9418 is no longer supported.
295295

296296
{% ifversion ghes %}
297297

298-
If you wish to support the unathenticated Git protocol in your environment, you must manually re-enable the feature. Run the following commands after your upgrade:
298+
If you wish to support the unauthenticated Git protocol in your environment, you must manually re-enable the feature. Run the following commands after your upgrade:
299299

300300
```shell
301301
sudo ghe-config app.gitauth.git-protocol true

content/apps/creating-github-apps/writing-code-for-a-github-app/building-ci-checks-with-a-github-app.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -288,7 +288,7 @@ class GHAapp < Sinatra::Application
288288
# Instantiate an Octokit client authenticated as a GitHub App.
289289
# GitHub App authentication requires that you construct a
290290
# JWT (https://jwt.io/introduction/) signed with the app's private key,
291-
# so GitHub can be sure that it came from the app an not altererd by
291+
# so GitHub can be sure that it came from the app and not altered by
292292
# a malicious third party.
293293
def authenticate_app
294294
payload = {
@@ -885,7 +885,7 @@ Open your `server.rb` file. In the code block that starts with `helpers do`, whe
885885
886886
The code above uses the `ruby-git` gem to clone the repository using the app's installation token. It clones the code in the same directory as `server.rb`. To run Git commands in the repository, the code needs to change into the repository directory. Before changing directories, the code stores the current working directory in a variable (`pwd`) to remember where to return before exiting the `clone_repository` method.
887887
888-
From the repository directory, this code fetches and merges the latest changes (`@git.pull`), and checks out the specifig Git ref (`@git.checkout(ref)`). The code to do all of this fits nicely into its own method. To perform these operations, the method needs the name and full name of the repository and the ref to checkout. The ref can be a commit SHA, branch, or tag. When it's done, the code changes the directory back to the original working directory (`pwd`).
888+
From the repository directory, this code fetches and merges the latest changes (`@git.pull`), and checks out the specific Git ref (`@git.checkout(ref)`). The code to do all of this fits nicely into its own method. To perform these operations, the method needs the name and full name of the repository and the ref to checkout. The ref can be a commit SHA, branch, or tag. When it's done, the code changes the directory back to the original working directory (`pwd`).
889889
890890
Now you've got a method that clones a repository and checks out a ref. Next, you need to add code to get the required input parameters and call the new `clone_repository` method.
891891
@@ -1510,7 +1510,7 @@ class GHAapp < Sinatra::Application
15101510
# Instantiate an Octokit client authenticated as a GitHub App.
15111511
# GitHub App authentication requires that you construct a
15121512
# JWT (https://jwt.io/introduction/) signed with the app's private key,
1513-
# so GitHub can be sure that it came from the app an not altererd by
1513+
# so GitHub can be sure that it came from the app and not altered by
15141514
# a malicious third party.
15151515
def authenticate_app
15161516
payload = {

content/apps/using-github-apps/saml-and-github-apps.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ If your organization uses SAML SSO, you may not be able to see your organization
1919

2020
## Installing or requesting {% data variables.product.prodname_github_apps %} for SAML users
2121

22-
If your organization uses SAML, you may not see your organzation listed when you try to install or request an {% data variables.product.prodname_github_app %} for your organization. To resolve this issue, follow these steps:
22+
If your organization uses SAML, you may not see your organization listed when you try to install or request an {% data variables.product.prodname_github_app %} for your organization. To resolve this issue, follow these steps:
2323

2424
1. Go to `https://github.com/orgs/ORGANIZATION-NAME/sso` to start an active SAML session for your organization. Replace `ORGANIZATION-NAME` with the name of your organization.
2525
1. Try to install or request the {% data variables.product.prodname_github_app %} again. For more information, see "[AUTOTITLE](/apps/using-github-apps/installing-a-github-app-from-a-third-party)," "[AUTOTITLE](/apps/using-github-apps/installing-a-github-app-from-github-marketplace-for-your-organizations)," and "[AUTOTITLE](/apps/using-github-apps/requesting-a-github-app-from-your-organization-owner)."

content/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ When you upgrade an app, your payment method is charged a prorated amount based
4747

4848
{% data reusables.enterprise-accounts.access-enterprise %}
4949
{% data reusables.enterprise-accounts.billing-tab %}
50-
1. In the "Marketplace apps" tab, find the app you want to uprade.
50+
1. In the "Marketplace apps" tab, find the app you want to upgrade.
5151
1. Next to the organization where you want to upgrade the app, select **{% octicon "kebab-horizontal" aria-label="More" %}** and then click **Change plan**.
5252
1. Select the **Edit your plan** dropdown and click an account's plan to edit.
5353
{% data reusables.marketplace.choose-new-plan %}

content/code-security/code-scanning/troubleshooting-sarif-uploads/file-too-large.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ If you still have too many results, check how many queries you are using to anal
5858

5959
Sometimes a single query reports many results because the codebase has a specific coding style, or because the analysis does not understand a particular library. You can review the results file in a SARIF viewer to see the distribution of results. For example, https://microsoft.github.io/sarif-web-component/.
6060

61-
- Check if the results are dominated by alerts identfied by a single query. Try excluding that query from analysis. You can reintroduce it when other alerts are fixed. For more information about {% data variables.product.prodname_codeql %} query configuration, see "[Excluding a query from analysis](#excluding-a-query-from-analysis)."
61+
- Check if the results are dominated by alerts identified by a single query. Try excluding that query from analysis. You can reintroduce it when other alerts are fixed. For more information about {% data variables.product.prodname_codeql %} query configuration, see "[Excluding a query from analysis](#excluding-a-query-from-analysis)."
6262
- Check if there are dataflow queries with many deep paths. Try omitting dataflow paths from the output. For more information about {% data variables.product.prodname_codeql %} analysis configuration, see "[Omitting dataflow paths from the output](#omitting-dataflow-paths-from-the-output)."
6363

6464
## Fixing the problem

content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -239,7 +239,7 @@ registry=https://<private-registry-url>
239239

240240
{% endraw %}
241241

242-
Aternatively you can add the private registry URL to an existing `.npmrc` file using the following command.
242+
Alternatively you can add the private registry URL to an existing `.npmrc` file using the following command.
243243

244244
{% raw %}
245245

@@ -627,7 +627,7 @@ If you are restricting which IPs can reach your Nexus host, you need to add the
627627
- "3.217.93.44/32"
628628
For more information, see [Securing Nexus Repository Manager](https://help.sonatype.com/repomanager3/planning-your-implementation/securing-nexus-repository-manager) in the Sonatype documentation.
629629

630-
Registries can be proxied to reach out to a public registry in case a dependency is not available in the private regstry.{% ifversion dependabot-private-registries %} However, you may want {% data variables.product.prodname_dependabot %} to only access the private registry and not access the public registry at all. For more information, see [Quick Start Guide - Proxying Maven and NPM](https://help.sonatype.com/repomanager3/planning-your-implementation/quick-start-guide---proxying-maven-and-npm)" in the Sonatype documentation, and "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/removing-dependabot-access-to-public-registries)."{% endif %}
630+
Registries can be proxied to reach out to a public registry in case a dependency is not available in the private registry.{% ifversion dependabot-private-registries %} However, you may want {% data variables.product.prodname_dependabot %} to only access the private registry and not access the public registry at all. For more information, see [Quick Start Guide - Proxying Maven and NPM](https://help.sonatype.com/repomanager3/planning-your-implementation/quick-start-guide---proxying-maven-and-npm)" in the Sonatype documentation, and "[AUTOTITLE](/code-security/dependabot/working-with-dependabot/removing-dependabot-access-to-public-registries)."{% endif %}
631631

632632
### ProGet
633633

0 commit comments

Comments
 (0)