From 26520af06a8b294d062c1e51afe5ebfb49cfbc03 Mon Sep 17 00:00:00 2001 From: Russell Dickenson <rdickenson@gitlab.com> Date: Wed, 29 May 2024 14:50:17 +1000 Subject: [PATCH] Fix spelling error --- doc/user/application_security/policies/scan-result-policies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/application_security/policies/scan-result-policies.md b/doc/user/application_security/policies/scan-result-policies.md index d5feb20f989da..a62cf3a0d5271 100644 --- a/doc/user/application_security/policies/scan-result-policies.md +++ b/doc/user/application_security/policies/scan-result-policies.md @@ -38,7 +38,7 @@ The following video gives you an overview of GitLab merge request approval polic ## Requirements and limitations - You must add the respective [security scanning tools](../index.md#application-coverage). - Otherwise, merge request approval policies cannot get evaluated and the corresonding approvals stay required. + Otherwise, merge request approval policies cannot get evaluated and the corresponding approvals stay required. - The maximum number of merge request approval policies is five per security policy project. - Each policy can have a maximum of five rules. - All configured scanners must be present in the merge request's latest pipeline. If not, approvals are required even if some vulnerability criteria have not been met. -- GitLab