align optional features with support

Author: armchairlinguist

docs/semgrep-appsec-platform/azure-pr-comments.md

@@ -136,34 +136,18 @@ steps:
 
 <CommentsInSupplyChain />
 
-## Customize PR comments
+## Optional features
 
-<CustomComments comment_type="PR" link_type="HTML, Markdown, and plaintext" />
+### Customize PR comments
 
-## Optional features
+<CustomComments comment_type="PR" link_type="HTML, Markdown, and plaintext" />
 
 ### Enable Autofix in Azure repositories
 
 [Autofix](/writing-rules/autofix) is a Semgrep feature in which rules contain suggested fixes to resolve findings.
 
 <EnableAutofix />
 
-### Dataflow traces in MR comments
-
-With **dataflow traces**, Semgrep Code provides you a visualization of the path of tainted, or untrusted, data in specific findings. This path can help you track the sources and sinks of the tainted data as they propagate through the body of a function or a method. For general information about taint analysis, see [Taint tracking](/writing-rules/data-flow/taint-mode/overview).
-
-When running Semgrep Code from the command line, you can pass in the flag `--dataflow-traces` to use this feature.
-
-You can view dataflow traces in the PR comments created by Semgrep Code.
-
-#### View the path of tainted data in MR comments
-
-To enable dataflow traces in your MR comments, fulfill the following prerequisites:
-
-- Set up Semgrep to post Azure DevOps pull request comments, as described on this page.
-- To get the most meaningful results of dataflow traces in PR comments, use cross-file analysis while scanning your repositories. To enable cross-file analysis, see [<i class="fa-regular fa-file-lines"></i> Perform cross-file analysis](/semgrep-code/semgrep-pro-engine-intro).
-- Not all Semgrep rules or rulesets make use of taint tracking. Ensure that you have a ruleset such as the **default ruleset** added to your **[Policies](https://semgrep.dev/orgs/-/policies)**. If this ruleset is not added, go to [https://semgrep.dev/p/default](https://semgrep.dev/p/default), and then click **Add to Policy**. You can add rules that use taint tracking from [Semgrep Registry](https://semgrep.dev/explore).
-
 ## Next steps
 
 <NextAfterComments />

docs/semgrep-appsec-platform/bitbucket-cloud-pr-comments.md

@@ -225,34 +225,18 @@ Bitbucket Premium provides [<i class="fas fa-external-link fa-xs"></i> access co
 Only rules set to the **Comment** and **Block** rule modes in the [Policies page](https://semgrep.dev/orgs/-/policies) create PR comments.
 :::
 
-## Customize PR comments
+## Optional features
 
-<CustomComments comment_type="PR" link_type="Markdown and plaintext" />
+### Customize PR comments
 
-## Optional features
+<CustomComments comment_type="PR" link_type="Markdown and plaintext" />
 
 ### Enable Autofix in Bitbucket Cloud repositories
 
 [Autofix](/writing-rules/autofix) is a Semgrep feature in which rules contain suggested fixes to resolve findings.
 
 <EnableAutofix />
 
-### Dataflow traces in MR comments
-
-With **dataflow traces**, Semgrep Code provides you a visualization of the path of tainted, or untrusted, data in specific findings. This path can help you track the sources and sinks of the tainted data as they propagate through the body of a function or a method. For general information about taint analysis, see [Taint tracking](/writing-rules/data-flow/taint-mode/overview).
-
-When running Semgrep Code from the command line, you can pass in the flag `--dataflow-traces` to use this feature.
-
-You can view dataflow traces in the PR comments created by Semgrep Code.
-
-#### View the path of tainted data in PR comments
-
-To enable dataflow traces in your PR comments, fulfill the following prerequisites:
-
-- Set up Semgrep to post Bitbucket Cloud pull request comments, as described on this page.
-- To get the most meaningful results of dataflow traces in PR comments, use cross-file analysis while scanning your repositories. To enable cross-file analysis, see [<i class="fa-regular fa-file-lines"></i> Perform cross-file analysis](/semgrep-code/semgrep-pro-engine-intro).
-- Not all Semgrep rules or rulesets make use of taint tracking. Ensure that you have a ruleset such as the **default ruleset** added to your **[Policies](https://semgrep.dev/orgs/-/policies)**. If this ruleset is not added, go to [https://semgrep.dev/p/default](https://semgrep.dev/p/default), and then click **Add to Policy**. You can add rules that use taint tracking from [Semgrep Registry](https://semgrep.dev/explore).
-
 ## Next steps
 
 <NextAfterComments />

docs/semgrep-appsec-platform/bitbucket-data-center-pr-comments.md

@@ -86,7 +86,9 @@ Once you've successfully enabled webhooks and the **Triage via code review comme
 
 <CommentsInSupplyChain />
 
-## Customize PR comments
+## Optional features
+
+### Customize PR comments
 
 <CustomComments comment_type="PR" link_type="Markdown and plaintext" />
 
@@ -96,22 +98,6 @@ Once you've successfully enabled webhooks and the **Triage via code review comme
 
 <EnableAutofix />
 
-### Dataflow traces in MR comments
-
-With **dataflow traces**, Semgrep Code provides you a visualization of the path of tainted, or untrusted, data in specific findings. This path can help you track the sources and sinks of the tainted data as they propagate through the body of a function or a method. For general information about taint analysis, see [Taint tracking](/writing-rules/data-flow/taint-mode/overview).
-
-When running Semgrep Code from the command line, you can pass in the flag `--dataflow-traces` to use this feature.
-
-You can view dataflow traces in the PR comments created by Semgrep Code.
-
-#### View the path of tainted data in PR comments
-
-To enable dataflow traces in your PR comments, fulfill the following prerequisites:
-
-- Set up Semgrep to post Bitbucket Data Center pull request comments, as described on this page.
-- To get the most meaningful results of dataflow traces in PR comments, use cross-file analysis while scanning your repositories. To enable cross-file analysis, see [<i class="fa-regular fa-file-lines"></i> Perform cross-file analysis](/semgrep-code/semgrep-pro-engine-intro).
-- Not all Semgrep rules or rulesets make use of taint tracking. Ensure that you have a ruleset such as the **default ruleset** added to your **[Policies](https://semgrep.dev/orgs/-/policies)**. If this ruleset is not added, go to [https://semgrep.dev/p/default](https://semgrep.dev/p/default), and then click **Add to Policy**. You can add rules that use taint tracking from [Semgrep Registry](https://semgrep.dev/explore).
-
 ## Next steps
 
 <NextAfterComments />

docs/semgrep-appsec-platform/gitlab-mr-comments.md

@@ -97,6 +97,10 @@ You've set up MR comments! Enable optional features provided in the following se
 
 ## Optional features
 
+### Customize MR comments
+
+<CustomComments comment_type="MR" link_type="HTML, Markdown, and plaintext" />
+
 ### Enable Autofix in GitLab repositories
 
 [Autofix](/writing-rules/autofix) is a Semgrep feature in which rules contain suggested fixes to resolve findings.
@@ -119,10 +123,6 @@ To enable dataflow traces in your MR comments, fulfill the following prerequisit
 - To get the most meaningful results of dataflow traces in MR comments, use cross-file analysis while scanning your repositories. To enable cross-file analysis, see [<i class="fa-regular fa-file-lines"></i> Perform cross-file analysis](/semgrep-code/semgrep-pro-engine-intro).
 - Not all Semgrep rules or rulesets make use of taint tracking. Ensure that you have a ruleset such as the **default ruleset** added to your **[Policies](https://semgrep.dev/orgs/-/policies)**. If this ruleset is not added, go to [https://semgrep.dev/p/default](https://semgrep.dev/p/default), and then click **Add to Policy**. You can add rules that use taint tracking from [Semgrep Registry](https://semgrep.dev/explore).
 
-### Customize MR comments
-
-<CustomComments comment_type="MR" link_type="HTML, Markdown, and plaintext" />
-
 ## Next steps
 
 <NextAfterComments />