nuxt · GalacticHypernova · May 4, 2023 · May 4, 2023 · May 4, 2023 · May 4, 2023
diff --git a/docs/1.getting-started/1.introduction.md b/docs/1.getting-started/1.introduction.md
@@ -1,11 +1,11 @@
 ---
 navigation.icon: uil:info-circle
-description: Nuxt's goal is to make web development intuitive and performant with a great Developer Experience in mind.
+description: Nuxt's goal is to make web development intuitive and performant with an exquisite developer experience in mind.
 ---
 
 # Introduction
 
-Nuxt is a free and [open-source framework](https://github.com/nuxt/nuxt) with an intuitive and extendable way to create type-safe, performant and production-grade full-stack web applications and websites with [Vue.js](https://vuejs.org).
+Nuxt is a free and [open-source framework](https://github.com/nuxt/nuxt) with an intuitive and extendable way to create type-safe, performant, and production-grade full-stack web applications and websites with [Vue.js](https://vuejs.org).
 
 We made everything so you can start writing `.vue` files from the beginning while enjoying hot module replacement in development and a performant application in production with server-side rendering by default.
 
@@ -16,13 +16,13 @@ Nuxt has no vendor lock-in, allowing you to deploy your application [**anywhere,
 Nuxt uses conventions and an opinionated directory structure to automate repetitive tasks and allow developers to focus on pushing features. The configuration file can still customize and override its default behaviors.
 
 ::list{type=success}
-- **File-based routing:** define routes based on the structure of your [`pages/` directory](/docs/guide/directory-structure/pages). This can make it easier to organize your application and avoid the need for manual route configuration.
+- **File-based routing:** Define routes based on the structure of your [`pages/` directory](/docs/guide/directory-structure/pages). This can make it easier to organize your application and avoid the need for manual route configuration.
 - **Code splitting:** Nuxt automatically splits your code into smaller chunks, which can help reduce the initial load time of your application.
-- **Server-side rendering out of the box:** Nuxt comes with built-in SSR capabilities, so you don't have to set up a separate server yourself.
-- **Auto-imports:** write Vue composables and components in their respective directories and use them without having to import them with the benefits of tree-shaking and optimised JS bundles.
-- **Data-fetching utilities:** Nuxt provides composables to handle SSR-compatible data fetching as well as different strategies.
-- **Zero-config TypeScript support:** write type-safe code without having to learn TypeScript with our auto-generated types and `tsconfig.json`
-- **Configured build tools:** we use [Vite](https://vitejs.dev) by default to support hot module replacement (HMR) in development and bundling your code for production with best-practices baked-in.
+- **Server-side rendering out of the box:** Nuxt has built-in SSR capabilities, so you don't have to set up a separate server.
+- **Auto-imports:** Write Vue composables and components in their respective directories and use them without having to import them with the benefits of tree-shaking and optimized JS bundles.
+- **Data-fetching utilities:** Nuxt provides composables for handling SSR-compatible data fetching and different strategies.
+- **Zero-config TypeScript support:** Write type-safe code without learning TypeScript using our auto-generated types and `tsconfig.json`.
+- **Configured build tools:** We use [Vite](https://vitejs.dev) by default to support hot module replacement (HMR) in development and bundling your code for production with best practices baked-in.
 ::
 
 Nuxt takes care of these and provides both frontend and backend functionality so you can focus on what matters: **creating your web application**.
@@ -32,45 +32,45 @@ Nuxt takes care of these and provides both frontend and backend functionality so
 Nuxt comes with built-in server-side rendering (SSR) capabilities by default, without having to configure a server yourself, which has many benefits for web applications:
 
 ::list{type=success}
-- **Faster initial page load time:** Nuxt sends a fully rendered HTML page to the browser, which can be displayed immediately. This can provide a faster perceived page load time and a better user experience (UX), especially on slower networks or devices.
-- **Improved SEO:** search engines can better index SSR pages because the HTML content is available immediately, rather than requiring JavaScript to render the content on the client-side.
-- **Better performance on low-powered devices:** it reduces the amount of JavaScript that needs to be downloaded and executed on the client-side, which can be beneficial for low-powered devices that may struggle with processing heavy JavaScript applications.
-- **Better accessibility:** the content is immediately available on the initial page load, improving accessibility for users who rely on screen readers or other assistive technologies.
-- **Easier caching:** pages can be cached on the server-side, which can further improve performance by reducing the amount of time it takes to generate and send the content to the client.
+- **Faster initial page load time:** Nuxt sends a fully rendered HTML page to the browser, which can be displayed immediately. This can provide a faster-perceived page load time and a better user experience (UX), especially on slower networks or devices.
+- **Improved SEO:** Search engines better index SSR pages because the HTML content is available immediately, rather than requiring JavaScript to render the content on the client side.
+- **Better performance on low-powered devices:** It reduces the amount of JavaScript that needs to be downloaded and executed on the client side, making it potentially beneficial for low-powered devices that may struggle with processing heavy JavaScript applications.
+- **Better accessibility:** The content is immediately available on the initial page load, improving accessibility for users who rely on screen readers or other assistive technologies.
+- **Easier caching:** Pages are cachable on the server side, which can further improve performance by reducing the time it takes to generate and send the content to the client.
 ::
 
-Overall, server-side rendering can provide a faster and more efficient user experience, as well as improve search engine optimization and accessibility.
+Overall, server-side rendering can provide a faster and more efficient user experience, including improved search engine optimization and accessibility.
 
-As Nuxt is a versatile framework, it gives you the possibility to statically render your whole application to a static hosting with `nuxt generate`,
-disable SSR globally with the `ssr: false` option or leverage hybrid rendering by setting up the `routeRules` option.
+As Nuxt is a versatile framework, it gives you the possibility to statically render your entire application to a static hosting with `nuxt generate`,
+disable SSR globally with the `ssr: false` option, or leverage hybrid rendering by setting up the `routeRules` option.
 
 ::alert{type="info"}
 Read more about the [Nuxt rendering modes](/docs/guide/concepts/rendering).
 ::
 
 ### Server engine
 
-The Nuxt server engine [Nitro](https://nitro.unjs.io) unlocks new full-stack capabilities.
+Nuxt's server engine, [Nitro](https://nitro.unjs.io), unlocks new full-stack capabilities.
 
 In development, it uses Rollup and Node.js workers for your server code and context isolation. It also generates your server API by reading files in `server/api/` and server middleware from `server/middleware/`.
 
-In production, Nitro builds your app and server into one universal `.output` directory. This output is light: minified and removed from any Node.js modules (except polyfills). You can deploy this output on any system supporting JavaScript, from Node.js, Serverless, Workers, Edge-side rendering or purely static.
+In production, it builds your app and server into one universal `.output` directory. This output is light: minified and removed from any Node.js modules (except polyfills). You can deploy it on any system supporting JavaScript, including serverless and edge environments, or pre-render for static hosting.
 
 ::alert{type="info"}
 Read more about [Nuxt server engine](/docs/guide/concepts/server-engine).
 ::
 
 ### Production-ready
 
-A Nuxt application can be deployed on a Node or Deno server, pre-rendered to be hosted in static environments, or deployed to serverless and edge providers.
+A Nuxt application is deployable on a Node or Deno server, pre-renderable for static hosting, or deployable to serverless and edge providers.
 
 ::alert{type="info"}
 Discover more in the [deployment section](/docs/getting-started/deployment).
 ::
 
 ### Modular
 
-A module system allows to extend Nuxt with custom features and integrations with third-party services.
+A module system allows extending Nuxt with custom features and integrating it with third-party services.
 
 ::alert{type="info"}
 Discover more about [modules](/docs/guide/concepts/modules).
@@ -89,7 +89,7 @@ Nuxt is composed of different [core packages](https://github.com/nuxt/nuxt/tree/
 - Nuxt 2 Bridge: [@nuxt/bridge](https://github.com/nuxt/bridge)
 ::
 
-We recommend reading each concept to have a full vision of Nuxt capabilities and the scope of each package.
+We recommend reading each concept for a complete vision of Nuxt's capabilities and the scope of each package.
 
 ::card-list
 ---
@@ -112,10 +112,10 @@ cardListClass: 'grid grid-cols-1 gap-y-4'
   Nuxt is the backbone of your Vue.js project, giving structure to build your project with confidence while keeping flexibility.
 <br>
 <br>
-  Extendable with a strong module ecosystem and hooks engine, it makes it easy to connect your REST or GraphQL endpoints, favorite CMS, CSS frameworks and more. PWA and AMP support is only a module away from your Nuxt project.
+  Extendable with an almighty module ecosystem and hooks engine, it makes it easy to connect your REST or GraphQL endpoints, favorite CMS, CSS frameworks, and more. PWA and AMP support is only a module away from your Nuxt project.
 <br>
 <br>
-  Ready to try? Head over to the [Installation section](/docs/getting-started/installation).
+  Ready to try? Head to the [Installation section](/docs/getting-started/installation).
   :::
 
   :::card-item

diff --git a/docs/1.getting-started/10.deployment.md b/docs/1.getting-started/10.deployment.md
@@ -1,11 +1,11 @@
 ---
 navigation.icon: uil:rocket
-description: Deploy on a Node.js server, pre-render for static hosting and to serverless or edge environments.
+description: Deploy on a Node.js server, pre-render for static hosting, and to serverless or edge environments.
 ---
 
 # Deployment
 
-A Nuxt application can be deployed on a Node.js server, pre-rendered for static hosting, or deployed to serverless or edge (CDN) environments.
+A Nuxt application is deployable on a Node.js server, to serverless or edge (CDN) environments, or pre-rendered for static hosting.
 
 ::alert{type=info}
 If you are looking for a list of cloud providers that support Nuxt 3, see the [list below](#supported-hosting-providers).
@@ -42,7 +42,7 @@ This preset will respect the following runtime environment variables:
 
 - `NITRO_PORT` or `PORT` (defaults to `3000`)
 - `NITRO_HOST` or `HOST` (defaults to `'0.0.0.0'`)
-- `NITRO_SSL_CERT` and `NITRO_SSL_KEY` - if both are present, this will launch the server in HTTPS mode. In the vast majority of cases, this should not be used other than for testing, and the Nitro server should be run behind a reverse proxy like nginx or Cloudflare which terminates SSL.
+- `NITRO_SSL_CERT` and `NITRO_SSL_KEY` - If both are present, this will launch the server in HTTPS mode. In most cases, this should be left alone for purposes other than testing, and the Nitro server should run behind a reverse proxy like nginx or Cloudflare, terminating SSL.
 
 #### Using PM2
 
@@ -64,24 +64,24 @@ module.exports = {
 
 #### Using Cluster Mode
 
-You can use `NITRO_PRESET=node_cluster` in order to leverage multi-process performance using Node.js [cluster](https://nodejs.org/dist/latest/docs/api/cluster.html) module.
+You can use `NITRO_PRESET=node_cluster` to leverage multi-process performance using [Node.js's cluster module](https://nodejs.org/dist/latest/docs/api/cluster.html).
 
-By default, the workload gets distributed to the workers with the round robin strategy.
+By default, the workload gets distributed to the workers with the round-robin strategy.
 
 ### Learn More
 
 :ReadMore{link="https://nitro.unjs.io/deploy/node" title="the Nitro documentation for node-server preset"}
 
 ## Static Hosting
 
-There are two ways to deploy a Nuxt application to any static hosting services:
+There are two ways to deploy a Nuxt application to any static hosting service:
 
-- Static site generation (SSG) with `ssr: true` pre-renders routes of your application at build time. (This is the default behaviour when running `nuxi generate`.) It will also generate `/200.html` and `/404.html` single-page app fallback pages, which can render dynamic routes or 404 errors on the client (though you may need to configure this on your static host).
-- Alternatively, you can prerender your site with `ssr: false` (static single-page app). This will produce HTML pages with an empty `<div id="__nuxt"></div>` where your Vue app would normally be rendered. You will lose many of the benefits of prerendering your site, so it is suggested instead to use `<ClientOnly>` to wrap the portions of your site that cannot be server rendered (if any).
+- Static Site Generation (SSG) with `ssr: true` pre-renders your application's routes at build time. (This is the default behavior when running `nuxi generate`.) It will also generate `/200.html` and `/404.html` fallback pages, which can render dynamic routes or 404 errors on the client (though you may need to configure this on your static host).
+- Alternatively, you can pre-render your site with `ssr: false` (static single-page app). This will produce HTML pages with an empty `<div id="__nuxt"></div>` where your Vue app normally would render. You will lose many benefits of pre-rendering your site, so it is suggested instead to use `<ClientOnly>` to wrap the portions of your site that cannot be server-rendered (if any).
 
 ### Crawl-based Pre-rendering
 
-Use the [`nuxi generate` command](/docs/api/commands/generate) to build your application. For every page, Nuxt uses a crawler to generate a corresponding HTML and payload files. The built files will be generated in the `.output/public` directory.
+Use the [`nuxi generate` command](/docs/api/commands/generate) to build your application. Nuxt uses a crawler to create corresponding HTML and payload files for each page. The files will be output to the `.output/public` directory.
 
 ```bash
 npx nuxi generate
@@ -129,7 +129,7 @@ defineNuxtConfig({
 
 ### Client-side Only Rendering
 
-If you don't want to pre-render your routes, another way of using static hosting is to set the `ssr` property to `false` in the `nuxt.config` file. The `nuxi generate` command will then output an `.output/public/index.html` entrypoint and JavaScript bundles like a classic client-side Vue.js application.
+If you don't want to pre-render your routes, another way of using static hosting is to set the `ssr` property to `false` in the `nuxt.config` file. The `nuxi generate` command will output a `.output/public/index.html` entry point and JavaScript bundles like a classic client-side Vue.js application.
 
 ```ts [nuxt.config.ts|js]
 defineNuxtConfig({
@@ -139,9 +139,9 @@ defineNuxtConfig({
 
 ## Presets
 
-In addition to Node.js servers and static hosting services, a Nuxt 3 project can be deployed with several well-tested presets and minimal amount of configuration.
+In addition to Node.js servers and static hosting services, a Nuxt 3 project is deployable with several well-tested presets and minimal configuration.
 
-You can explicitly set the desired preset in the [`nuxt.config`](/docs/guide/directory-structure/nuxt.config) file:
+You can explicitly set the desired preset in the [`nuxt.config` file](/docs/guide/directory-structure/nuxt.config):
 
 ```js [nuxt.config.js|ts]
 export default {
@@ -161,12 +161,12 @@ NITRO_PRESET=node-server nuxt build
 
 ### Supported Hosting Providers
 
-Nuxt 3 can be deployed to several cloud providers with a minimal amount of configuration:
+Nuxt 3 is deployable to several cloud providers with a minimal amount of configuration:
 
 - :icon{name="logos:aws" class="h-5 w-4 inline mb-2"} [AWS](https://nitro.unjs.io/deploy/providers/aws)
 - :icon{name="logos:microsoft-azure" class="h-5 w-4 inline mb-2"} [Azure](https://nitro.unjs.io/deploy/providers/azure)
 - :icon{name="ph:cloud-duotone" class="h-5 w-4 inline mb-2"} [Cleavr](https://nitro.unjs.io/deploy/providers/cleavr)
-- :icon{name="logos:cloudflare" class="h-5 w-4 inline mb-2"} [CloudFlare](https://nitro.unjs.io/deploy/providers/cloudflare)
+- :icon{name="logos:cloudflare" class="h-5 w-4 inline mb-2"} [Cloudflare](https://nitro.unjs.io/deploy/providers/cloudflare)
 - :icon{name="logos:digital-ocean" class="h-5 w-4 inline mb-2"} [DigitalOcean](https://nitro.unjs.io/deploy/providers/digitalocean)
 - :icon{name="ph:cloud-duotone" class="h-5 w-4 inline mb-2"} [Edgio](https://nitro.unjs.io/deploy/providers/edgio)
 - :icon{name="logos:firebase" class="h-5 w-4 inline mb-2"} [Firebase](https://nitro.unjs.io/deploy/providers/firebase)
@@ -179,14 +179,14 @@ Nuxt 3 can be deployed to several cloud providers with a minimal amount of confi
 
 ## CDN Proxy
 
-In most cases, Nuxt can work with third-party content that is not generated or created by Nuxt itself. But sometimes such content can cause problems, especially Cloudflare's "Minification and Security Options".
+In most cases, Nuxt can work with third-party content not generated or created by it. But sometimes such content can cause problems, especially Cloudflare's "Minification and Security Options".
 
-Accordingly, you should make sure that the following options are unchecked / disabled in Cloudflare. Otherwise, unnecessary re-rendering or hydration errors could impact your production application.
+Accordingly, you should ensure the following options are unchecked/disabled in Cloudflare. Otherwise, unnecessary re-rendering or hydration errors could impact your production application.
 
-1. Speed > Optimization > Auto Minify: Uncheck JavaScript, CSS and HTML
-2. Speed > Optimization > Disable "Rocket Loader™"
-3. Speed > Optimization > Disable "Mirage"
-4. Scrape Shield > Disable "Email Address Obfuscation"
-5. Scrape Shield > Disable "Server-side Excludes"
+1. Speed > Optimization > Auto Minify: Uncheck JavaScript, CSS, and HTML
+2. Speed > Optimization: Disable "Rocket Loader™"
+3. Speed > Optimization: Disable "Mirage"
+4. Scrape Shield: Disable "Email Address Obfuscation"
+5. Scrape Shield: Disable "Server-side Excludes"
 
 With these settings, you can be sure that Cloudflare won't inject scripts into your Nuxt application that may cause unwanted side effects.