rename table of contents to keep the search results clean

docs/src/docPages/guide/build-your-editor.md

@@ -1,6 +1,6 @@
 # Build your editor
 
-## Table of Contents
+## toc
 
 ## Introduction
 In its simplest version tiptap comes very raw. There is no menu, no buttons, no styling. That’s intended. See tiptap as your building blocks to build exactly the editor you would like to have.

docs/src/docPages/guide/collaborative-editing.md

@@ -1,6 +1,6 @@
 # Collaborative editing
 
-## Table of Contents
+## toc
 
 ## Introduction
 

docs/src/docPages/guide/configuration.md

@@ -1,6 +1,6 @@
 # Configuration
 
-## Table of Contents
+## toc
 
 ## Introduction
 tiptap is all about customization. There are a ton of options to configure the behavior and functionality of the editor. Most of those settings can be set before creating the Editor. Give tiptap a JSON with all the settings you would like to overwrite.

docs/src/docPages/guide/custom-extensions.md

@@ -1,6 +1,6 @@
-# Custom Extensions
+# Custom extensions
 
-## Table of Contents
+## toc
 
 ## Introduction
 One of the strength of tiptap is it’s extendability. You don’t depend on the provided extensions, it’s intended to extend the editor to your liking. With custom extensions you can add new content types and new functionalities, on top of what already exists or on top of that.

docs/src/docPages/guide/custom-styling.md

@@ -1,6 +1,6 @@
 # Custom styling
 
-## Table of Contents
+## toc
 
 ## Introduction
 Tiptap is renderless, that doesn’t mean there is no styling provided. You can decided how your editor should look like.

docs/src/docPages/guide/getting-started.md

@@ -1,6 +1,6 @@
 # Getting started
 
-## Table of Contents
+## toc
 
 ## Introduction
 tiptap is framework-agnostic and works with Vue.js and React. It even works with plain JavaScript, if that’s your thing. To keep everything as small as possible, we put the code to use tiptap with those frameworks in different packages.

docs/src/docPages/guide/store-content.md

@@ -1,6 +1,6 @@
 # Store content
 
-## Table of Contents
+## toc
 
 ## Introduction
 You can store your content as a JSON object or as a good old HTML string. Both work fine. And of course, you can pass both formats to the editor to restore your content.