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.

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

Misspelled brand names in content #30826

Closed
1 task done
jsoref opened this issue Dec 26, 2023 · 0 comments · Fixed by #30827
Closed
1 task done

Misspelled brand names in content #30826

jsoref opened this issue Dec 26, 2023 · 0 comments · Fixed by #30827
Labels
content This issue or pull request belongs to the Docs Content team

Comments

@jsoref
Copy link
Contributor

jsoref commented Dec 26, 2023

Code of Conduct

What article on docs.github.com is affected?

  • content/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/deploying-runner-scale-sets-with-actions-runner-controller.md
  • content/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages.md
  • content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md
  • contributing/codespace.md
  • (content using the reusable: data/features/actions-default-workflow-permissions-restrictive.yml)

What part(s) of the article would you like to see updated?

references to brands should be spelled correctly

Additional information

No response

@jsoref jsoref added the content This issue or pull request belongs to the Docs Content team label Dec 26, 2023
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team. label Dec 26, 2023
@nguyenalex836 nguyenalex836 removed the triage Do not begin working on this issue until triaged by the team. label Dec 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants