From 2e6ccf288212e3f5a94de174bcf9a37c791955fa Mon Sep 17 00:00:00 2001
From: Kathryn Tan <33826441+KTanAug21@users.noreply.github.com>
Date: Wed, 4 Oct 2023 15:29:52 +0800
Subject: [PATCH] Clean instances keyword from laravel storage page (#1082)

* Remove final mentions of "instances"

* Remove mention of instances

* re-commit
---
 laravel/the-basics/laravel-volume-storage.html.markerb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/laravel/the-basics/laravel-volume-storage.html.markerb b/laravel/the-basics/laravel-volume-storage.html.markerb
index 05e5c8f39a..5b58d95ce2 100644
--- a/laravel/the-basics/laravel-volume-storage.html.markerb
+++ b/laravel/the-basics/laravel-volume-storage.html.markerb
@@ -89,14 +89,14 @@ It's the default burrow for session, cache, and file data amongst others. If you
     - The condition statement checks if the app folder does not exist in the volumized storage folder. If it does not exist, it copies over the contents of the storage_ folder to the volumized storage folder.
 
 7. <b>Finally, deploy your Laravel Fly App!</b>
-
+ 
     ```cmd
     fly deploy
     ```
 
 <div class="callout">
-Fly Volume instances do not automatically sync their data with each other. Please remember to create the appropriate data-replication logic if your Fly App will be using more than one volume instance, and if your app requires data available across the volume instances.
-</div>
+Fly Volumes do not automatically sync their data with each other. Please remember to create the appropriate data-replication logic if your Fly App will be using more than one volume instance, and if your app requires data available across its Volumes.
+</div> 
 
 #### **_Possible Errors_**