docs: fix 404 links

Author: atinux

docs/content/blog/visual-editor.md

@@ -34,7 +34,7 @@ This article explains the technical processes behind the visual editor, explorin
 
 ![Edit directly markdown on Nuxt Studio](/blog/markdown-editor.webp)
 
-The Markdown editor in Nuxt Studio provides full control over your content, allowing you to write directly in [MDC](https://content.nuxt.com/usage/markdown) (an empowered Markdown syntax). This syntax enables integration of Vue components directly into your Markdown files, offering more flexibility to structure your pages.
+The Markdown editor in Nuxt Studio provides full control over your content, allowing you to write directly in [MDC](/docs/files/markdown) (an empowered Markdown syntax). This syntax enables integration of Vue components directly into your Markdown files, offering more flexibility to structure your pages.
 
 When your file is saved with the Markdown editor, the content is stored exactly as you've written it, preserving all specific syntax and formatting. This editor is ideal for users comfortable with Markdown who want precise control over the layout and structure of their content.
 
@@ -60,7 +60,7 @@ As the Visual Editor translates the visual formatting back into Markdown, it app
 
 #### **Critical Changes**
 
-Ideally, every feature in Markdown has a direct and accurate equivalent in the Visual Editor. We've built custom TipTap extensions to support custom MDC syntax such as [Vue components](https://content.nuxt.com/usage/markdown#vue-components) edition or [front-matter](https://content.nuxt.com/usage/markdown#front-matter). However, in rare cases, particularly with complex or unconventional Markdown elements, the Visual Editor may not fully support or correctly interpret these elements. When this happens, the editor might approximate, simplify, or even omit these elements during the parsing process.
+Ideally, every feature in Markdown has a direct and accurate equivalent in the Visual Editor. We've built custom TipTap extensions to support custom MDC syntax such as [Vue components](/docs/files/markdown#vue-components) edition or [front-matter](/docs/files/markdown#front-matter). However, in rare cases, particularly with complex or unconventional Markdown elements, the Visual Editor may not fully support or correctly interpret these elements. When this happens, the editor might approximate, simplify, or even omit these elements during the parsing process.
 
 Such discrepancies can result in data loss or regressions when converting back to Markdown. While these occurrences are rare, they can disrupt the intended display or functionality of your content.
 

docs/content/changelog/frontmatter-form.md

@@ -25,12 +25,12 @@ You can now edit your markdown front-matter without writing in the `YAML` syntax
 
 ## What is the front-matter?
 
-Front-matter is a convention used in Markdown-based CMSs to provide metadata for pages, such as descriptions, titles, and more. In [Nuxt Content](https://content.nuxt.com/usage/markdown#front-matter), the front-matter uses the YAML syntax.
+Front-matter is a convention used in Markdown-based CMSs to provide metadata for pages, such as descriptions, titles, and more. In [Nuxt Content](/docs/files/markdown#front-matter), the front-matter uses the YAML syntax.
 
 ::callout
 ---
 icon: i-ph-info
-to: https://content.nuxt.com/usage/markdown#front-matter
+to: /docs/files/markdown#front-matter
 ---
 For more detailed information about front-matter syntax, visit the Nuxt Content documentation.
 ::

docs/content/changelog/yaml-json-form.md

@@ -41,6 +41,6 @@ In the coming months, we’ll focus on testing and refining Nuxt Content v3 to e
 
 - **Merging the Studio module**: Soon, the Studio module will be integrated directly into Nuxt Content. Once Nuxt Content v3 is released, activating Studio will be as simple as setting `content.editor: true` in your `nuxt.config.ts` file. This simplification means no extra module is required for Studio, making setup faster.
 - **Unified documentation**: With the module integration, we’ll also merge the [Content](https://content.nuxt.com) and [Studio](https://nuxt.studio) documentation and websites into one comprehensive resource. Only the Studio platform (available once the user is logged) will remain as a standalone site.
-- **Take advantage of data structures and collections in Studio**: With Nuxt Content v3, the Studio platform will support and adapt its behaviour to [collections](https://content.nuxt.com/getting-started/collections) and user-defined schemas. This enhancement will allow schema-generated forms for both YAML and JSON files as well as front-matter within Markdown files.
+- **Take advantage of data structures and collections in Studio**: With Nuxt Content v3, the Studio platform will support and adapt its behaviour to [collections](/docs/collections/define) and user-defined schemas. This enhancement will allow schema-generated forms for both YAML and JSON files as well as front-matter within Markdown files.
 
 These updates reflect our commitment to providing the best content editing platform for your Nuxt website. Stay tuned!