diff --git a/docs/content/2.guide/1.concepts/1.introduction.md b/docs/content/2.guide/1.concepts/1.introduction.md
index 32a2305fbf..339763b223 100644
--- a/docs/content/2.guide/1.concepts/1.introduction.md
+++ b/docs/content/2.guide/1.concepts/1.introduction.md
@@ -1,10 +1,10 @@
 # What is Nuxt?
 
-Nuxt goal is to make web development intuitive and performant with a great developer experience in mind.
+Nuxt's goal is to make web development intuitive and performant with a great developer experience in mind.
 
 ## Why Nuxt?
 
-To understand what is Nuxt, we need to understand what we need to create a modern application:
+To understand what Nuxt is, we need to understand what we need to create a modern application:
 ::list{type=success}
 
 - A JavaScript framework to bring reactivity and web components, we chose [Vue.js](https://v3.vuejs.org).
diff --git a/docs/content/2.guide/1.concepts/2.vuejs-development.md b/docs/content/2.guide/1.concepts/2.vuejs-development.md
index 818b69dd32..35630e188f 100644
--- a/docs/content/2.guide/1.concepts/2.vuejs-development.md
+++ b/docs/content/2.guide/1.concepts/2.vuejs-development.md
@@ -48,15 +48,15 @@ Try to replace the `<template>`’s content with a custom welcome message. The b
 
 ## Differences with Nuxt 2 / Vue 2
 
-Nuxt 3 is based on Vue 3. The new Vue major version introduces several changes that Nuxt takes advantage of:
+Nuxt 3 is based on Vue 3. The new major Vue version introduces several changes that Nuxt takes advantage of:
 
-- Better performances
+- Better performance
 - Composition API
 - TypeScript support
 
 ### Faster rendering
 
-Vue Virtual DOM (VDOM) has been rewritten from the ground up and allows for better rendering performances. On top of that, when working with compiled Single-file components, the Vue compiler can further optimize components at build time by separating static and dynamic markup.
+The Vue Virtual DOM (VDOM) has been rewritten from the ground up and allows for better rendering performance. On top of that, when working with compiled Single File Components, the Vue compiler can further optimize them at build time by separating static and dynamic markup.
 
 This results in faster first rendering (component creation) and updates, and less memory usage. In Nuxt 3, it enables faster server-side rendering as well.
 
diff --git a/docs/content/2.guide/1.concepts/3.rendering.md b/docs/content/2.guide/1.concepts/3.rendering.md
index 4e0074b696..3eeda7e6b5 100644
--- a/docs/content/2.guide/1.concepts/3.rendering.md
+++ b/docs/content/2.guide/1.concepts/3.rendering.md
@@ -1,6 +1,6 @@
 # Rendering Modes
 
-Both Browser and Server can interpret JavaScript code to render Vue.js components into HTML elements. This step is called **rendering**. Nuxt supports both **client-side** and **universal** rendering. The two approaches have pros and cons that we will cover in this section.
+Both the browser and server can interpret JavaScript code to render Vue.js components into HTML elements. This step is called **rendering**. Nuxt supports both **client-side** and **universal** rendering. The two approaches have pros and cons that we will cover in this section.
 
 ## Client-side only rendering
 
@@ -19,8 +19,8 @@ While this technique allows building complex and dynamic UIs with smooth page tr
 
 ### Cons
 
-- **Performance**: The user has to wait for the browser to download, parse and run javascript files. Depending on the network for the download part and the user's device for the parsing and execution, this can take some time and impact your user's experience.
-- **Search Engine Optimization**: Indexing and updating the content delivered via client-side rendering takes more time than an HTML document already built. This is related to the performance drawback we discussed, as search engine crawlers won't wait for the interface to be fully rendered on their first try to index the page. Your content will take more time to show and update in search results pages with pure client-side rendering.
+- **Performance**: The user has to wait for the browser to download, parse and run JavaScript files. Depending on the network for the download part and the user's device for the parsing and execution, this can take some time and impact the user's experience.
+- **Search Engine Optimization**: Indexing and updating the content delivered via client-side rendering takes more time than with a server-rendered HTML document. This is related to the performance drawback we discussed, as search engine crawlers won't wait for the interface to be fully rendered on their first try to index the page. Your content will take more time to show and update in search results pages with pure client-side rendering.
 
 ### Examples