Skip to content

Fix verb form in Workflows page #4140

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
flippedcoder merged 1 commit into from
Feb 4, 2026
Merged

Fix verb form in Workflows page #4140

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/encyclopedia/workflow/workflow-overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,9 +43,9 @@ You'll develop those Workflows by writing code in a general-purpose programming
or Python. The code you write is the same code that will be executed at runtime, so you can use your favorite tools and
libraries to develop Temporal Workflows.

Temporal Workflows are resilient. They can run—and keep running—for years, even if the underlying infrastructure fails.
If the application itself crashes, Temporal will automatically recreate its pre-failure state so it can continue right
where it left off.
Temporal Workflows are resilient.
They can run—and keep running—for years, even if the underlying infrastructure fails.
If the application itself crashes, Temporal will automatically recreate its pre-failure state so it can continue right where it left off.

Each Workflow Execution progresses through a series of **Commands** and **Events**, which are recorded in an **Event
History**.
Expand Down