diff --git a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow.md b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow.md
index 9d6e8c13ac99..2891ffd7ba27 100644
--- a/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-self-hosted-runners-in-a-workflow.md
@@ -61,7 +61,7 @@ A self-hosted runner automatically receives certain labels when it is added to {
 
 - `self-hosted`: Default label applied to all self-hosted runners.
 - `linux`, `windows`, or `macOS`: Applied depending on operating system.
-- `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture.
+- `x64`, `ARM32`, or `ARM64`: Applied depending on hardware architecture.
 
 You can use your workflow's YAML to send jobs to a combination of these labels. In this example, a self-hosted runner that matches all three labels will be eligible to run the job: