diff --git a/docs/kb/semgrep-code/unexpected-new-findings.md b/docs/kb/semgrep-code/unexpected-new-findings.md
index 1abbcfb434..d6dbfce4b5 100644
--- a/docs/kb/semgrep-code/unexpected-new-findings.md
+++ b/docs/kb/semgrep-code/unexpected-new-findings.md
@@ -7,9 +7,9 @@ description: This may be occurring because rule coverage has increased.
 
 # Why are there more Semgrep findings when the code hasn't changed?
 
-If the rules you're using in Semgrep have changed since you last scanned your code, you may see more findings even if your code has not changed.
+If the rules you're using in Semgrep have changed since you last performed a full scan of your project, you may see more findings for the project even if your code has not changed.
 
-For rulesets in the Semgrep Registry, if you add a ruleset to one of your policies, the policy receives updates and additions to the ruleset on an ongoing basis. So if a rule is added to a ruleset, or changes make a rule more comprehensive (or more precise), your policy automatically picks up those changes, and the subsequent scan can show new findings for the new or updated rules.
+For rulesets in the Semgrep Registry, if you add a ruleset to one of your policies, the policy receives updates and additions to the ruleset on an ongoing basis. When a rule is added to a ruleset, or when changes make a rule more comprehensive or more precise, your policy automatically picks up those changes. As a result, the next full scan of the project may surface new findings from the new or updated rules.
 
 For Semgrep-curated rulesets, you can view each rule's history to see recent changes: