update docs

docs/introduction.md

@@ -37,7 +37,7 @@ If the module you're exporting uses named exports, you may resolve it like this:
 var module = await _bundle("lodash", "filter"); // Resolves a named export 'filter'
 ```
 
-**_In cases like this it might be advantagious to use per-method imports instead. Please refer to the [advanced usage example](/bundle/advanced-usage.html#per-method-exports)._**
+_In cases like this it might be advantagious to use per-method imports instead. Please refer to the [advanced usage example](/bundle/advanced-usage.html#per-method-exports)._
 
 <br />
 

docs/production-builds.md

@@ -9,6 +9,14 @@ Eventhough Bun is very fast, since Bundle transpiles & bundles your imports on t
 
 You may run `php artisan bundle:build` to bundle all your imports beforehand. These will be added to your `storage/app/bundle` directory, make sure to add those to vsc or otherwise build them in CI before deployment.
 
+You may configure what paths are scanned by publishing the Bundle config file and updating the `build_paths` array. Note this config option accepts an array of glob patterns.
+
+```php
+'build_paths' => [
+    resource_path('views/**/*.blade.php')
+]
+```
+
 <br />
 {: .note }