diff --git a/content/docs/build/automation/flows.mdx b/content/docs/build/automation/flows.mdx
index d7d967e..3e047e5 100644
--- a/content/docs/build/automation/flows.mdx
+++ b/content/docs/build/automation/flows.mdx
@@ -6,7 +6,7 @@ description: Declarative business logic — described to AI or written in TypeSc
 Flows are how you express business logic without writing a server.
 Every flow is declarative metadata that the runtime executes — same
 as objects and views. That means flows show up in `os diff`, the
-audit log, the flow builder, and the [AI Builder](/docs/build/ai-builder)
+audit log, Studio's flow builder, and the [AI Builder](/docs/build/ai-builder)
 all at once.
 
 Most customers create flows by asking the AI:
@@ -278,7 +278,8 @@ auditable in the flow builder.
 
 ObjectOS ships a visual flow builder that round-trips with the
 declarative metadata — non-engineers can edit a flow, and it serializes
-back to the same shape as the TypeScript you'd hand-author.
+back to the same shape as the TypeScript you'd hand-author. It is
+Studio's **Automations** pillar.
 
 ## Testing flows
 
diff --git a/content/docs/build/index.mdx b/content/docs/build/index.mdx
index 5dee113..3d84c73 100644
--- a/content/docs/build/index.mdx
+++ b/content/docs/build/index.mdx
@@ -1,6 +1,6 @@
 ---
 title: Build
-description: How apps come to life in ObjectOS — by chatting with AI, by clicking through forms, or by forking a template.
+description: How apps come to life in ObjectOS — by chatting with AI, by clicking through forms in Studio, or by forking a template.
 ---
 
 In ObjectOS the customer doesn't write metadata. **They describe what
@@ -10,7 +10,7 @@ most people actually use the platform:
 | Path | Who's it for | Output |
 |---|---|---|
 | **[AI Builder](/docs/build/ai-builder)** (primary) | Business users, product owners, anyone | Live metadata in your tenant, queued for approval |
-| **Click-build** (fallback) | Admins who prefer forms | The same live metadata |
+| **Click-build** (fallback) | Admins who prefer Studio's forms | The same live metadata |
 | **[Template fork](/docs/build/templates)** (dev path) | Engineers who want code under source control | A TypeScript package shipped via the marketplace |
 
 All three paths produce **the same artifact shape** — packages of
@@ -49,7 +49,7 @@ Every app is composed from the same primitives. Learn these once.
 ## What you'll never have to do
 
 - Write a REST endpoint. The platform generates one per object.
-- Wire a form. The form renders from the schema.
+- Wire a Studio form. The form renders from the schema.
 - Write RBAC checks. Permissions are declared, not coded.
 - Build an admin UI. Setup and Account cover system administration and sign-in.
 - Generate types. `@objectstack/spec` derives them from the schema.