diff --git a/content/docs/200-concepts/100-how-contentlayer-works.mdx b/content/docs/200-concepts/100-how-contentlayer-works.mdx index f14e884..3c7f4d6 100644 --- a/content/docs/200-concepts/100-how-contentlayer-works.mdx +++ b/content/docs/200-concepts/100-how-contentlayer-works.mdx @@ -18,13 +18,13 @@ Other frameworks like Next.js take no stance on content, and leave it up to you. There are three main uses for Contentlayer, each revolving around the primary purpose of transforming your content into data that can be easily consumed by your code. These pieces are: -- Transformation Content into Data +- Transforming Content into Data - Structuring Loose Data - Defining Data Types -## Transformation Content into Data +## Transforming Content into Data -Regardless of the source of the data or how the data will be used in the code, the primary purpose for Contentlayer is to transform content in to data that your code can use. +Regardless of the source of the data or how the data will be used in the code, the primary purpose for Contentlayer is to transform content into data that your code can use. This process occurs by reading data from the data source, whether that source is external or a series of local files, and converting it into a format that your code can understand, as importable JavaScript files.