diff --git a/docs/src/docPages/api/schema.md b/docs/src/docPages/api/schema.md
index 0af9ad93..ffe81ebf 100644
--- a/docs/src/docPages/api/schema.md
+++ b/docs/src/docPages/api/schema.md
@@ -150,7 +150,7 @@ createNode({
 ```
 
 #### Selectable
-> Controls whether nodes of this type can be selected as a node selection. Defaults to true for non-text nodes.
+Besides the already visible text selection, there is an invisible node selection. If you want to make your nodes selectable, you can configure it like this:
 
 ```js
 createNode({
@@ -177,7 +177,9 @@ createNode({
 ```
 
 #### Defining
-> Determines whether this node is considered an important parent node during replace operations (such as paste). Non-defining (the default) nodes get dropped when their entire content is replaced, whereas defining nodes persist and wrap the inserted content. Likewise, in inserted content the defining parents of the content are preserved when possible. Typically, non-default-paragraph textblock types, and possibly list items, are marked as defining.
+Nodes get dropped when their entire content is replaced (for example, when pasting new content) by default. If a node should be kept for such replace operations, configure them as `defining`.
+
+Typically, that applies to [`Blockquote`](/api/extensions/blockquote), [`CodeBlock`](/api/extensions/code-block), [`Heading`](/api/extensions/heading), and [`ListItem`](/api/extensions/list-item).
 
 ```js
 createNode({
diff --git a/docs/src/docPages/guide/collaborative-editing.md b/docs/src/docPages/guide/collaborative-editing.md
index 98b73209..85216413 100644
--- a/docs/src/docPages/guide/collaborative-editing.md
+++ b/docs/src/docPages/guide/collaborative-editing.md
@@ -1,7 +1,7 @@
 # Collaborative editing
 
-:::premium Requires Premium Extensions
-Using the collaborative editing in production requires a **tiptap pro** license. [Read more](/sponsor)
+:::premium Requires Pro Extensions
+We kindly ask you to sponsor us, before using this example in production. [Read more](/sponsor)
 :::
 
 ## toc
diff --git a/docs/src/docPages/guide/store-content.md b/docs/src/docPages/guide/store-content.md
index 4380a40a..784ae3a5 100644
--- a/docs/src/docPages/guide/store-content.md
+++ b/docs/src/docPages/guide/store-content.md
@@ -92,7 +92,7 @@ That said, tiptap **does** support Markdown shortcuts to format your content. Tr
 ## Generate HTML from ProseMirror JSON
 If you need to render the content on the server side, for example to render a blog post which was written with tiptap, you’ll probably need a way to do just that without an actual editor instance.
 
-That’s what `generateHTML()` is for. It’s a utility function that renders HTML without an actual editor instance.
+That’s what `generateHTML()` is for. It’s a utility function that renders HTML without an actual editor instance. As an easy alternative, you can also use tiptap in a [read-only mode](/examples/read-only).
 
 :::info Browser-only rendering
 Import a lightweight implementation from `@tiptap/core` if you’re using the function in a browser context only.
diff --git a/docs/src/links.yaml b/docs/src/links.yaml
index 683c5980..8fa7a0a4 100644
--- a/docs/src/links.yaml
+++ b/docs/src/links.yaml
@@ -34,7 +34,7 @@
         - title: Full Editor
           link: /examples/full-editor
           draft: true
-    - title: Feedback
+    - title: Share feedback
       link: /overview/feedback
 
 - title: Guide
@@ -152,7 +152,7 @@
       link: /api/events
     - title: Schema
       link: /api/schema
-      draft: true
+      new: true
     - title: Keyboard Shortcuts
       link: /api/keyboard-shortcuts