diff --git a/rules/S7171/secrets/rule.adoc b/rules/S7171/secrets/rule.adoc
index ec22ee6631c..1900d935cc1 100644
--- a/rules/S7171/secrets/rule.adoc
+++ b/rules/S7171/secrets/rule.adoc
@@ -7,28 +7,17 @@ include::../../../shared_content/secrets/rationale.adoc[]
 
 === What is the potential impact?
 
-// Optional: Give a general description of the secret and what it's used for.
-
 Below are some real-world scenarios that illustrate some impacts of an attacker
 exploiting the secret.
 
-// Set value that can be used to refer to the type of secret in, for example:
-// "An attacker can use this {secret_type} to ..."
 :secret_type: credentials
 
-// Where possible, use predefined content for common impacts. This content can
-// be found in the folder "shared_content/secrets/impact".
-// When using predefined content, search for any required variables to be set and include them in this file.
-// Not adding them will not trigger warnings.
-
 include::../../../shared_content/secrets/impact/phishing.adoc[]
 
 include::../../../shared_content/secrets/impact/exceed_rate_limits.adoc[]
 
 include::../../../shared_content/secrets/impact/suspicious_activities_termination.adoc[]
 
-
-
 == How to fix it
 
 include::../../../shared_content/secrets/fix/revoke.adoc[]