diff --git a/docs/2.guide/1.concepts/2.vuejs-development.md b/docs/2.guide/1.concepts/2.vuejs-development.md index 476c8bb395..4679d1b3eb 100644 --- a/docs/2.guide/1.concepts/2.vuejs-development.md +++ b/docs/2.guide/1.concepts/2.vuejs-development.md @@ -25,7 +25,7 @@ We chose to build Nuxt on top of Vue for these reasons: ### Auto-imports -Every Vue component created in the [`components/`](/docs/guide/directory-structure/components) directoryof a Nuxt project will be available in your project without having to import it. If a component is not used anywhere, your production’s code will not include it. +Every Vue component created in the [`components/`](/docs/guide/directory-structure/components) directory of a Nuxt project will be available in your project without having to import it. If a component is not used anywhere, your production’s code will not include it. :read-more{to="/docs/guide/concepts/auto-imports"} diff --git a/docs/2.guide/1.concepts/7.esm.md b/docs/2.guide/1.concepts/7.esm.md index d59c685bb4..00db9d883a 100644 --- a/docs/2.guide/1.concepts/7.esm.md +++ b/docs/2.guide/1.concepts/7.esm.md @@ -38,7 +38,7 @@ However, there are some key differences with actual spec; here's [a helpful expl You may have been writing your app using ESM syntax for a long time. After all, it's natively supported by the browser, and in Nuxt 2 we compiled all the code you wrote to the appropriate format (CJS for server, ESM for browser). -When using modules you'd install into your package, things were a little different. A sample library might expose both CJS and ESM versions, and let us pick which one we wanted: +When adding modules to your package, things were a little different. A sample library might expose both CJS and ESM versions, and let us pick which one we wanted: ```json { diff --git a/docs/2.guide/2.directory-structure/1.components.md b/docs/2.guide/2.directory-structure/1.components.md index eba64a77ce..2e74fc1ea0 100644 --- a/docs/2.guide/2.directory-structure/1.components.md +++ b/docs/2.guide/2.directory-structure/1.components.md @@ -415,7 +415,7 @@ You can specify a `fallbackTag` to make it render a specific tag if it fails to ## Library Authors -Making Vue component libraries with automatic tree-shaking and component registration is super easy ✨ +Making Vue component libraries with automatic tree-shaking and component registration is super easy. ✨ You can use the `components:dirs` hook to extend the directory list without requiring user configuration in your Nuxt module. diff --git a/docs/2.guide/2.directory-structure/1.middleware.md b/docs/2.guide/2.directory-structure/1.middleware.md index 2d7f55c43c..c849fb07ad 100644 --- a/docs/2.guide/2.directory-structure/1.middleware.md +++ b/docs/2.guide/2.directory-structure/1.middleware.md @@ -9,7 +9,7 @@ Nuxt provides a customizable **route middleware** framework you can use througho There are three kinds of route middleware: -1. Anonymous (or inline) route middleware are defined directly within the page +1. Anonymous (or inline) route middleware are defined directly within the page. 2. Named route middleware, placed in the `middleware/` and automatically loaded via asynchronous import when used on a page. 3. Global route middleware, placed in the `middleware/` with a `.global` suffix and is run on every route change. @@ -157,7 +157,7 @@ export default defineNuxtPlugin(() => { ---| auth.ts ``` -In your page file, you can reference this route middleware +In your page file, you can reference this route middleware: ```vue