From 6f2bf282bb03d006f1a1efe838fe4048286432e3 Mon Sep 17 00:00:00 2001 From: Bilgin Ibryam Date: Thu, 11 Sep 2025 16:45:01 +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 d8a67fef6..1494399e1 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 @@ -26,7 +26,7 @@ The diagram below is an overview of how the outbox feature works at a high level ## How outbox works under the hood -Dapr Outbox processes requests in two flows: the user request flow and the background message flow. Together, they guarantee that state and events stay consistent. +Dapr outbox processes requests in two flows: the user request flow and the background message flow. Together, they guarantee that state and events stay consistent. Diagram showing the steps of the outbox pattern