docs: spelling mistakes in the migration guide (#2908)

Author: puzzle-it-nu

docs/content/docs/1.getting-started/3.configuration.md

@@ -15,7 +15,7 @@ export default defineNuxtConfig({
 
 ## `build`
 
-Nuxt Content read and parse all the available contents at built time. This option let you control over parsing contents.
+Nuxt Content read and parse all the available contents at build time. This option gives you control over parsing contents.
 
 ### `markdown`
 
@@ -183,7 +183,7 @@ export default defineNuxtConfig({
 
 - `highlight.langs`
 
-By default, module loads couple of languages for syntax highlighter:
+By default, the module loads a couple of languages for syntax highlighting:
 
 ```ts [Default]
 ['json', 'js', 'ts', 'html', 'css', 'vue', 'shell', 'mdc', 'md', 'yaml']
@@ -256,7 +256,7 @@ Here is the list of supported database adapters:
 
 ### `SQLite`
 
-If you want to change default database location and move it to elsewhere you can use `sqlite` adapter to do so. This is the default value to `database` option.
+If you want to change the default database location and move it to elsewhere you can use `sqlite` adapter to do so. This is the default value to the `database` option.
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -271,7 +271,7 @@ export default defineNuxtConfig({
 
 ### `D1`
 
-If you plan to deploy your application to Couldflare workers, you need to use `d1` database adapter. Create `d1` binding in Cloudflare dashboard and fill the `binding` field.
+If you plan to deploy your application to Cloudflare workers, you need to use the `d1` database adapter. Create a `d1` binding in the Cloudflare dashboard and fill in the `binding` field.
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -286,12 +286,12 @@ export default defineNuxtConfig({
 
 ### `Postgres`
 
-If you plan to deploy your application using PostgreSql database you need to use `postgres` database adapter.
+If you plan to deploy your application using PostgreSQL database you need to use the `postgres` database adapter.
 
 First, make sure to install the `pg` package:
 
 ```bash [Terminal]
-npx nypm i pg
+npx npm i pg
 ```
 
 Then, configure the `postgres` adapter in your `nuxt.config.ts`:
@@ -310,12 +310,12 @@ export default defineNuxtConfig({
 
 ### `LibSQL`
 
-If you plan to deploy your application using LibSQL database you need to use `libsql` database adapter.
+If you plan to deploy your application using a LibSQL database you need to use the `libsql` database adapter.
 
 First, make sure to install the `@libsql/client` package:
 
 ```bash [Terminal]
-npx nypm i @libsql/client
+npx npm i @libsql/client
 ```
 
 Then, configure the `libsql` adapter in your `nuxt.config.ts`:

docs/content/docs/1.getting-started/4.migration.md

@@ -3,7 +3,7 @@ title: Migration
 description: How to migrate from v2 to v3
 ---
 
-Nuxt Content v3 had been rebuilt from the ground up, resulting in a new library with enhanced capabilities. While we've redesigned concepts and components in a similar way as Content v2, breaking changes are inevitable.
+Nuxt Content v3 has been rebuilt from the ground up, resulting in a new library with enhanced capabilities. While we've redesigned concepts and components in a similar way as Content v2, breaking changes are inevitable.
 
 Don't worry, you don't need to modify your content files, We made sure that Content v3 handles content in the same way as Content v2.
 
@@ -40,7 +40,7 @@ Don't worry, you don't need to modify your content files, We made sure that Cont
 
 ## Implement Document Driven mode in v3
 
-Implementing document driven mode is Content v3 is quite easy. All you need is to create a catch-all page in Nuxt and fetch contents based on route path.
+Implementing document driven mode in Content v3 is quite easy. All you need is to create a catch-all page in Nuxt and fetch contents based on route path.
 
 ```vue [pages/[...slug\\].vue]
 <script lang="ts" setup>
@@ -63,9 +63,9 @@ const { data: page } = await useAsyncData(route.path, () => {
 
 ## Converting `queryContent` to `queryCollections`
 
-As we mentioned above, `queryContent` is droped in favor of new collection based `queryCollection`. There is two main difference between these two:
+As we mentioned above, `queryContent` is dropped in favor of new collection based `queryCollection`. There are two main differences between these two:
 
-1. `queryCollection` is builting a query for SQL database.
+1. `queryCollection` is building a query for SQL database.
 2. `queryCollection` do the search only inside the specific collection. You should know the collection.
 
 ```ts [Find content with path]

docs/content/docs/3.files/1.markdown.md

@@ -86,15 +86,15 @@ const { data: post } = await useAsyncData(`blog-${slug}`, () => {
 Read more about the [`<ContentRenderer>`](/docs/components/content-renderer) component and [`Prose Components`](/docs/components/prose).
 ::
 
-## Front-matter
+## Frontmatter
 
-Front-matter is a convention of Markdown-based CMS to provide meta-data to pages, like description or title. In Nuxt Content, the front-matter uses the YAML syntax with `key: value` pairs.
+Frontmatter is a convention of Markdown-based CMS to provide meta-data to pages, like description or title. In Nuxt Content, the frontmatter uses the YAML syntax with `key: value` pairs.
 
 These data are available when rendering the content and can store any information that you would need.
 
 ### Syntax
 
-You can declare a front-matter block at the top of the Markdown files in the `content/` directory with the `---` identifier.
+You can declare a frontmatter block at the top of the Markdown files in the `content/` directory with the `---` identifier.
 
 ```md [content/index.md]
 ---
@@ -294,7 +294,7 @@ Oops! An error occurred
 ::
 ```
 
-The `v-bind` shorthand `:` can be also be used to bind a prop to a value in the front matter.
+The `v-bind` shorthand `:` can be also be used to bind a prop to a value in the frontmatter.
 
 ```mdc
 ---
@@ -418,7 +418,7 @@ Attributes work on:
 
 ## Binding Data in Markdown
 
-You can bind data within your Markdown document using the `{{ $doc.variable || 'defaultValue' }}` syntax. These values can be defined in the YAML front matter at the top of the document, within each MDC component, or injected using the `data` prop of the `<ContentRenderer>` component.
+You can bind data within your Markdown document using the `{{ $doc.variable || 'defaultValue' }}` syntax. These values can be defined in the YAML frontmatter at the top of the document, within each MDC component, or injected using the `data` prop of the `<ContentRenderer>` component.
 
 ### Example 1: Define in YAML
 
@@ -518,7 +518,7 @@ Learn how to use `@nuxt/content`.
 Full amount of content beyond the more divider.
 ```
 
-Description property will contain the excerpt content unless defined within the Front Matter props.
+Description property will contain the excerpt content unless defined within the frontmatter props.
 
 If there is no `<!--more-->` divider in the text then excerpt is undefined.
 

docs/content/docs/3.utils/.navigation.yml docs/content/docs/4.utils/.navigation.yml

@@ -48,7 +48,7 @@ Create a query builder to search in the specific collection.
 
 Search for contents that have specific `path`. (`path` is an special field in `page` collections which generates based on fs path and can be use as route to render the content)
 
-- Patameter:
+- Parameter:
 - - `path`: The path string to match.
 
 ```ts

docs/content/docs/3.utils/1.query-collection.md docs/content/docs/4.utils/1.query-collection.md

@@ -1,5 +1,5 @@
 ---
-title: slot
+title: Slot
 description: The fastest way to inject Markdown into your Vue components.
 ---
 

docs/content/docs/3.utils/2.query-collection-navigation.md docs/content/docs/4.utils/2.query-collection-navigation.md

@@ -39,7 +39,7 @@ const { data } = useAsyncData('page-' + route.path, () => queryCollection('docs'
 </template>
 ```
 
-In case you don't want to ship raw content of a specific file you can add `rawbody: ''` to frontmatter of that file. The auto filled value of `rawbody` is acting like default value and when you define `rawbody` in the frontmater it will overwriten.
+In case you don't want to ship raw content of a specific file you can add `rawbody: ''` to frontmatter of that file. The auto filled value of `rawbody` is acting like default value and when you define `rawbody` in the frontmatter it will overwritten.
 
 ```md [content.md]
 ---
@@ -50,5 +50,5 @@ rawbody: ''
 ```
 
 ::callout
-It is important to fill frontmatter fields with a same type of data that defined in collection schema. In this case `rawbody` is a string, and you should consider passing empty string. Do not use `boolean` or other type of values.
+It is important to fill frontmatter fields with a same type of data that is defined in collection schema. In this case `rawbody` is a string, and you should consider passing empty string. Do not use `boolean` or other type of values.
 ::

docs/content/docs/3.utils/3.query-collection-item-surroundings.md docs/content/docs/4.utils/3.query-collection-item-surroundings.md

@@ -48,7 +48,7 @@ Once created, your project URL must be set to enjoy all Studio features, especia
 We are proposing a GitHub Pages deployment. By using it, we will handle all the requirements for you. However, if you want to use the deployment platform of your choice, please follow the simple guideline below.
 ::
 
-To enable the live preview, you just need to activate studio in the content configuration of your fv`nuxt.config.ts` file.
+To enable the live preview, you just need to activate studio in the content configuration of your `nuxt.config.ts` file.
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({

docs/content/docs/3.utils/4.query-collection-search-sections.md docs/content/docs/4.utils/4.query-collection-search-sections.md

@@ -7,7 +7,7 @@ navigation:
 ---
 
 ::tip
-This section explains the syncronization behaviour between Studio and GitHub. However this process is handled directly from the platform and do not require any external action. This page purpose is purely informational.
+This section explains the syncronization behaviour between Studio and GitHub. However this process is handled directly from the platform and does not require any external action. This page purpose is purely informational.
 ::
 
 ## Overview

docs/content/docs/4.components/.navigation.yml docs/content/docs/5.components/.navigation.yml

@@ -28,9 +28,9 @@ Each editor serves its own purpose. Some users are used to code edition, while o
 
 This editor is heavily inspired by Notion, well known for its intuitive design and flexibility. Much like a standard text editor, this editor is designed to be familiar and easy to use. However, it stands out with its additional features that improve the writing experience:
 
-### Front-matter
+### Frontmatter
 
-[Front-matter](/docs/files/markdown#front-matter) is a convention of Markdown-based CMS to provide meta-data to pages, like description or title or any other data you would like to store as `key: value` pair.
+[Frontmatter](/docs/files/markdown#frontmatter) is a convention of Markdown-based CMS to provide meta-data to pages, like description or title or any other data you would like to store as `key: value` pair.
 
 Based on the user [collection and schema](/docs/collections/collections) provided, a form is generated to edit this metadata from the editor.
 

docs/content/docs/4.components/0.content-renderer.md docs/content/docs/5.components/0.content-renderer.md

@@ -58,5 +58,5 @@ That's it! You should now be able to access Studio UI and confirm that your conf
 ::
 
 ::warning
-Any modification of your `nuxt.config.ts` file or any changes in a Vue file require a restart of the Nuxt dev server. Once the server has restarted you can synchronized the Studio interface by calling the `Sync meta` action from command menu :shortcut{value="meta"} :shortcut{value="K"} . A refresh of the Studio app should also applies update.
+Any modification of your `nuxt.config.ts` file or any changes in a Vue file require a restart of the Nuxt dev server. Once the server has restarted you can synchronize the Studio interface by calling the `Sync meta` action from command menu :shortcut{value="meta"} :shortcut{value="K"} . A refresh of the Studio app should also apply the update.
 ::

docs/content/docs/4.components/1.slot.md docs/content/docs/5.components/1.slot.md

@@ -22,7 +22,7 @@ seo:
 The git-based CMS for :br Nuxt projects.
 
 #description
-Nuxt Content is a module for Nuxt that provides a simple way to manage content for your application. It allows developers to write their content in Markdown, YAML, or JSON files and then query and display it in their application.
+Nuxt Content is a module for Nuxt that provides a simple way to manage content for your application. It allows developers to write their content in Markdown, YAML, CSV or JSON files and then query and display it in their application.
 
 #links{unwrap="p"}
   :::u-button
@@ -58,7 +58,7 @@ Nuxt Content is a module for Nuxt that provides a simple way to manage content f
   File-based CMS
 
   #description{unwrap="p"}
-  Write your content in Markdown, YML, CSV or JSON and query it in your components.
+  Write your content in Markdown, YAML, CSV or JSON and query it in your components.
   :::
 
   :::u-page-card
@@ -360,7 +360,7 @@ Define your content structure with collections and query them with schema valida
   variant: naked
   ---
   #title{unwrap="p"}
-  Define schema for the collection front matter
+  Define schema for the collection frontmatter
   :::
 
   :::u-page-card