repo sync

content/actions/hosting-your-own-runners/about-self-hosted-runners.md

@@ -63,7 +63,7 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
 {% data reusables.github-actions.usage-api-requests %}
 - **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
 
-### Supported operating systems for self-hosted runners
+### Supported architectures and operating systems for self-hosted runners
 
 The following operating systems are supported for the self-hosted runner application.
 
@@ -92,6 +92,14 @@ The following operating systems are supported for the self-hosted runner applica
 
 - macOS 10.13 (High Sierra) or later
 
+#### Architectures
+
+The following processor architectures are supported for the self-hosted runner application.
+
+- `x64` - Linux, macOS, Windows.
+- `ARM64` - Linux only.
+- `ARM32` - Linux only.
+
 {% if enterpriseServerVersions contains currentVersion %}
 
 ### Supported actions on self-hosted runners

content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md

@@ -29,7 +29,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.
-* `x86`, `x64`, `ARM`, or `ARM64`: Applied depending on hardware architecture.
+* `x64`, `ARM`, 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: