docs(shell-docs): wording pass — replace 'showcase cell' references with generic phrasing

samjulien · samjulien · commit 157cdae57477 · 2026-04-23T12:12:32.000-07:00
diff --git a/showcase/shell-docs/src/content/ag-ui/quickstart/clients.mdx b/showcase/shell-docs/src/content/ag-ui/quickstart/clients.mdx
@@ -1,6 +1,6 @@
 ---
 title: "Build clients"
-description: "Showcase: build a conversational CLI agent from scratch using AG-UI and Mastra"
+description: "Build a conversational CLI agent from scratch using AG-UI and Mastra"
 ---
 
 # Introduction
diff --git a/showcase/shell-docs/src/content/docs/agentic-chat-ui.mdx b/showcase/shell-docs/src/content/docs/agentic-chat-ui.mdx
@@ -30,7 +30,7 @@ The live `agentic-chat` cell above is built from a single, small page. Wrap your
 <Snippet region="provider-setup" title="frontend/src/app/page.tsx — CopilotKit provider" />
 
 Inside the chat, the `useConfigureSuggestions` hook lets you show contextual
-starter prompts. The showcase cell uses it to seed a simple "Write a sonnet"
+starter prompts. The example below uses it to seed a simple "Write a sonnet"
 suggestion:
 
 <Snippet region="configure-suggestions" title="frontend/src/app/page.tsx — starter suggestions" />
diff --git a/showcase/shell-docs/src/content/docs/backend/ag-ui.mdx b/showcase/shell-docs/src/content/docs/backend/ag-ui.mdx
@@ -116,7 +116,7 @@ This indirection is what enables the runtime to provide authentication, middlewa
 
 On the server side, the `CopilotRuntime` accepts a map of AG-UI `AbstractAgent` instances. Each agent framework provides its own implementation, but they all extend the same base type.
 
-Here's a real example from the `langgraph-python` showcase integration — registering a `LangGraphAgent` (which is an `AbstractAgent`) under multiple agent IDs that all share the same backend graph:
+Here's a real example from the `langgraph-python` integration — registering a `LangGraphAgent` (which is an `AbstractAgent`) under multiple agent IDs that all share the same backend graph:
 
 ```ts title="app/api/copilotkit/route.ts"
 import {
diff --git a/showcase/shell-docs/src/content/docs/custom-look-and-feel/reasoning-messages.mdx b/showcase/shell-docs/src/content/docs/custom-look-and-feel/reasoning-messages.mdx
@@ -162,10 +162,10 @@ slot props. Your component receives the same top-level props as the built-in one
 
 <InlineDemo demo="agentic-chat-reasoning" />
 
-The showcase's `ReasoningBlock` renders the reasoning as an amber-tagged inline
-banner, intentionally louder than the default card so the thinking chain is
-the focal UI of the demo. Swap in your own component to match your product's
-tone:
+The `ReasoningBlock` used above renders the reasoning as an amber-tagged
+inline banner, intentionally louder than the default card so the thinking
+chain is the focal UI of the demo. Swap in your own component to match
+your product's tone:
 
 <Snippet region="reasoning-block-render" title="frontend/src/app/page.tsx — custom reasoning slot" />
 
diff --git a/showcase/shell-docs/src/content/docs/generative-ui/a2ui.mdx b/showcase/shell-docs/src/content/docs/generative-ui/a2ui.mdx
@@ -19,17 +19,15 @@ You can design and preview A2UI schemas visually using the
 
 ## The two approaches
 
-CopilotKit's showcase ships two complementary A2UI cells:
+CopilotKit ships two complementary A2UI approaches:
 
 - **[Dynamic Schema](./a2ui/dynamic-schema)** — a secondary LLM
   generates both the schema *and* the data. Maximum flexibility —
-  the agent can produce any UI for any prompt. Backed by the
-  `declarative-gen-ui` cell.
+  the agent can produce any UI for any prompt.
 
 - **[Fixed Schema](./a2ui/fixed-schema)** — the component tree is
   authored ahead of time as JSON. The agent only streams *data* into
   the data model at runtime. Fastest — no LLM schema generation.
-  Backed by the `a2ui-fixed-schema` cell.
 
 Both approaches share the same A2UI wire protocol and the same
 frontend renderer. The difference is *where the schema comes from* and
diff --git a/showcase/shell-docs/src/content/docs/generative-ui/a2ui/dynamic-schema.mdx b/showcase/shell-docs/src/content/docs/generative-ui/a2ui/dynamic-schema.mdx
@@ -41,8 +41,8 @@ side-by-side under `frontend/src/app/a2ui/`:
 
 Each entry pairs a Zod prop schema with a description. The description
 is crucial; the LLM reads it to decide which component to emit. The
-showcase's `declarative-gen-ui` cell ships a small dashboard catalog
-(Card / StatusBadge / Metric / InfoRow / PrimaryButton):
+example below ships a small dashboard catalog (Card / StatusBadge /
+Metric / InfoRow / PrimaryButton):
 
 <Snippet region="definitions-zod" />
 </Step>
diff --git a/showcase/shell-docs/src/content/docs/generative-ui/a2ui/fixed-schema.mdx b/showcase/shell-docs/src/content/docs/generative-ui/a2ui/fixed-schema.mdx
@@ -30,9 +30,8 @@ Ask about a flight and the agent renders a fully structured card from a pre-defi
 
 ## Schemas as JSON: compositional trees
 
-The showcase's `a2ui-fixed-schema` cell ships a flight card assembled
-compositionally from small sub-components rather than one monolithic
-`FlightCard`:
+The example below ships a flight card assembled compositionally from
+small sub-components rather than one monolithic `FlightCard`:
 
 ```
 Card
