diff --git a/docs/content/2.usage/2.markdown.md b/docs/content/2.usage/2.markdown.md
index c07effcdc..662c26ae0 100644
--- a/docs/content/2.usage/2.markdown.md
+++ b/docs/content/2.usage/2.markdown.md
@@ -549,13 +549,13 @@ const mdcVars = ref({ name: 'Maxime'});
### Prose Components
-In Nuxt Content, the prose represents HTML tags generated by the Markdown syntax, such as title levels and links.
+In Nuxt Content, the prose represents HTML tags generated by the Markdown syntax, such as heading levels and links.
For each HTML tag, a Vue component is used, allowing you to override them if needed, for example `
` becomes ``.
If you want to customize a Prose component, here are the recommended steps:
-- Checkout the original [component sources](https://github.com/nuxt-modules/mdc/blob/main/src/runtime/components/prose).
+- Check out the original [component sources](https://github.com/nuxt-modules/mdc/blob/main/src/runtime/components/prose).
- Use the exact same props.
- In your `components/content/` directory, give it the same name.
- Make it yours 🚀.
diff --git a/docs/content/6.snippets/1.fulltext-search.md b/docs/content/6.snippets/1.fulltext-search.md
index aa566e33d..8dc5ca1df 100644
--- a/docs/content/6.snippets/1.fulltext-search.md
+++ b/docs/content/6.snippets/1.fulltext-search.md
@@ -9,7 +9,7 @@ You can use the result of this utility in combination with [Nuxt UI Content Sear
## Nuxt UI Pro
-Nuxt UI Pro provide a ready to use component for full-text search. You can use it by passing the result of `queryCollectionSearchSections` to the `files` prop of the component.
+Nuxt UI Pro provides a ready to use component for full-text search. You can use it by passing the result of `queryCollectionSearchSections` to the `files` prop of the component.
Read more about [Nuxt UI Content Search][nuxt-ui-content-search].
diff --git a/docs/content/6.snippets/2.raw-content.md b/docs/content/6.snippets/2.raw-content.md
new file mode 100644
index 000000000..803e3e68e
--- /dev/null
+++ b/docs/content/6.snippets/2.raw-content.md
@@ -0,0 +1,54 @@
+---
+title: Raw Content
+description: Access to contents raw data in appliction
+---
+
+There were lots of requests in Content version 2 about accessing contents raw data in production. We're happy to announce that in version 3 it is possible to ship contents raw data to production.
+
+In order to ship raw contents to production you need to define `rawbody` field in your collection's schema.
+That's it.
+
+Nuxt Content will detect this magical field in your schema and fill it with the raw content.
+
+```ts [content.config.ts]
+import { defineCollection, z } from '@nuxt/content'
+
+export const collections = {
+ docs: defineCollection({
+ source: '**',
+ type: 'page',
+ schema: z.object({
+ rawbody: z.string()
+ })
+ })
+}
+```
+
+And you can use `queryCollection()`{lang="ts-type"} to fetch the raw content.
+
+```vue [pages/index.vue]
+
+
+
+ {{ data.rawbody }}
+
+```
+
+
+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.
+
+```md [content.md]
+---
+title: My page
+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 empry string. Do not use `boolean` or other type of values.
+::
\ No newline at end of file
diff --git a/playground/content.config.ts b/playground/content.config.ts
index 3bee363e8..d3b018c59 100644
--- a/playground/content.config.ts
+++ b/playground/content.config.ts
@@ -11,6 +11,7 @@ const content = defineCollection({
},
schema: z.object({
date: z.date(),
+ rawbody: z.string(),
}),
})