From ed9ae82f334957170e0f350c66d94278d019a36d Mon Sep 17 00:00:00 2001
From: Leon Si <leon@leonzalion.com>
Date: Mon, 5 Sep 2022 17:09:01 -0400
Subject: [PATCH 1/2] Update 3.modules.md

---
 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 4ae9cc05a4e..86ae547b754 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 `<FooButton>` and `useFooBar()` and **not** `<Foo>` and `useBar()`)
+Ideally you should prefix them with your module name (If your module is called `nuxt-foo`, expose `<FooButton>` and `useFooBar()` and **not** `<Button>` and `useBar()`)
 
 ### Be TypeScript Friendly
 

From 851896f4fe04669aec441421c465406d41400932 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Damian=20G=C5=82owala?=
 <48835293+DamianGlowala@users.noreply.github.com>
Date: Tue, 6 Sep 2022 00:07:46 +0200
Subject: [PATCH 2/2] Update docs/content/2.guide/6.going-further/3.modules.md

---
 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 86ae547b754..ed63c69aa48 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 `<FooButton>` and `useFooBar()` and **not** `<Button>` and `useBar()`)
+Ideally, you should prefix them with your module's name (e.g. if your module is called `nuxt-foo`, expose `<FooButton>` and `useFooBar()` and **not** `<Button>` and `useBar()`).
 
 ### Be TypeScript Friendly