From b764d4bef1b791c79a93756fa558970305c844e5 Mon Sep 17 00:00:00 2001
From: Greg Mohler <110078080+CallMeGreg@users.noreply.github.com>
Date: Mon, 12 Dec 2022 21:30:01 -0500
Subject: [PATCH] fixed small typo in phase 1 description

---
 .../phase-1-align-on-your-rollout-strategy-and-goals.md         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md b/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
index b63169d1c530..39723e911eee 100644
--- a/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
+++ b/content/code-security/adopting-github-advanced-security-at-scale/phase-1-align-on-your-rollout-strategy-and-goals.md
@@ -62,7 +62,7 @@ If your company is interested in custom {% data variables.product.prodname_codeq
 
 #### 5. {% data variables.product.prodname_codeql %} scans the whole codebase, not just the changes made in a pull request
 
-When code scanning is run from a pull request, the scan will include the full codebase and not just the changes made in the pull request. Scanning the entire codebase is an important step to ensure the change has been reviewed all against all interactions in the codebase.
+When code scanning is run from a pull request, the scan will include the full codebase and not just the changes made in the pull request. Scanning the entire codebase is an important step to ensure the change has been reviewed against all interactions in the codebase.
 
 {% note %}