diff --git a/showcase/shell-docs/src/content/docs/generative-ui/reasoning.mdx b/showcase/shell-docs/src/content/docs/generative-ui/reasoning.mdx
@@ -64,8 +64,8 @@ still streaming and whether it's the active trailing message:
 
 <Snippet region="reasoning-block-render" title="frontend/src/app/page.tsx — custom reasoning slot" />
 
-The showcase's `ReasoningBlock` (imported above) renders the reasoning as
-an amber-tagged inline banner, intentionally louder than the default card
+The `ReasoningBlock` (imported above) renders the reasoning as an
+amber-tagged inline banner, intentionally louder than the default card
 so the thinking chain is the focal UI of the demo. Swap in your own
 component to match your product's tone.
 
diff --git a/showcase/shell-docs/src/content/docs/generative-ui/tool-based.mdx b/showcase/shell-docs/src/content/docs/generative-ui/tool-based.mdx
@@ -44,7 +44,7 @@ component.
 <Snippet region="bar-chart-renderer" title="frontend/src/app/page.tsx — bar chart component" />
 
 The component itself is ordinary React: it reads only its props and can
-stream in as the agent fills the payload. The showcase cell uses
+stream in as the agent fills the payload. The example above uses
 [Recharts](https://recharts.org) for the bar chart; it doesn't know
 anything about CopilotKit.
 
diff --git a/showcase/shell-docs/src/content/docs/human-in-the-loop/headless.mdx b/showcase/shell-docs/src/content/docs/human-in-the-loop/headless.mdx
@@ -69,7 +69,7 @@ A few things this hook is careful about:
 ## Driving it from plain UI
 
 Once `useHeadlessInterrupt` returns `{ pending, resolve }`, the rest is
-just React. The showcase cell uses two buttons to kick off the agent
+just React. The example below uses two buttons to kick off the agent
 and a button grid to resolve, with no `<CopilotChat>` and no render prop:
 
 ```tsx
diff --git a/showcase/shell-docs/src/content/docs/human-in-the-loop/useInterrupt.mdx b/showcase/shell-docs/src/content/docs/human-in-the-loop/useInterrupt.mdx
@@ -36,8 +36,8 @@ the user, prefer [`useHumanInTheLoop`](../human-in-the-loop).
 
 ## The backend: `interrupt()` inside a tool
 
-The showcase `gen-ui-interrupt` cell exposes a `schedule_meeting` tool.
-When the model calls it, the tool issues a `langgraph.interrupt(...)`
+The example agent exposes a `schedule_meeting` tool. When the model
+calls it, the tool issues a `langgraph.interrupt(...)`
 with the meeting context. The run freezes here until the client
 resolves; the resolution becomes the return value of `interrupt()`,
 which the tool then turns into a final string for the model:
diff --git a/showcase/shell-docs/src/content/docs/integrations/langgraph/generative-ui/tool-rendering.mdx b/showcase/shell-docs/src/content/docs/integrations/langgraph/generative-ui/tool-rendering.mdx
@@ -47,8 +47,8 @@ when your agent is calling tools. CopilotKit allows you to fully customize how t
 <Step>
 ### Give your agent a tool to call
 
-The agent in the live showcase exposes a mock `get_weather` tool. This is the
-definition straight from the `tool-rendering` cell's Python backend:
+The agent in the live demo above exposes a mock `get_weather` tool. This is
+the definition straight from the Python backend:
 
 <Snippet region="weather-tool-backend" />
 
@@ -65,9 +65,9 @@ the UI.
   tool.
 </Callout>
 
-The showcase's `tool-rendering` cell uses a branded `<WeatherCard />`
-component to render the call — same pattern as the minimal example above,
-just wired to a richer UI:
+The example below uses a branded `<WeatherCard />` component to render
+the call — same pattern as the minimal example above, just wired to a
+richer UI:
 
 <Snippet region="render-weather-tool" />
 
@@ -76,9 +76,9 @@ just wired to a richer UI:
 ### Add a catch-all renderer (optional)
 
 For every other tool the agent calls, a single `useDefaultRenderTool`
-hook can provide a uniform fallback UI — this is exactly how the showcase
-handles `get_stock_price`, `roll_dice`, and any tool the agent might add
-later without a dedicated renderer:
+hook can provide a uniform fallback UI — this is exactly how the demo
+above handles `get_stock_price`, `roll_dice`, and any tool the agent might
+add later without a dedicated renderer:
 
 <Snippet region="catchall-renderer" />
 
diff --git a/showcase/shell-docs/src/content/docs/multi-agent/subagents.mdx b/showcase/shell-docs/src/content/docs/multi-agent/subagents.mdx
@@ -32,7 +32,7 @@ that each benefit from their own focus:
 - **Divide-and-conquer** — any problem that fits cleanly into parallel
   or sequential sub-problems.
 
-The showcase cell uses the Research → Write → Critique shape as the
+The example below uses the Research → Write → Critique shape as the
 canonical example.
 
 ## Setting up sub-agents
diff --git a/showcase/shell-docs/src/content/docs/prebuilt-components/index.mdx b/showcase/shell-docs/src/content/docs/prebuilt-components/index.mdx
@@ -79,7 +79,7 @@ the agent registry. Everything else is optional configuration:
 ## Starter suggestions
 
 `useConfigureSuggestions` lets you seed the chat with contextual
-prompts the moment a user arrives. The showcase cell uses a single
+prompts the moment a user arrives. The example below uses a single
 "Write a sonnet" suggestion:
 
 <Snippet region="configure-suggestions" title="frontend/src/app/page.tsx — suggestions" />
diff --git a/showcase/shell-docs/src/content/docs/prebuilt-components/popup.mdx b/showcase/shell-docs/src/content/docs/prebuilt-components/popup.mdx
@@ -41,7 +41,7 @@ The gif below shows the popup launcher toggling open over page content:
 
 Wrap your app in `<CopilotKit>` once (the provider wires the runtime,
 session, and agent registry) and render `<CopilotPopup>` as a sibling of
-your main content. The showcase cell opens the popup by default and
+your main content. The example below opens the popup by default and
 customizes the input placeholder via `labels`:
 
 <Snippet region="popup-basic-setup" title="frontend/src/app/page.tsx — CopilotPopup wired up" />
diff --git a/showcase/shell-docs/src/content/docs/prebuilt-components/sidebar.mdx b/showcase/shell-docs/src/content/docs/prebuilt-components/sidebar.mdx
@@ -47,7 +47,7 @@ your page:
 ## Configuring the sidebar
 
 `<CopilotSidebar>` accepts the same props as `<CopilotChat>` plus a few of
-its own. The showcase cell opens the sidebar by default and targets a named
+its own. The example below opens the sidebar by default and targets a named
 agent:
 
 <Snippet region="sidebar-configuration" title="frontend/src/app/page.tsx — defaultOpen + agentId" />
diff --git a/showcase/shell-docs/src/content/docs/shared-state.mdx b/showcase/shell-docs/src/content/docs/shared-state.mdx
@@ -39,9 +39,8 @@ slices:
 - An **agent-written** slice (e.g. notes, a document, a plan) that the
   UI renders in real time as the agent produces it.
 
-The `shared-state-read-write` showcase cell wires both sides against a
-single `AgentState` schema with `preferences` (UI-written) and `notes`
-(agent-written).
+The example below wires both sides against a single `AgentState`
+schema with `preferences` (UI-written) and `notes` (agent-written).
 
 ## Reading agent state
 
diff --git a/showcase/shell-docs/src/content/docs/unselected/generative-ui/your-components/display-only.mdx b/showcase/shell-docs/src/content/docs/unselected/generative-ui/your-components/display-only.mdx
@@ -32,7 +32,7 @@ For components that need user interaction, see [Interactive Components](./intera
 
 <Snippet region="pie-chart-renderer" title="frontend/src/app/page.tsx — pie chart component" />
 
-The component itself is ordinary React — it reads only its props and can stream in as the agent fills the payload. The showcase cell uses [Recharts](https://recharts.org) for the bar chart and a hand-rolled SVG donut for the pie chart; neither knows anything about CopilotKit.
+The component itself is ordinary React — it reads only its props and can stream in as the agent fills the payload. The example above uses [Recharts](https://recharts.org) for the bar chart and a hand-rolled SVG donut for the pie chart; neither knows anything about CopilotKit.
 
 <Callout type="info">
 The `name` you pass to `useComponent` is what the agent sees as the tool name. Make it a verb like `render_bar_chart` or `show_weather` so the LLM reliably picks it when the user asks for that visualization.
diff --git a/showcase/shell-docs/src/content/docs/unselected/prebuilt-components/index.mdx b/showcase/shell-docs/src/content/docs/unselected/prebuilt-components/index.mdx
@@ -43,7 +43,7 @@ Wrap your app in `<CopilotKit>` and drop `<CopilotChat>` where the chat should l
 
 ## Starter suggestions
 
-`useConfigureSuggestions` lets you seed the chat with contextual prompts the moment a user arrives. The showcase cell uses a single "Write a sonnet" suggestion:
+`useConfigureSuggestions` lets you seed the chat with contextual prompts the moment a user arrives. The example below uses a single "Write a sonnet" suggestion:
 
 <Snippet region="configure-suggestions" title="frontend/src/app/page.tsx — suggestions" />
 
diff --git a/showcase/shell-docs/src/content/docs/unselected/prebuilt-components/popup.mdx b/showcase/shell-docs/src/content/docs/unselected/prebuilt-components/popup.mdx
@@ -40,7 +40,7 @@ The gif below shows the popup launcher toggling open over page content:
 
 Wrap your app in `<CopilotKit>` once — the provider wires the runtime,
 session, and agent registry — then render `<CopilotPopup>` as a sibling of
-your main content. The showcase cell opens the popup by default and
+your main content. The example below opens the popup by default and
 customizes the input placeholder via `labels`:
 
 <Snippet region="popup-basic-setup" title="frontend/src/app/page.tsx — CopilotPopup wired up" />
diff --git a/showcase/shell-docs/src/content/docs/unselected/prebuilt-components/sidebar.mdx b/showcase/shell-docs/src/content/docs/unselected/prebuilt-components/sidebar.mdx
@@ -48,7 +48,7 @@ your page:
 ## Configuring the sidebar
 
 `<CopilotSidebar>` accepts the same props as `<CopilotChat>` plus a few of
-its own. The showcase cell opens the sidebar by default and targets a named
+its own. The example below opens the sidebar by default and targets a named
 agent:
 
 <Snippet region="sidebar-configuration" title="frontend/src/app/page.tsx — defaultOpen + agentId" />
