docs: remove useless front matter (#7518)

website/docs/guides/docs/docs-create-doc.mdx

@@ -1,10 +1,11 @@
 ---
 id: create-doc
-title: Create a doc
 description: Create a Markdown Document
 slug: /create-doc
 ---
 
+# Create a doc
+
 Create a Markdown file, `greeting.md`, and place it under the `docs` directory.
 
 ```bash

website/docs/guides/docs/docs-introduction.md

@@ -1,10 +1,11 @@
 ---
 id: introduction
-title: Docs Introduction
 sidebar_label: Introduction
 slug: /docs-introduction
 ---
 
+# Docs Introduction
+
 The docs feature provides users with a way to organize Markdown files in a hierarchical format.
 
 :::info

website/docs/guides/docs/docs-multi-instance.mdx

@@ -1,10 +1,11 @@
 ---
 id: multi-instance
-title: Docs Multi-instance
 description: Use multiple docs plugin instances on a single Docusaurus site.
 slug: /docs-multi-instance
 ---
 
+# Docs Multi-instance
+
 The `@docusaurus/plugin-content-docs` plugin can support [multi-instance](../../using-plugins.md#multi-instance-plugins-and-plugin-ids).
 
 :::note

website/docs/guides/docs/versioning.md

@@ -1,16 +1,16 @@
 ---
-id: versioning
-title: Versioning
 slug: /versioning
 ---
 
+# Versioning
+
+You can use the versioning CLI to create a new documentation version based on the latest content in the `docs` directory. That specific set of documentation will then be preserved and accessible even as the documentation in the `docs` directory continues to evolve.
+
 ```mdx-code-block
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 ```
 
-You can use the version script to create a new documentation version based on the latest content in the `docs` directory. That specific set of documentation will then be preserved and accessible even as the documentation in the `docs` directory changes moving forward.
-
 :::caution
 
 Think about it before starting to version your documentation - it can become difficult for contributors to help improve it!