Fix typo in self-hosted runners architecture labels

[garysassano]

Why:

The main self-hosted runners page mentions ARM32 as an architecture, while elsewhere that's referenced simply as ARM so it must be wrong in one place.

Closes:

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

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.

[github-actions]

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/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow.md	fpt ghec ghes@ 3.11 3.10 3.9 3.8	fpt ghec ghes@ 3.11 3.10 3.9 3.8

---

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

[nguyenalex836]

@garysassano Thanks so much for opening a PR! I'll get this triaged for review ✨

[SiaraMist]

Thank you for updating this, @garysassano! ✨ I'll go ahead and get it merged.

Oops, I approved this too soon, apologies. If you go to one of your repositories and add a self-hosted runner, you'll see that when you choose a runner with a Linux operating system, the choices for available architectures are x64, ARM, and ARM64. Whichever architecture you chose would then be added as a label to the runner, which matches what the article you are updating says. If you set the runs-on key to runs-on: [self-hosted, linux, ARM32], it would not work because ARM32 would not be an accurate runner label. In light of that, I'm going to close this pull request. We really appreciate you thinking critically about the docs and making fixes!

[garysassano]

@SiaraMist So It was probably this page that needed to be aligned for consistency in naming.