docs: update content

docs/src/docPages/api/commands.md

@@ -186,7 +186,7 @@ Have a look at all of the core commands listed below. They should give you a goo
 | .selectNodeForward()  | Select a node forward.                  |
 | .selectParentNode()   | Select the parent node.                 |
 
-## Example use cases
+<!-- ## Example use cases
 
 ### Quote a text
 TODO
@@ -207,7 +207,7 @@ this.editor
   .createParagraphNear()
   .insertHTML('<p></p>')
   .run()
-```
+``` -->
 
 ## Add your own commands
 All extensions can add additional commands (and most do), check out the specific [documentation for the provided nodes](/api/nodes), [marks](/api/marks), and [extensions](/api/extensions) to learn more about those.

docs/src/docPages/api/extensions/annotation.md

@@ -1,8 +0,0 @@
-# Annotation
-TODO
-
-## Source code
-[packages/extension-annotation/](https://github.com/ueberdosis/tiptap-next/blob/main/packages/extension-annotation/)
-
-## Usage
-<demo name="Extensions/Annotation" highlight="24,44-46,60-67" />

docs/src/docPages/guide/accessibility.md

@@ -14,10 +14,10 @@ An interface needs to have well-defined contrasts, big enough click areas, seman
 
 But no worries, we’ll provide an interface soon and take accessibility into account early on.
 
-## Editor
+## Output
 The editor needs to produce semantic markup, must be keyboard accessible and well documented. The tiptap content is well structured so that’s a good foundation already. That said, we can add support and encourage the usage of additional attributes, for example the Alt-attribute for images.
 
-## Writing assistance (optional)
+### Writing assistance (optional)
 An optional writing assitance could help people writing content semanticly correct, for example pointing out an incorrect usage of heading levels. With that kind of assistance provided by the core developers, we could help to improve the content of a lot of applications.
 
 ## Resources