Update tutorials/nservicebus-sagas/3-integration/tutorial.md

tamararivera · helenktsai · web-flow · commit da21eb4974d6 · 2024-10-03T12:31:42.000-07:00
Co-authored-by: Helen T &lt;35390871+helenktsai@users.noreply.github.com&gt;
diff --git a/tutorials/nservicebus-sagas/3-integration/tutorial.md b/tutorials/nservicebus-sagas/3-integration/tutorial.md
@@ -26,7 +26,7 @@ In the exercises so far, we had a `ShippingPolicy` saga that was rather passive
 >
 > downloadbutton(Download Previous Solution, /tutorials/nservicebus-sagas/2-timeouts)
 >
-> The solution contains 5 projects. The **ClientUI**, **Sales**, **Billing**, and **Shipping** projects define endpoints that communicate with each other using messages. The **ClientUI** endpoint mimics a web application and is an entry point to the system.
+> The solution contains 5 projects. The **ClientUI**, **Sales**, **Billing**, and **Shipping** projects define endpoints that communicate with each other using messages. The **ClientUI** endpoint mimics a web application and is the entry point to the system.
 > **Sales**, **Billing**, and **Shipping** contain business logic related to processing, fulfilling, and shipping orders. Each endpoint references the **Messages** assembly, which contains the classes that define the messages exchanged in our system.
 > To see how to start building this system from scratch, check out the [NServiceBus step-by-step tutorial](/tutorials/nservicebus-step-by-step/).
 >

Original file line number	Diff line number	Diff line change
@@ -26,7 +26,7 @@ In the exercises so far, we had a `ShippingPolicy` saga that was rather passive
`26`	`26`	`>`
`27`	`27`	`> downloadbutton(Download Previous Solution, /tutorials/nservicebus-sagas/2-timeouts)`
`28`	`28`	`>`
`29`		`-> The solution contains 5 projects. The ClientUI, Sales, Billing, and Shipping projects define endpoints that communicate with each other using messages. The ClientUI endpoint mimics a web application and is an entry point to the system.`
	`29`	`+> The solution contains 5 projects. The ClientUI, Sales, Billing, and Shipping projects define endpoints that communicate with each other using messages. The ClientUI endpoint mimics a web application and is the entry point to the system.`
`30`	`30`	`> Sales, Billing, and Shipping contain business logic related to processing, fulfilling, and shipping orders. Each endpoint references the Messages assembly, which contains the classes that define the messages exchanged in our system.`
`31`	`31`	`> To see how to start building this system from scratch, check out the [NServiceBus step-by-step tutorial](/tutorials/nservicebus-step-by-step/).`
`32`	`32`	`>`