From fdbcabdbf5d361b5563f619dc45727e32285a940 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Mon, 29 Jun 2026 16:10:42 +0000 Subject: [PATCH] docs: align heading case and split a long sentence in editor setup docs --- async-collaboration/comments/setup/apryse.mdx | 2 +- async-collaboration/comments/setup/lexical.mdx | 2 +- async-collaboration/comments/setup/slatejs.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/async-collaboration/comments/setup/apryse.mdx b/async-collaboration/comments/setup/apryse.mdx index f4c52ab80..1ef017eae 100644 --- a/async-collaboration/comments/setup/apryse.mdx +++ b/async-collaboration/comments/setup/apryse.mdx @@ -40,7 +40,7 @@ npm i @pdftron/webviewer **Serve Apryse's runtime assets** -Apryse's WebViewer isn't just JavaScript — it ships with a **WebAssembly core**, the **Office Editor engine**, and a **UI shell** (HTML/CSS/JS), all under `node_modules/@pdftron/webviewer/public/`. These are loaded at runtime over **HTTP** from a URL on your site (the `path` option you pass to `WebViewer(...)`), *not* via a JS import — so your bundler won't pick them up on its own. You need to copy them into your app's static folder so the browser can fetch them. +Apryse's WebViewer isn't just JavaScript — it ships with a **WebAssembly core**, the **Office Editor engine**, and a **UI shell** (HTML/CSS/JS), all under `node_modules/@pdftron/webviewer/public/`. The browser loads these at runtime over **HTTP** from a URL on your site (the `path` option you pass to `WebViewer(...)`), *not* via a JS import. Your bundler won't pick them up on its own, so you need to copy them into your app's static folder so the browser can fetch them. Most teams automate this with a `postinstall` script: diff --git a/async-collaboration/comments/setup/lexical.mdx b/async-collaboration/comments/setup/lexical.mdx index 9c8c0ef48..8e1f4f691 100644 --- a/async-collaboration/comments/setup/lexical.mdx +++ b/async-collaboration/comments/setup/lexical.mdx @@ -215,7 +215,7 @@ npm install @veltdev/lexical-velt-comments @veltdev/client lexical -#### Step 7: Persist Editor Content Without Velt Marks (optional) +#### Step 7: Persist editor content without Velt marks (optional) - When saving editor content to your backend, you may want to exclude Velt comment marks to keep the content clean. - Use `exportJSONWithoutComments` to export the editor state as JSON without Velt comment nodes. diff --git a/async-collaboration/comments/setup/slatejs.mdx b/async-collaboration/comments/setup/slatejs.mdx index 998e0c1e8..02f2b926f 100644 --- a/async-collaboration/comments/setup/slatejs.mdx +++ b/async-collaboration/comments/setup/slatejs.mdx @@ -44,7 +44,7 @@ npm i @veltdev/slate-velt-comments -#### Step 4: Register Velt Component Type in SlateJS +#### Step 4: Register Velt component type in SlateJS - Register the Velt Comments Element type with your SlateJS editor's custom types. - This ensures proper type checking for the comments functionality.