Remove mention of steps from concurrency description

Concurrency group can be defined either on a workflow level or on a job level. Steps should not be mentioned because it's not possible to control concurrency on a job step level.
github · Jan 28, 2025 · 2eb1442 · 2eb1442
1 parent fb0ebe7
commit 2eb1442
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/...oosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs.md b/...oosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs.md
@@ -16,9 +16,9 @@ redirect_from:
 
 ## Overview
 
-By default, {% data variables.product.prodname_actions %} allows multiple jobs within the same workflow, multiple workflow runs within the same repository, and multiple workflow runs across a repository owner's account to run concurrently. This means that multiple workflow runs, jobs, or steps can run at the same time.
+By default, {% data variables.product.prodname_actions %} allows multiple jobs within the same workflow, multiple workflow runs within the same repository, and multiple workflow runs across a repository owner's account to run concurrently. This means that multiple instances of the same workflow or job can run at the same time.
 
-{% data variables.product.prodname_actions %} also allows you to control the concurrency of workflow runs, so that you can ensure that only one run, one job, or one step runs at a time in a specific context. This can be useful for controlling your account's or organization's resources in situations where running multiple workflows, jobs, or steps at the same time could cause conflicts or consume more Actions minutes and storage than expected.
+{% data variables.product.prodname_actions %} also allows you to disable concurrency, limiting a workflow or a job to a single running instance at any given time in a specific context. This can be useful for controlling your account's or organization's resources in situations where running multiple workflows or jobs at the same time could cause conflicts or consume more Actions minutes and storage than expected.
 
 For example, the ability to run workflows concurrently means that if multiple commits are pushed to a repository in quick succession, each push could trigger a separate workflow run, and these runs will execute concurrently.