diff --git a/submissions/description/insufficient_security_configurability/weak_password_reset_implementation/token_is_not_invalidated_after_email_change/recommendations.md b/submissions/description/insufficient_security_configurability/weak_password_reset_implementation/token_is_not_invalidated_after_email_change/recommendations.md
index cb0399c4..4cbf7965 100644
--- a/submissions/description/insufficient_security_configurability/weak_password_reset_implementation/token_is_not_invalidated_after_email_change/recommendations.md
+++ b/submissions/description/insufficient_security_configurability/weak_password_reset_implementation/token_is_not_invalidated_after_email_change/recommendations.md
@@ -1,11 +1,11 @@
 # Recommendation(s)
 
-The password reset token should be invalidated if the account email changes. Overall, the password reset implementation should conform to the following guidelines:
+It is best practice to invalidate the password reset token when the account email changes. Overall, the password reset implementation should conform to the following guidelines:
 
-A secure password policy should be in place for the user to create a strong new password
-Password reset tokens should be long to protect against brute force guessinging attacks, linked to an individual, invalidated after use, and have a short expiry time
-Passwords should be stored and transmitted securely
-Once a user’s password has been reset, they should be prompted to login in again through the usual login portal and not automatically signed in
+- A secure password policy should be in place for the user to create a strong new password
+- Password reset tokens should be long to protect against brute force guessinging attacks, linked to an individual, invalidated after use, and have a short expiry time
+- Passwords should be stored and transmitted securely
+- Once a user’s password has been reset, they should be prompted to login in again through the usual login portal and not automatically signed in
 
 For more information refer to the following guide relating to this vulnerability:
 <https://cheatsheetseries.owasp.org/cheatsheets/Forgot_Password_Cheat_Sheet.html>