From 8bc499d18d7c325e941c11e3de66e4b5f0639215 Mon Sep 17 00:00:00 2001 From: Bilgin Ibryam Date: Thu, 11 Sep 2025 16:45:09 +0100 Subject: [PATCH] Update daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md Co-authored-by: Mark Fussell Signed-off-by: Bilgin Ibryam --- .../building-blocks/state-management/howto-outbox.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md b/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md index 1494399e1..aa818f437 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md +++ b/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-outbox.md @@ -30,7 +30,7 @@ Dapr outbox processes requests in two flows: the user request flow and the backg Diagram showing the steps of the outbox pattern -Here is the full sequence of interactions: +This is the sequence of interactions: 1. Application calls the Dapr State API to write state transactionally. This is the entry point where business data, such as an order or profile update, is submitted for persistence.