Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spelling fixes #35097

Merged
merged 5 commits into from
Nov 1, 2024
Merged

Spelling fixes #35097

merged 5 commits into from
Nov 1, 2024

Conversation

ArieHein
Copy link
Contributor

@ArieHein ArieHein commented Oct 29, 2024 •
edited
Loading

Why:

Christmas is early and you get an early present in the form of a few spell fixes across all areas of the repo.

Closes:

Hopefully some of my OCD spotting the spelling problems :)

What's being changed (if available, include any code snippets, screenshots, or gifs):

Markdown files across all areas of the repo

Check off the following:

  • I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

    • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

  • For content changes, I have completed the self-review checklist.

@welcome Welcome
Copy link

welcome bot commented Oct 29, 2024

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Oct 29, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Oct 29, 2024 •
edited
Loading

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source Preview Production What Changed
actions/migrating-to-github-actions/using-github-actions-importer-to-automate-migrations/extending-github-actions-importer-with-custom-transformers.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/managing-invitations-to-organizations-within-your-enterprise.md ghec
 ghec
admin/upgrading-your-instance/performing-an-upgrade/upgrading-with-an-upgrade-package.md ghes@ 3.14 3.13 3.12 3.11 3.10
ghes@ 3.14 3.13 3.12 3.11 3.10
admin/upgrading-your-instance/preparing-to-upgrade/overview-of-the-upgrade-process.md ghes@ 3.14 3.13 3.12 3.11 3.10
ghes@ 3.14 3.13 3.12 3.11 3.10
billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md fpt
ghec
ghes@ 3.14 3.13 3.12
fpt
ghec
ghes@ 3.14 3.13 3.12
billing/using-the-new-billing-platform/about-the-new-billing-platform-for-enterprises.md ghec
 ghec
code-security/code-scanning/troubleshooting-code-scanning/advanced-security-must-be-enabled.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
code-security/code-scanning/troubleshooting-code-scanning/cannot-enable-codeql-in-a-private-repository.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
code-security/code-scanning/troubleshooting-sarif-uploads/results-exceed-limit.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
code-security/codeql-for-vs-code/using-the-advanced-functionality-of-the-codeql-for-vs-code-extension/telemetry-in-codeql-for-visual-studio-code.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
code-security/dependabot/working-with-dependabot/about-dependabot-on-github-actions-runners.md fpt
ghec
 fpt
ghec
code-security/securing-your-organization/managing-the-security-of-your-organization/interpreting-security-findings.md fpt
ghec
 fpt
ghec
issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/available-rules-for-rulesets.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11
admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md ghes@ 3.14 3.13 3.12 3.11 3.10
ghes@ 3.14 3.13 3.12 3.11 3.10
from reusable
admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md ghes@ 3.14 3.13 3.12 3.11 3.10
ghes@ 3.14 3.13 3.12 3.11 3.10
from reusable
admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md ghes@ 3.14 3.13 3.12 3.11 3.10
ghes@ 3.14 3.13 3.12 3.11 3.10
from reusable
admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md ghes@ 3.14 3.13 3.12 3.11 3.10
ghes@ 3.14 3.13 3.12 3.11 3.10
from reusable
admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md ghes@ 3.14 3.13 3.12 3.11 3.10
ghes@ 3.14 3.13 3.12 3.11 3.10
from reusable
admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md ghes@ 3.14 3.13 3.12 3.11 3.10
ghes@ 3.14 3.13 3.12 3.11 3.10
from reusable
code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
fpt
ghec
ghes@ 3.14 3.13 3.12 3.11 3.10
from reusable

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

@nguyenalex836 nguyenalex836 added content This issue or pull request belongs to the Docs Content team ready to merge This pull request is ready to merge and removed triage Do not begin working on this issue until triaged by the team labels Oct 29, 2024
@nguyenalex836
Copy link
Contributor

@ArieHein Thank you for opening a PR with all of these fixes! 🎁 We appreciate the holiday spirit 😄 ✨ We made one minor change, but aside from that, these changes look wonderful!

We are currently in a repo freeze, but we'll get this merged on November 1st when the freeze ends 🍏

If you're looking for other issues to pick up, take a look at our help wanted section to find open issues you can work on! ✨

@ArieHein
Copy link
Contributor Author

ArieHein commented Oct 29, 2024 •
edited
Loading

No problem and yes ive seen the issue there but it does make me wonder as Aarch64 is basically a differernt word for Arm64.
And yes, its GH Universe so not a problem, enjoy the event :)

@nguyenalex836 nguyenalex836 added this pull request to the merge queue Nov 1, 2024
Merged via the queue into github:main with commit 8a561ef Nov 1, 2024
44 checks passed
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 1, 2024

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@nguyenalex836 nguyenalex836 nguyenalex836 approved these changes

Assignees
No one assigned
Labels
content This issue or pull request belongs to the Docs Content team ready to merge This pull request is ready to merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ArieHein @nguyenalex836