@@ -1,7 +1,7 @@
 ---
 title: Custom endpoints declared as metadata
 navTitle: Declarative Endpoints
-description: "Expose your app to systems outside the platform by declaring an apis: endpoint as metadata — which channel to pick, the four publish gates, and the obligation that comes with an anonymous endpoint."
+description: "Expose your app to outside systems by declaring an apis: endpoint as metadata — pick the channel, pass the four publish gates, secure anonymous calls."
 ---
 
 A stack can publish an HTTP endpoint as **metadata** instead of writing a handler: a URL,
 
@@ -1,7 +1,7 @@
 ---
 title: Plugin endpoints — add routes from a plugin
 navTitle: Plugin Endpoints
-description: REST endpoints that become available when the corresponding plugin is installed — auth, workflow, automation, views, realtime, notifications, AI, i18n, and file storage.
+description: REST endpoints each installed plugin adds — auth, workflow, automation, views, realtime, notifications, AI, i18n and files — and how to discover them.
 ---
 
 These REST endpoints are only available when the corresponding plugin is installed. Check the [discovery manifest](/docs/api#discovery) `services` map before calling them; all paths are relative to the base URL (defaults to `/api/v1`).
 
@@ -1,7 +1,7 @@
 ---
 title: Approval chains — multi-step sign-off rules
 navTitle: Approval workflow
-description: Route a record for sign-off — who can configure the automation, and the run-identity decision that keeps an approval flow from quietly bypassing row-level security.
+description: Route a record for sign-off with an approval flow — who may configure it, and the run-identity choice that keeps it from bypassing row-level security.
 ---
 
 ## Scenario
 
@@ -1,7 +1,7 @@
 ---
 title: Connectors — call external systems safely
 navTitle: Connectors
-description: Call external systems from flows — plugin-registered connectors, and declarative provider-bound instances (rest / openapi / mcp) authored as pure metadata with reference-based credentials.
+description: Call external systems from flows with plugin connectors or declarative rest, openapi and mcp instances — pure metadata with reference-based credentials.
 ---
 
 > **Status:** Shipped · **Audience:** App authors (human and AI), integration
 
@@ -1,7 +1,7 @@
 ---
 title: What can it do? — the capability overview
 navTitle: What Can It Do?
-description: The platform's capabilities in business language — data, views, automation, approvals, permissions, analytics, AI, integrations — each with a real CRM as the running example
+description: What the platform can do, in business language — data, views, automation, approvals, permissions, analytics, AI and integrations, shown on a real CRM.
 ---
 
 
 
@@ -1,7 +1,7 @@
 ---
 title: Metadata lifecycle — load, publish and HMR
 navTitle: Metadata Lifecycle & HMR
-description: How metadata flows through Repository → Change Log → Cache → Registry — the canonical event stream that powers Studio HMR, REST writes, and future cloud editing.
+description: How metadata flows through Repository, Change Log, Cache and Registry — the event stream behind Studio hot reload, REST writes and cloud editing.
 ---
 
 This page documents the metadata data path introduced by [ADR-0008](https://github.com/objectstack-ai/objectstack/blob/main/docs/adr/0008-metadata-repository-and-change-log.md) and refined by [ADR-0005](https://github.com/objectstack-ai/objectstack/blob/main/docs/adr/0005-metadata-customization-overlay.md). It is the canonical event stream that powers Studio Hot Module Replacement (HMR), REST writes, and future cloud editing.
 
@@ -1,7 +1,7 @@
 ---
 title: North star — why this framework exists
 navTitle: North Star
-description: ObjectStack's current product and architecture direction.
+description: "Where ObjectStack is headed: a metadata-native backend that humans and AI agents can both operate safely — its principles, runtime shape and non-goals."
 ---
 
 ObjectStack is the metadata-native backend for business software that humans and
 
@@ -1,7 +1,7 @@
 ---
 title: Database drivers — Postgres, MySQL, Mongo
 navTitle: Database Drivers
-description: Configuration reference for supported database drivers
+description: Connect ObjectStack to PostgreSQL, MySQL, SQLite, MongoDB, Turso or memory — URL-based driver inference, per-driver config keys and dialect caveats.
 ---
 
 ObjectStack supports multiple database backends through a unified driver interface.
 
@@ -1,7 +1,7 @@
 ---
 title: Deployment — ship a runtime to production
 navTitle: Deployment Overview
-description: Two things deploy on this platform and they move on separate clocks — the platform runtime you operate, and the metadata app you build. Which one you are doing decides which pages in this section are yours.
+description: Deploy the platform runtime or ship your metadata app — two things on separate clocks. Find out which one you are doing and which pages cover it.
 ---
 
 Two different things get deployed here, and they run on **separate clocks**:
 
@@ -1,7 +1,7 @@
 ---
 title: Publish, versioning and preview builds
 navTitle: Publish, Versioning & Preview
-description: A metadata app is versioned in your catalog while the platform moves on its own release train. Compile the app into an artifact, then pick how it reaches a running platform — installed from the catalog, or pinned as the runtime's boot artifact.
+description: Compile a metadata app into a versioned artifact, then install it from the catalog or pin it as the runtime's boot artifact to preview and publish.
 ---
 
 ## Your app and the platform move on separate clocks