You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorials/nservicebus-sagas/index.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ How do we create a delay so that we can trigger an action at some point in the f
19
19
For these types of scenarios, you need a *stateful* message handler. Other ways to describe what is needed might include a message-driven state machine or an orchestration engine.
20
20
In NServiceBus, we call these [**Sagas**](/nservicebus/sagas/). In this tutorial, we'll build on the solution from the [NServiceBus Step-by-step tutorial](/tutorials/nservicebus-step-by-step/) and learn to master NServiceBus Sagas.
21
21
22
-
This lessons make the most sense when tackled in order, but it's not required.
22
+
These lessons make the most sense when tackled in order, but it's not required.
23
23
24
24
1.[**Saga basics**](1-saga-basics/) (20-25 minutes) - learn how to introduce Sagas to complete the order shipping process.
25
25
1.[**Timeouts**](2-timeouts/) (20-25 minutes) - learn how to delay processing of an order to implement the *buyer's remorse* pattern.
0 commit comments