Apply suggestions from code review

Co-authored-by: Michal Kleiner <mk@011.nz>
silverstripe · Aug 2, 2023 · 20f67a0 · 20f67a0
1 parent 2f8167d
commit 20f67a0
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/en/06_Project_Governance/06_Minor_release_policy.md b/en/06_Project_Governance/06_Minor_release_policy.md
@@ -10,7 +10,7 @@ This policy complements the [Silverstripe CMS Major release policy](major_releas
 
 Note that the release cadence and pre-release time frame are indicative only. We may alter those in response to external constraints.
 
-Our minor release policy is more flexible because minor release upgrades are more straight forward to manage than major release upgrades. 
+Our minor release policy is more flexible because minor release upgrades are more straightforward to manage than major release upgrades. 
 
 ## Scope of the policy
 
@@ -60,7 +60,7 @@ A minor release line stays in the *bug and security fixes* phase until a follow
 
 At the end of the *bug and security fixes* phase, a Silverstripe CMS minor release line transitions to the *security fixes only* phase.
 
-In the *security fixes only* phase, a Silverstripe CMS minor release line only receives patches for high impact security issues defined has having a CVSS of 7.0 or above.
+In the *security fixes only* phase, a Silverstripe CMS minor release line only receives patches for high impact security issues defined as having a CVSS score of 7.0 or above.
 
 ### End-of-life