Apply suggestions from code review

Co-authored-by: Tim Bastin <38261809+timbastin@users.noreply.github.com>

Author: timbastin

src/pages/explanations/supply-chain-security/transitive-vulnerability-path-analysis.mdx

@@ -121,14 +121,14 @@ The algorithm downloads the package metadata and asks: "What does this version r
 The answer comes in the form of a version constraint, like:
 - "version 4.3.0 or higher"
 - "version 4.3 compatible versions"
-- "version 4 specifically"
+- "Anything that has major version 4"
 
 ### Step 4: Find the Best Matching Version
 
 Given that constraint ("4.3.0 or higher"), look at all available versions in the registry.
 
 The algorithm picks the highest version that satisfies the constraint. In this case, if versions 4.3.0, 4.3.1, 4.4.0, 4.5.1, and 5.0.0 exist, it would pick 4.5.1 because:
-- It's the latest version available
+- It's the latest version available in the **same** major release
 - It still satisfies "4.3.0 or higher"
 - It doesn't break the requirement