From 25de950005dc876897fc26f692d15d2aa76b72ca Mon Sep 17 00:00:00 2001
From: "lehcar (rachel)" <37482914+Lehcar@users.noreply.github.com>
Date: Tue, 9 Aug 2022 12:43:24 -0700
Subject: [PATCH] Update using custom labels to route jobs

---
 .../using-self-hosted-runners-in-a-workflow.md                  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md b/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
index c5a957c3bf..2bfb341c9e 100644
--- a/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
+++ b/content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
@@ -63,7 +63,7 @@ runs-on: [self-hosted, linux, x64, gpu]
 - `x64` - Only use a runner based on x64 hardware.
 - `gpu` - This custom label has been manually assigned to self-hosted runners with the GPU hardware installed. 
 
-These labels operate cumulatively, so a self-hosted runner’s labels must match all four to be eligible to process the job.
+These labels operate cumulatively, so a self-hosted runner must have all four labels to be eligible to process the job.
 
 ## Routing precedence for self-hosted runners