Skip to content

Commit f39fc39

Browse files
authored
Update chaining-tasks-by-using-continuation-tasks.md (dotnet#23618)
Fixed typo.
1 parent 01bab68 commit f39fc39

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/standard/parallel-programming/chaining-tasks-by-using-continuation-tasks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.assetid: 0b45e9a2-de28-46ce-8212-1817280ed42d
1212

1313
# Chaining tasks using continuation tasks
1414

15-
In asynchronous programming, it's common for one asynchronous operation, on completion, to invoke a second operation. Continuations allow decedent operations to consume the results of the first operation. Traditionally, continuations have been done by using callback methods. In the Task Parallel Library, the same functionality is provided by _continuation tasks_. A continuation task (also known just as a continuation) is an asynchronous task that's invoked by another task, known as the _antecedent_, when the antecedent finishes.
15+
In asynchronous programming, it's common for one asynchronous operation, on completion, to invoke a second operation. Continuations allow descendant operations to consume the results of the first operation. Traditionally, continuations have been done by using callback methods. In the Task Parallel Library, the same functionality is provided by _continuation tasks_. A continuation task (also known just as a continuation) is an asynchronous task that's invoked by another task, known as the _antecedent_, when the antecedent finishes.
1616

1717
Continuations are relatively easy to use, but are nevertheless powerful and flexible. For example, you can:
1818

0 commit comments

Comments
 (0)