wip

gwleuverink · Jan 18, 2024 · 1d3b1dc · 1d3b1dc
1 parent b7b5fe1
commit 1d3b1dc
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/integrations/alpinejs.md b/docs/integrations/alpinejs.md
@@ -1,5 +1,5 @@
 ---
-nav_order: 3
+nav_order: 2
 title: AlpineJS
 parent: Integration examples
 image: "/assets/social-square.png"
@@ -83,7 +83,7 @@ Since the `@once` directive is added internally you are safe to use these import
 
 Because of this you are able to create composable Alpine/Blade components. For example, a calendar input may include imports for both Alpine & fullcalendar.js, regardless if those are used elsewhere on the page.
 
-This opens up a whole new dimension to fully portable Blade components!
+This opens up a whole new dimension to fully portable Blade components! But use with care. Shared dependencies [are not chunked](https://laravel-bundle.dev/caveats.html#code-splitting).
 
 ## Plugins
 

diff --git a/docs/integrations/laravel-livewire.md b/docs/integrations/laravel-livewire.md
@@ -25,7 +25,7 @@ Bundle uses the `@once` directive internally, so there is no need to wrap the co
 
 ---
 
-After you've used the `<x-import>` in your template you can retreive the bundle inside any inline script.
+After you've used the `<x-import>` in your template you can retrieve the bundle inside any inline script.
 
 ```html
 <script type="module">
-Original file line number
+Diff line change
@@ Expand Up @@
     ---
-    After you've used the `<x-import>` in your template you can retreive the bundle inside any inline script.
+    After you've used the `<x-import>` in your template you can retrieve the bundle inside any inline script.
     ```html
     <script type="module">
@@ Expand Down @@