diff --git a/doc/user/application_security/policies/scan-result-policies.md b/doc/user/application_security/policies/scan-result-policies.md
index d5feb20f989daad4a4f4482a575e79db616ab002..a62cf3a0d52713b4e37e6474b89fc2976151b722 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.