Skip to content

Commit edd923e

Browse files
Hyperlint Automation Fix
1 parent ecce2a9 commit edd923e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/content/docs/agents/api-reference/run-workflows.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Because an Agent is just like a Worker script, it can create Workflows defined i
1616

1717
Agents and Workflows have some similarities: they can both run tasks asynchronously. For straightforward tasks that are linear or need to run to completion, a Workflow can be ideal: steps can be retried, they can be cancelled, and can act on events.
1818

19-
Agents do not have to run to completion: they can loop, branch and run forever, and they can also interact directly with users (over HTTP or WebSockets). An Agent can be used to trigger multiple Workflows as it runs, and can thus be used to co-ordinate and manage Workflows to achieve its goals.
19+
Agents do not have to run to completion: they can loop, branch and run forever, and they can also interact directly with users (over HTTP or WebSocket). An Agent can be used to trigger multiple Workflows as it runs, and can thus be used to co-ordinate and manage Workflows to achieve its goals.
2020

2121
:::
2222

@@ -97,7 +97,7 @@ You can also call a Workflow that is defined in a different Workers script from
9797
// Required:
9898
"name": "EMAIL_WORKFLOW",
9999
"class_name": "MyWorkflow",
100-
// Optional: set tthe script_name field if your Workflow is defined in a
100+
// Optional: set the script_name field if your Workflow is defined in a
101101
// different project from your Agent
102102
"script_name": "email-workflows"
103103
}

0 commit comments

Comments
 (0)