From de3875c2d1cb86190715bc3755fe97c7c1e698b4 Mon Sep 17 00:00:00 2001
From: s-3ntinel <30324873+s-3ntinel@users.noreply.github.com>
Date: Mon, 16 Sep 2024 11:04:50 +0200
Subject: [PATCH] update typo in the sentence

---
 .../secret-scanning/introduction/about-secret-scanning.md       | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/code-security/secret-scanning/introduction/about-secret-scanning.md b/content/code-security/secret-scanning/introduction/about-secret-scanning.md
index 12276eeeb9a2..e0ca7ca894f3 100644
--- a/content/code-security/secret-scanning/introduction/about-secret-scanning.md
+++ b/content/code-security/secret-scanning/introduction/about-secret-scanning.md
@@ -54,7 +54,7 @@ Below is a typical workflow that explains how {% data variables.product.prodname
 
 * **Review**: When a secret is detected, you'll need to review the alert details provided.
 
-* **Remediation**: You then need take appropriate actions to remediate the exposure. This might include:
+* **Remediation**: You then need to take appropriate actions to remediate the exposure. This might include:
   * Rotating the affected credential to ensure it is no longer usable.
   * Removing the secret from the repository's history (using tools like BFG Repo-Cleaner or {% data variables.product.prodname_dotcom %}'s built-in features).