Polish CKEditor setup docs

Author: yoen-velt

async-collaboration/comments/setup/ckeditor.mdx

@@ -3,17 +3,17 @@ title: "CKEditor Setup"
 description: "Add Velt comments to a CKEditor 5 editor with the Velt CKEditor comments plugin."
 ---
 
-![Add text comments in an editor](/gifs/Add-Text-Comments.gif)
-
-The CKEditor integration renders comment highlights as view-only overlay elements positioned over the commented text. It does not modify your CKEditor schema, saved HTML, or undo history. Highlight positions are tracked with CKEditor model ranges and re-positioned as the document changes.
+![](/gifs/Add-Text-Comments.gif)
 
 ## Setup
 
 #### Step 1: Add Comment components
 
-- Add the `Velt Comments` component to the root of your app. This component is required to create and render comments in your app.
+- Add the `Velt Comments` component to the root of your app.
+- This component is required to render comments in your app.
+- Set the `text mode` prop to `false` to hide the default text comment tool.
+- CKEditor selections are handled by `@veltdev/ckeditor-velt-comments`.
 - Authenticate the user with `authProvider` and set the Velt document before users add comments.
-- Set the `textMode` prop to `false` to hide the default Velt text comment tool. CKEditor selections are handled by `@veltdev/ckeditor-velt-comments`.
 - Add `VeltCommentsSidebar` if you want a Google Docs-style comment sidebar.
 
 <Tabs>
@@ -243,7 +243,9 @@ The library automatically writes `context.textEditorConfig` with the selected te
 
 #### Step 7: Re-apply highlights after reloading content
 
-Comment highlights are view-only overlay elements. They are not stored in the CKEditor document, so your saved HTML, schema, and undo history stay clean.
+Comment highlights are view-only overlay elements positioned over the commented text. They are not stored in the CKEditor document, so your saved HTML, schema, and undo history stay clean.
+
+Highlight positions are tracked with CKEditor model ranges and re-positioned as the document changes.
 
 Call `renderComments` whenever the editor is recreated or its content is replaced. The `useEffect` in Step 6 handles this automatically when the `editor` instance or the annotation list changes.