diff --git a/docs/references/agent_component_reference/concentrator.mdx b/docs/references/agent_component_reference/concentrator.mdx
index e69de29bb..fbc24695a 100644
--- a/docs/references/agent_component_reference/concentrator.mdx
+++ b/docs/references/agent_component_reference/concentrator.mdx
@@ -0,0 +1,26 @@
+---
+sidebar_position: 10
+slug: /concentrator_component
+---
+
+# Concentrator component
+
+A component that directs execution flow to multiple downstream components.
+
+---
+
+The **Concentrator** component acts as a "repeater" of execution flow, transmitting a flow to multiple downstream components.
+
+
+## Scenarios
+
+A **Concentrator** component enhances the current UX design. For a component originally designed to support only one downstream component, you can append a **Concentrator**, enabling it to have multiple downstream components.
+
+## Examples
+
+Explore our general-purpose chatbot agent template, featuring a **Concentrator** component (component ID: **medical**) that relays an execution flow from category 2 of the **Categorize** component to the two translator components:
+
+1. Click the **Agent** tab at the top center of the page to access the **Agent** page.
+2. Click **+ Create agent** on the top right of the page to open the **agent template** page.
+3. On the **agent template** page, hover over the **General-purpose chatbot** card and click **Use this template**.
+4. Name your new agent and click **OK** to enter the workflow editor.
\ No newline at end of file
diff --git a/docs/references/agent_component_reference/switch.mdx b/docs/references/agent_component_reference/switch.mdx
index f2f709e37..085f35bf0 100644
--- a/docs/references/agent_component_reference/switch.mdx
+++ b/docs/references/agent_component_reference/switch.mdx
@@ -19,7 +19,7 @@ A **Switch** component is essential for condition-based direction of execution f
 
 ### Case n
 
-A **Switch** component must have at least one case, each with multiple specified conditions and corresponding downstream components. When multiple conditions are specified for a case, you must set the logical relationship between them to either AND or OR.
+A **Switch** component must have at least one case, each with multiple specified conditions and *only one* downstream component. When multiple conditions are specified for a case, you must set the logical relationship between them to either AND or OR.
 
 #### Next step