fix(broker): add conceptual intro, use case, and naming clarification (#384)

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Joyce Fee <102751339+Feediver1@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: prakhargarg105 <prakhar.garg@redpanda.com>
Co-authored-by: vbotbuildovich <62446873+vbotbuildovich@users.noreply.github.com>
Co-authored-by: JakeSCahill <45230295+JakeSCahill@users.noreply.github.com>
Co-authored-by: Joyce Fee <joyce@redpanda.com>
Co-authored-by: micheleRP <michele@redpanda.com>

Author: 8 people

.gitignore

@@ -1,3 +1,4 @@
+memory/
 node_modules
 .vscode
 docs

modules/components/pages/outputs/broker.adoc

@@ -10,8 +10,11 @@
 component_type_dropdown::[]
 
 
-Allows you to route messages to multiple child outputs using a range of brokering <<patterns>>.
+A meta-output that routes messages to child outputs using a range of brokering <<patterns,patterns>>. Unlike regular outputs, `broker` doesn't send messages anywhere by itself. Instead, it wraps other outputs and controls how messages are delivered across them.
 
+Use `broker` to fan out the same message to multiple destinations (for example, publishing events to Kafka while also writing them to a database), or to distribute messages across a pool of outputs for load balancing or throughput scaling. The delivery pattern determines whether each message is written to all outputs or routed to a single output, and whether writes happen in parallel or in sequence.
+
+NOTE: The name `broker` refers to the brokering delivery pattern, not a Redpanda broker (cluster node).
 
 [tabs]
 ======
@@ -57,7 +60,9 @@ include::redpanda-connect:components:partial$fields/outputs/broker.adoc[]
 
 == Patterns
 
-The broker pattern determines the way in which messages are allocated and can be chosen from the following:
+The broker pattern determines how messages are distributed across outputs. Use `fan_out` (the default) when every output should receive every message. Use `round_robin` or `greedy` when you want to distribute messages across outputs for load balancing rather than duplication.
+
+The available patterns are:
 
 === `fan_out`