From 173aead93778dad71a4b3fc0bf91a06e00323945 Mon Sep 17 00:00:00 2001 From: Leon Si Date: Tue, 6 Sep 2022 03:49:01 -0400 Subject: [PATCH] docs: fix typo (#7262) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Damian Głowala <48835293+DamianGlowala@users.noreply.github.com> --- docs/content/2.guide/6.going-further/3.modules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/2.guide/6.going-further/3.modules.md b/docs/content/2.guide/6.going-further/3.modules.md index 4ae9cc05a4..ed63c69aa4 100644 --- a/docs/content/2.guide/6.going-further/3.modules.md +++ b/docs/content/2.guide/6.going-further/3.modules.md @@ -127,7 +127,7 @@ Be careful that `nuxi dev` waits for your module setup before going to the next Nuxt Modules should provide an explicit prefix for any exposed configuration, plugin, API, composable, or component to avoid conflict with other modules and internals. -Ideally you should prefix them with your module name (If your module is called `nuxt-foo`, expose `` and `useFooBar()` and **not** `` and `useBar()`) +Ideally, you should prefix them with your module's name (e.g. if your module is called `nuxt-foo`, expose `` and `useFooBar()` and **not** `