From 996e92ca133de7b436c9ce48af5fcd7381ccb3df Mon Sep 17 00:00:00 2001
From: Drew Sirenko <68304519+AndrewSirenko@users.noreply.github.com>
Date: Fri, 27 Dec 2024 13:45:45 -0500
Subject: [PATCH] Update volume modification example 6 hour cooldown note

---
 docs/modify-volume.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/modify-volume.md b/docs/modify-volume.md
index 4c2af93f8a..78b076ee1c 100644
--- a/docs/modify-volume.md
+++ b/docs/modify-volume.md
@@ -40,7 +40,8 @@ The EBS CSI Driver also supports modifying tags of existing volumes (only availa
 
 ## Considerations
 
-- Keep in mind the [6 hour cooldown period](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifyVolume.html) for EBS ModifyVolume. Multiple ModifyVolume calls for the same volume within a 6 hour period will fail. 
+- Keep in mind the [6-hour cooldown period](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifyVolume.html) for EBS ModifyVolume. Multiple ModifyVolume calls for the same volume within a 6 hour period will fail.
+  - Note: If your volume modification only creates/modifies AWS resource tags, EBS ModifyVolume will not be called and this 6-hour cooldown period does not apply.  
 - Ensure that the desired volume properties are permissible. The driver does minimum client side validation. 
 
 ## Example