typos

Author: patriciasantaana

src/content/partials/ddos-protection/override-example.mdx

@@ -42,5 +42,5 @@ An additional dimension to take into account is Cloudflare’s DDoS systems will
 
 You receive a small attack below the threshold for low sensitivity, but above the threshold for high sensitivity on **managed rule 1**.
 
-- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next Managed Rule in case Override Rules instructs DoS to mitigate. 
+- **Rule override A** does not meet the low sensitivity threshold. Therefore, we do not match the override and do not mitigate the attack, but proceed to evaluate the next managed rule in case the rule override instructs DoS to mitigate. 
 - **Rule override B** sets `log` at default visibility, which matches the condition. So, the defined action is applied and attack traffic is logged.

src/content/partials/ddos-protection/override-logic.mdx

@@ -3,7 +3,7 @@
 
 ---
 
-When Cloudflare’s DDoS Protection systems detect an attack, an ephemeral mitigation rule is created and installed in-line to mitigate the attack. A mitigation rule is generated based on the logic of the DDoS Protection Managed Ruleset. Each mitigation rule is generated from a single managed rule.
+When Cloudflare's DDoS Protection systems detect an attack, an ephemeral mitigation rule is created and installed in-line to mitigate the attack. A mitigation rule is generated based on the logic of the DDoS Protection managed ruleset. Each mitigation rule is generated from a single managed rule.
 
 All mitigations and its associated managed rules are evaluated in order by the DDoS systems one by one. Cloudflare will go through all of the rule overrides defined in the ruleset overrides until one matches the managed rule, and apply the action and stop at that point. Otherwise, the evaluation will continue in order until a rule matches.