diff --git a/docs/01-introduction/03-optimizing-local-development.md b/docs/01-introduction/03-optimizing-local-development.md
index 9043b6da7d..fb32166c9b 100644
--- a/docs/01-introduction/03-optimizing-local-development.md
+++ b/docs/01-introduction/03-optimizing-local-development.md
@@ -9,7 +9,9 @@ If you're looking for production-specific optimizations, check out [Deploying to
## Enabling OPcache
-[OPcache](https://www.php.net/manual/en/book.opcache.php) improves PHP performance by storing precompiled script bytecode in shared memory, thereby removing the need for PHP to load and parse scripts on each request.
+[OPcache](https://www.php.net/manual/en/book.opcache.php) improves PHP performance by storing precompiled script bytecode in shared memory, thereby removing the need for PHP to load and parse scripts on each request. This can significantly speed up your local development environment, especially for larger applications.
+
+### Checking OPcache status
To check if [OPcache](https://www.php.net/manual/en/book.opcache.php) is enabled, run:
@@ -23,6 +25,10 @@ You should see `opcache.enable => 1`. If not, enable it by adding the following
opcache.enable=1 # Enable OPcache
```
+
+
### Configuring OPcache settings
If you're experiencing slow response times or suspect that OPcache is running out of space, you can adjust these parameters in your `php.ini` file:
@@ -32,6 +38,10 @@ opcache.memory_consumption=128
opcache.max_accelerated_files=10000
```
+
+
- `opcache.memory_consumption`: defines how much memory (in megabytes) OPcache can use to store precompiled PHP code. You can try setting this to `128` and adjust based on your project's needs.
- `opcache.max_accelerated_files`: sets the maximum number of PHP files that OPcache can cache. You can try `10000` as a starting point and increase if your application includes a large number of files.
@@ -53,7 +63,7 @@ Tools like [Microsoft Defender](https://www.microsoft.com/en-us/microsoft-365/mi
## Disabling debugging tools
-Debugging tools can be very useful for local development, but at the same time slow down your application unnecessarily when you aren't using them.
+Debugging tools can be very useful for local development, but they can significantly slow down your application when you aren't actively using them. Temporarily disabling these tools when you need maximum performance can make a noticeable difference in your development experience.
### Disabling view debugging in Laravel Herd
@@ -90,6 +100,10 @@ If `Xdebug` is installed but not disabled, it will still be enabled by default.
xdebug.mode=off # Disable Xdebug
```
+
+
## Caching Blade icons
Caching [Blade icons](https://blade-ui-kit.com/blade-icons) can help improve performance during local development, especially in views that render many icons.