From 2412e1f665bba7d6f53474f01cbac1445c5f0eec Mon Sep 17 00:00:00 2001 From: Haomin Shi Date: Mon, 12 Jun 2023 13:24:58 -0400 Subject: [PATCH] fixed: incorrect class name for workflow parent --- docs/userguide/concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/userguide/concepts.md b/docs/userguide/concepts.md index 3a776cb05..d81db0c5d 100644 --- a/docs/userguide/concepts.md +++ b/docs/userguide/concepts.md @@ -76,7 +76,7 @@ When that is called, `EmailInboxWorkflow` enqueues an Action function that emits ![Workflow schematic showing EmailBrowserWorkflow rendering by delegating to two children, InboxWorkflow and MessageWorkflow, and assembling their renderings into its own.](../images/split_screen_update.svg) Whenever such a [Workflow Action cascade](../../glossary#action-cascade) fires, the root Workflow is asked for a new Rendering. -Just as before, `EmailInboxWorkflow` delegates to its two children for their Renderings, this time providing the new value of `selection` as the updated Props for `MessageWorkflow`. +Just as before, `EmailBrowserWorkflow` delegates to its two children for their Renderings, this time providing the new value of `selection` as the updated Props for `MessageWorkflow`.