Update README.md

olahallvall · Apr 25, 2024 · ae6f1dc · ae6f1dc
1 parent c0b8bd5
commit ae6f1dc
Showing 1 changed file with 2 additions and 3 deletions.
diff --git a/README.md b/README.md
@@ -32,9 +32,8 @@ The solution employs a microservices architecture, where each component (car, ho
 
 ![Synchronous choreography-based call chains](Docs/synchronous-choreography-based-call-chains.png)
 
-So how does FlowDance help us out when we have to base our solution on synchronous RPC-Calls?   
-Remember that FlowDance wants to support communication between microservices based on synchronous RPC-calls. 
-Event-driven architecture is out of scoop here.
+So how does FlowDance help us out when we still want to base our solution on synchronous RPC-Calls but leaving MSDTC behind?
+Remember that FlowDance wants to support communication between microservices based on synchronous RPC-calls. Event-driven architecture is out of scoop here.
 
 In short - by replacing **System.Transactions.TransactionScope** with **FlowDance.Client.CompensationSpan** you leaves the world of strong consistency into eventual consistency.