diff --git a/src/pentesting-cloud/aws-security/aws-post-exploitation/aws-secrets-manager-post-exploitation.md b/src/pentesting-cloud/aws-security/aws-post-exploitation/aws-secrets-manager-post-exploitation.md
index a40a89165..2db024cce 100644
--- a/src/pentesting-cloud/aws-security/aws-post-exploitation/aws-secrets-manager-post-exploitation.md
+++ b/src/pentesting-cloud/aws-security/aws-post-exploitation/aws-secrets-manager-post-exploitation.md
@@ -62,7 +62,7 @@ aws secretsmanager restore-secret \
   --secret-id <Secret_Name>
 ```
 
-## secretsmanager:DeleteResourcePolicy, DoS
+## secretsmanager:DeleteResourcePolicy
 
 This action allows deleting the resource policy that controls who can access a secret. This could lead to a DoS if the resource policy was configured to allow access to a specific set of users.
 
@@ -72,7 +72,7 @@ aws secretsmanager delete-resource-policy \
   --secret-id <Secret_Name>
 ```
 
-## secretsmanager:UpdateSecretVersionStage, DoS
+## secretsmanager:UpdateSecretVersionStage
 
 The states of a secret are used to manage versions of a secret. AWSCURRENT marks the active version that applications use, AWSPREVIOUS keeps the previous version so that you can roll back if necessary, and AWSPENDING is used in the rotation process to prepare and validate a new version before making it the current one.