From 79b8350b89df7529e34fc7f2a733141eb7a2e3be Mon Sep 17 00:00:00 2001
From: Anton Mykhailovskyi <amykhailovskyi@brightgrove.com>
Date: Tue, 14 Nov 2023 12:12:54 +0100
Subject: [PATCH] Fix namespace in Castables samples

---
 eloquent-mutators.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/eloquent-mutators.md b/eloquent-mutators.md
index c03d57ce634..ddb2db1c596 100644
--- a/eloquent-mutators.md
+++ b/eloquent-mutators.md
@@ -721,7 +721,7 @@ When attaching a custom cast to a model, cast parameters may be specified by sep
 
 You may want to allow your application's value objects to define their own custom cast classes. Instead of attaching the custom cast class to your model, you may alternatively attach a value object class that implements the `Illuminate\Contracts\Database\Eloquent\Castable` interface:
 
-    use App\Models\Address;
+    use App\ValueObjects\Address;
 
     protected $casts = [
         'address' => Address::class,
@@ -731,7 +731,7 @@ Objects that implement the `Castable` interface must define a `castUsing` method
 
     <?php
 
-    namespace App\Models;
+    namespace App\ValueObjects;
 
     use Illuminate\Contracts\Database\Eloquent\Castable;
     use App\Casts\Address as AddressCast;
@@ -751,7 +751,7 @@ Objects that implement the `Castable` interface must define a `castUsing` method
 
 When using `Castable` classes, you may still provide arguments in the `$casts` definition. The arguments will be passed to the `castUsing` method:
 
-    use App\Models\Address;
+    use App\ValueObjects\Address;
 
     protected $casts = [
         'address' => Address::class.':argument',