diff --git a/docs/introduction.md b/docs/introduction.md
index 3e74dca..530efaa 100644
--- a/docs/introduction.md
+++ b/docs/introduction.md
@@ -25,7 +25,7 @@ The <x-import /> component processes your import on the fly and renders a script
 
 {: .note }
 
-> Bundle is meant as a tool for Blade centric apps, like [Livewire](https://livewire.laravel.com), to enable code colocation with page specific JavaScript.
+> Bundle is meant as a tool for Blade centric apps, like [Livewire](https://livewire.laravel.com), to enable colocation of page specific JavaScript inside Blade.
 
 In contrary to how a JavaScript app would be bundled, this package creates tiny bundles usually only consisting of one module each. Depending on the props you pass to the `<x-import />` component.
 
diff --git a/docs/local-modules.md b/docs/local-modules.md
index 1a81eff..024b7ea 100644
--- a/docs/local-modules.md
+++ b/docs/local-modules.md
@@ -5,7 +5,7 @@ image: "/assets/social-square.png"
 ---
 
 {: .note }
-> Bundle is meant as a tool for Blade centric apps, like [Livewire](https://livewire.laravel.com), to enable code colocation with page specific JavaScript. Preferably the bulk your code should live inline in a script tag or in a [Alpine](https://alpinejs.dev) component.
+> Bundle is meant as a tool for Blade centric apps, like [Livewire](https://livewire.laravel.com), to enable colocation of page specific JavaScript inside Blade. Preferably the bulk your code should live inline in a script tag or in a [Alpine](https://alpinejs.dev) component.
 >
 > Local modules are a place to put boilerplate code. Like importing a single module & doing some setup, loading plugins etc. Writing complex code in here is discouraged. You should put that a inline script within the same component/partial that consumes it instead.