Apply suggestions from code review

Author: patriciasantaana

src/content/docs/ddos-protection/managed-rulesets/network/override-expressions.mdx

@@ -39,8 +39,8 @@ Refer to the [Fields reference](/ruleset-engine/rules-language/fields/reference/
 ## Important remarks
 
 - Each expression is limited to 4,000 characters, which means you can enter approximately a maximum of 200 IP addresses in a single expression. However, you can enter IP addresses in CIDR format, which allows you to include a larger number of IP addresses. For example, you can use `192.0.0.0/24` to match IP addresses from `192.0.0.0` to `192.0.0.255`.
-- Override expressions are not allowlists. They apply to the mitigation, not detection. This means an override only takes effect if the attack fingerprint—as generated by the DDoS Managed Rules—includes the same fields specified in your expression.
+- Override expressions are not allowlists. They apply to the mitigation, not during detection. This means an override only takes effect if the attack fingerprint — as generated by the DDoS managed rules — includes the same fields specified in your expression.
 
-For example, if you create an override with sensitivity set to `Essentially Off` for `ip.src eq 192.0.2.1`, it only applies if the fingerprint includes ip.src. However, because DDoS attacks are often distributed across many source IPs, the fingerprint may not include ip.src at all. In such cases, your override is ignored.
+For example, if you create an override with sensitivity set to `Essentially Off` for `ip.src eq 192.0.2.1`, it only applies if the fingerprint includes `ip.src`. However, because DDoS attacks are often distributed across many source IPs, the fingerprint may not include `ip.src` at all. In such cases, your override is not applied.
 
-In a common scenario an attack originating from thousands of IPs targeting can target a single destination IP and port. The fingerprint would focus on the shared attributes—likely just the destination IP and port and additional packet fields that represent the strong signals of the attack pattern. Even if your override matches a specific source IP, it won’t apply if that field isn't in the fingerprint. As a result, the system will mitigate the attack using the default high sensitivity, and traffic from your specified IP could still be blocked. It is therefore recommended to use more stable expressions such as protocol, destination IP and destination port.
+In a common scenario, an attack originating from thousands of IPs can target a single destination IP and port. The fingerprint would focus on the shared attributes, such as the destination IP, port, and additional packet fields that represent strong signals of the attack pattern. Even if your override matches a specific source IP, it will not apply if that field is not present in the fingerprint. As a result, the system will mitigate the attack using the default high sensitivity, and traffic from your specified IP could still be blocked. It is recommended to use more stable expressions such as protocol, destination IP, and destination port.