Skip to content

Commit 586e2e5

Browse files
authored
Update task states terminology in services.md (#24467)
<!--Delete sections as needed --> ## Description Corrected task states terminology in the documentation. <!-- Tell us what you did and why --> ## Related issues or tickets Closes #24464 <!-- Related issues, pull requests, or Jira tickets --> ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [ ] Technical review - [ ] Editorial review - [ ] Product review
2 parents e4259e3 + b7d7110 commit 586e2e5

File tree

1 file changed

+1
-1
lines changed
  • content/manuals/engine/swarm/how-swarm-mode-works

1 file changed

+1
-1
lines changed

content/manuals/engine/swarm/how-swarm-mode-works/services.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,7 +53,7 @@ fails its health check or crashes, the orchestrator creates a new replica task
5353
that spawns a new container.
5454

5555
A task is a one-directional mechanism. It progresses monotonically through a
56-
series of states: assigned, prepared, running, etc. If the task fails, the
56+
series of states: `ASSIGNED`, `PREPARING`, `RUNNING`, etc. If the task fails, the
5757
orchestrator removes the task and its container and then creates a new task to
5858
replace it according to the desired state specified by the service.
5959

0 commit comments

Comments
 (0)