Turn off Vale for false positives

doc/operations/incident_management/alerts.md

@@ -53,6 +53,8 @@ immediately identify which alerts you should prioritize investigating:
 
 Alerts contain one of the following icons:
 
+<!-- vale gitlab.SubstitutionWarning = NO -->
+
 | Severity | Icon                    | Color (hexadecimal) |
 |----------|-------------------------|---------------------|
 | Critical | **{severity-critical}** | `#8b2615`           |
@@ -62,6 +64,8 @@ Alerts contain one of the following icons:
 | Info     | **{severity-info}**     | `#418cd8`           |
 | Unknown  | **{severity-unknown}**  | `#bababa`           |
 
+<!-- vale gitlab.SubstitutionWarning = YES -->
+
 ## Alert details page
 
 Navigate to the Alert details view by visiting the [Alert list](alerts.md)

doc/user/application_security/coverage_fuzzing/index.md

@@ -10,7 +10,7 @@ type: reference, howto
 Coverage-guided fuzzing sends random inputs to an instrumented version of your application in an
 effort to cause unexpected behavior. Such behavior indicates a bug that you should address.
 GitLab allows you to add coverage-guided fuzz testing to your pipelines. This helps you discover
-bugs and potential security issues that other QA processes may miss. 
+bugs and potential security issues that other QA processes may miss.
 
 We recommend that you use fuzz testing in addition to the other security scanners in [GitLab Secure](../index.md)
 and your own test processes. If you're using [GitLab CI/CD](../../../ci/index.md),
@@ -248,6 +248,8 @@ which shows an overview of all the security vulnerabilities in your groups, proj
 Clicking the vulnerability opens a modal that provides additional information about the
 vulnerability:
 
+<!-- vale gitlab.Acronyms = NO -->
+
 - Status: The vulnerability's status. As with any type of vulnerability, a coverage fuzzing
   vulnerability can be Detected, Confirmed, Dismissed, or Resolved.
 - Project: The project in which the vulnerability exists.
@@ -261,3 +263,5 @@ vulnerability:
 - Scanner: The scanner that detected the vulnerability (for example, Coverage Fuzzing).
 - Scanner Provider: The engine that did the scan. For Coverage Fuzzing, this can be any of the
   engines listed in [Supported fuzzing engines and languages](#supported-fuzzing-engines-and-languages).
+
+<!-- vale gitlab.Acronyms = YES -->

doc/user/application_security/sast/index.md

@@ -27,6 +27,8 @@ analysis are available in the [security dashboards](../security_dashboard/index.
 
 The results are sorted by the priority of the vulnerability:
 
+<!-- vale gitlab.SubstitutionWarning = NO -->
+
 1. Critical
 1. High
 1. Medium
@@ -34,6 +36,8 @@ The results are sorted by the priority of the vulnerability:
 1. Info
 1. Unknown
 
+<!-- vale gitlab.SubstitutionWarning = YES -->
+
 A pipeline consists of multiple jobs, including SAST and DAST scanning. If any job fails to finish
 for any reason, the security dashboard does not show SAST scanner output. For example, if the SAST
 job finishes but the DAST job fails, the security dashboard does not show SAST results. On failure,

doc/user/application_security/vulnerability_report/index.md

@@ -45,6 +45,8 @@ From the Vulnerability Report you can:
 
 You can filter the vulnerabilities table by:
 
+<!-- vale gitlab.SubstitutionWarning = NO -->
+
 | Filter   | Available options |
 |:---------|:------------------|
 | Status   | Detected, Confirmed, Dismissed, Resolved. |
@@ -53,6 +55,8 @@ You can filter the vulnerabilities table by:
 | Project  | For more details, see [Project filter](#project-filter). |
 | Activity | For more details, see [Activity filter](#activity-filter). |
 
+<!-- vale gitlab.SubstitutionWarning = YES -->
+
 ### Filter the list of vulnerabilities
 
 To filter the list of vulnerabilities: