docs: fix typo

docs/content/3.guide/1.writing/7.document-driven.md

@@ -230,4 +230,4 @@ definePageMeta({
 
 ## Example
 
-Jump into the [Document Driven Example](/examples/essentials/document-driven) to see a working example.
+Jump into the [Document Driven Example](/examples/essentials/document-driven) to see a working example.

docs/content/4.api/1.components/4.content-query.md

@@ -15,10 +15,10 @@ The `<ContentQuery>`{lang=html} component fetches a document and gives access to
 - `without`{lang=ts}: Remove a subset of fields from an array of keys.
   - Type: `Array<String>`{lang=ts}
   - Default: `undefined`{lang=ts}
-- `where`{lang=ts}: Filter results with a where clause definition.
+- `where`{lang=ts}: Filter results with a `where` clause definition.
   - Type: `{ [key: string]: any }`{lang=ts}
   - Default: `undefined`{lang=ts}
-- `sort`: Sort results with a sort clause definition.
+- `sort`{lang=ts}: Sort results with a `sort` clause definition.
   - Type: `SortParams`{lang=ts}
   - Default: `undefined`{lang=ts}
 - `limit`{lang=ts}: Limit the amount of results.

docs/content/4.api/1.components/7.prose.md

@@ -64,7 +64,7 @@ To overwrite a prose component, create a component with the same name in your pr
 
 ::
 
-Check out [highlight options](/api/configuration#highlight) for more about the syntax highlighting.
+Check out the [highlight options](/api/configuration#highlight) for more about the syntax highlighting.
 
 ## `ProseCodeInline`
 

docs/content/4.api/2.composables/1.query-content.md

@@ -39,7 +39,7 @@ const articles = await queryContent('articles').where({ age: { $gt: 18 } }).find
 const articles = await queryContent('articles').where({ name: { $in: ['odin', 'thor'] } }).find()
 ```
 
-In order to filter in objects and array you can use nested properties style:
+In order to filter in objects and an array or arrays, you can use the nested properties style:
 
 ```ts
 const products = await queryContent('products').where({ 'categories': { $contains: 'top' } }).find()
@@ -153,7 +153,7 @@ const articles = await queryContent('articles').find()
 
 ## `findOne()`
 
-Fetch first matched content.
+Fetch the first match of content.
 
 ```ts
 const firstArticle = await queryContent('articles').findOne()
@@ -168,7 +168,7 @@ const firstArticle = await queryContent('articles').findOne()
   - Type: `{ before: number, after: number }`{lang=ts}
   - Default: `{ before: 1, after: 1 }`{lang=ts}
 
-Get previous and next results around the path. The path should be full path of the target content.
+Get the previous and next results around the path. The path should be the full path of the target content.
 
 You will always obtain an array of fixed length filled with the matching document or null.
 

docs/content/4.api/3.configuration.md

@@ -77,7 +77,7 @@ The watcher is a development feature and will not be included in production.
 
 Define different sources for contents.
 
-Contents can located in multiple places, in multiple directories or in remote git repositories.
+Contents can be located in multiple places, in multiple directories, or in remote git repositories.
 
 ```ts [nuxt.config.ts]
 export default defineNuxtConfig({
@@ -167,7 +167,7 @@ Whether MDC syntax should be supported or not.
 
 Control behavior of Table of Contents generation.
 
-- `depth`{lang=ts}: Maximum heading depth to includes in the table of contents.
+- `depth`{lang=ts}: Maximum heading depth to include in the table of contents.
 - `searchDepth`{lang=ts}: Maximum depth of nested tags to search for heading.
 
 ### `tags`
@@ -193,7 +193,7 @@ export default defineNuxtConfig({
 - Type: `Boolean | Object`{lang=ts}
 - Default: `{depth: 4, exclude: [1]}`{lang=ts}
 
-By default Content module generates anchor links for `h2`, `h3` and `h4` heading. Using this option you can control link generation.
+By default, the Content module generates anchor links for `h2`, `h3` and `h4` headings. Using this option, you can control link generation.
 
 `false`{lang=ts} will disable link generation.
 
@@ -204,7 +204,7 @@ By default Content module generates anchor links for `h2`, `h3` and `h4` heading
 | Option  |    Type    | Description                                              |
 | ------- | :--------: | :------------------------------------------------------- |
 | depth   |  `number`  | Sets the maximal depth for anchor link generation.       |
-| exclude | `number[]` | A list of which headings to exclude from link generation |
+| exclude | `number[]` | A list of headings to exclude from link generation. |
 
 
 ## `highlight`
@@ -252,7 +252,7 @@ export default defineNuxtConfig({
 
 By default, module preloads couple of languages for syntax highlighter: `['diff', 'json', 'js', 'ts', 'css', 'shell', 'html', 'md', 'yaml']`{lang=ts} 
 
-If you plan to use code samples of other languages you need to define the language in this options.
+If you plan to use code samples of other languages, you need to define the language in these options.
 
 ```ts
 export default defineNuxtConfig({

docs/content/4.api/4.advanced.md

@@ -77,10 +77,10 @@ Internally, the module has specific transformers for each content type to parse
 You can create custom transformers to support new content types or improve functionalities of supported content types.
 
 1. Create your transformer. A transformer consists of 4 parts:
-  - `name`: Transformer name
-  - `extensions`: List of valid file extensions
-  - `parse`: If provided this function will be used to parsed the raw content
-  - `transform`: Received that parsed content and manipulate the content. 
+  - `name`: Transformer name.
+  - `extensions`: List of valid file extensions.
+  - `parse`: If provided, this function will be used to parse the raw content.
+  - `transform`: Receives that parsed content and manipulates it. 
 
 ```ts [my-transformer.ts]
 // filename: my-transformer.ts