fix: fix docs

Author: zhuravlevma

README.md

@@ -70,7 +70,11 @@ In a good way, each bounded context in a micro-service architecture should have
 ### Saga
 
 The project uses a saga with choreography and a registrar. The registrar is capable of rolling back transactions in case of failure.
+
+Calling for compensation
 ![image](https://github.com/user-attachments/assets/334c00b2-9bda-4552-be61-76b2771ee938)
+
+Timeout compensation
 ![image](https://github.com/user-attachments/assets/6e25acc7-46b5-4ae6-972b-fd9fd164d687)
 
 ### Important

docs/SAGA.puml

@@ -17,11 +17,9 @@ ServiceA -> ServiceA: run second step
 ServiceA --> Registrator: run third step, send second step compensation
 ServiceA --> ServiceB: run third step
 
+ServiceB -> ServiceB: run third step
 
-ServiceB -[#red]> ServiceB: run third step (ERROR)
-
-
-Registrator -> Registrator: third step timeout (12 hours), send compensations
+ServiceB --> Registrator: run compensations by sagaId
 
 Registrator --> ServiceA: Compensation for second step
 Registrator --> Service: Compensation for first step

docs/SAGA_TIMEOUT.puml

@@ -0,0 +1,27 @@
+@startuml saga
+title Choreographic Saga with a Registrator
+
+participant "Service" as Service
+
+participant "ServiceA" as ServiceA
+participant "ServiceB" as ServiceB
+participant "Registrator" as Registrator
+
+Service -> Registrator: run new saga
+Registrator --> Service: return SagaId
+Service -> Service: run first step
+Service --> Registrator: run second step, send first step compensation
+Service --> ServiceA: run second step
+
+ServiceA -> ServiceA: run second step
+ServiceA --> Registrator: run third step, send second step compensation
+ServiceA --> ServiceB: run third step
+
+
+ServiceB -[#red]> ServiceB: run third step (ERROR)
+
+
+Registrator -> Registrator: third step timeout (12 hours), send compensations
+
+Registrator --> ServiceA: Compensation for second step
+Registrator --> Service: Compensation for first step