From 348187804844e494c9f522250d126d0f36a4e73a Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 20 Jul 2026 16:09:21 +0000 Subject: [PATCH] docs: normalize heading case on overview pages for style consistency --- ai/agents/overview.mdx | 2 +- async-collaboration/suggestions/overview.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/ai/agents/overview.mdx b/ai/agents/overview.mdx index 7d7bd3ae..6454a2f6 100644 --- a/ai/agents/overview.mdx +++ b/ai/agents/overview.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Overview" description: "Build review agents for your product that review web pages, data, charts, and anything else you can surface via API or MCP, then create findings as comment annotations." --- -## What are Review Agents? +## What are review agents? Build review agents for your product. Point an agent at a URL, and it reviews the content and posts findings as comment annotations. diff --git a/async-collaboration/suggestions/overview.mdx b/async-collaboration/suggestions/overview.mdx index 9cdc43c6..c118a62f 100644 --- a/async-collaboration/suggestions/overview.mdx +++ b/async-collaboration/suggestions/overview.mdx @@ -28,7 +28,7 @@ The accept/reject UI renders on the Velt comment dialog, so your app needs Velt - Suggestion mode is global for the current user and **not persisted**. A page reload returns to normal editing until you enable it again. - An edit is committed when the user finishes it, not on every keystroke. Text-like inputs (text, number, date, textarea, contenteditable) commit when the field loses focus (`focusout`), so each focus session produces at most one suggestion. Dropdowns, checkboxes, and radios commit on `change`, since picking a value is the whole edit. - Unchanged values never create suggestions. Focusing and blurring without editing is ignored, and `commitSuggestion` rejects a `newValue` that's identical to the old value. -- Events come from two elements: accept/reject outcomes are emitted on the **comment element**, while the rest of the lifecycle (`suggestionCreated`, `suggestionStale`, `targetEditStart`, `targetEditCommit`) is emitted on the **SuggestionElement**. See [Event Subscription](#event-subscription). +- Events come from two elements: accept/reject outcomes are emitted on the **comment element**, while the rest of the lifecycle (`suggestionCreated`, `suggestionStale`, `targetEditStart`, `targetEditCommit`) is emitted on the **SuggestionElement**. See [Event subscription](#event-subscription). - **The SDK never mutates your data.** It captures intent, orchestrates review, and persists the outcome. Applying the change is your code's job. - Drift detection is best-effort. On accept, if a getter is registered, the live value is compared against `oldValue`; a mismatch sets `driftDetected: true` on the suggestion. v1 records the flag; a future release will surface a confirmation prompt. - Stale wins over drift. If the target DOM node can't be resolved at accept time, the suggestion transitions to `stale` immediately and drift detection is skipped. @@ -424,7 +424,7 @@ Suggestions are stored as comment annotations, so you manage them from your back - Update annotation-level fields using the Update Comment Annotations REST API. [Learn more](/api-reference/rest-apis/v2/comments-feature/comment-annotations/update-comment-annotations) - Delete suggestion threads using the Delete Comment Annotations REST API. [Learn more](/api-reference/rest-apis/v2/comments-feature/comment-annotations/delete-comment-annotations) -## Event Subscription +## Event subscription ### [on](/api-reference/sdk/api/api-methods#on-6)