Skip to content

Commit ae49bd1

Browse files
committed
Remove duplicate text in Terminology
1 parent ea7eaa8 commit ae49bd1

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

articles/azure-functions/durable/durable-functions-orchestration-versioning.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,6 @@ This article uses two related but distinct terms:
2424
- **Orchestration instance** (or simply "orchestration"): Refers to a specific running execution of an orchestrator function, with its own state, instance ID, and inputs. Multiple orchestration instances can run concurrently from the same orchestrator function.
2525

2626
Understanding this distinction is crucial for orchestration versioning, where the orchestrator function code contains version-aware logic, while orchestration instances are permanently associated with a specific version when created.
27-
> - **Orchestrator function** (or simply "orchestrator"): Refers to the function code that defines the workflow logic - the template or blueprint for how a workflow should execute.
28-
> - **Orchestration instance** (or simply "orchestration"): Refers to a specific running execution of an orchestrator function, with its own state, instance ID, and inputs. Multiple orchestration instances can run concurrently from the same orchestrator function.
29-
>
30-
> Understanding this distinction is crucial for orchestration versioning, where the orchestrator function code contains version-aware logic, while orchestration instances are permanently associated with a specific version when created.
3127

3228
### Key benefits
3329

0 commit comments

Comments
 (0)