From 027ad7b3700ffa04e3fd2a45b54d51489898e98f Mon Sep 17 00:00:00 2001
From: Ahmed Alaa <92916738+AhmedAlaa4611@users.noreply.github.com>
Date: Fri, 6 Jun 2025 19:33:59 +0300
Subject: [PATCH] Improve clarity in Isolatable commands

---
 artisan.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/artisan.md b/artisan.md
index e0c386b3d04..5f114362856 100644
--- a/artisan.md
+++ b/artisan.md
@@ -243,7 +243,7 @@ class SendEmails extends Command implements Isolatable
 }
 ```
 
-When you mark a command as `Isolatable`, Laravel automatically makes the `--isolated` option available for the command without you needing to explicitly define it in the command's options. When the command is invoked with that option, Laravel will ensure that no other instances of that command are already running. Laravel accomplishes this by attempting to acquire an atomic lock using your application's default cache driver. If other instances of the command are running, the command will not execute; however, the command will still exit with a successful exit status code:
+When you mark a command as `Isolatable`, Laravel automatically makes the `--isolated` option available for the command without needing to explicitly define it in the command's options. When the command is invoked with that option, Laravel will ensure that no other instances of that command are already running. Laravel accomplishes this by attempting to acquire an atomic lock using your application's default cache driver. If other instances of the command are running, the command will not execute; however, the command will still exit with a successful exit status code:
 
 ```shell
 php artisan mail:send 1 --isolated