Skip to content

Commit 20146d3

Browse files
Apply suggestions from code review
Co-authored-by: ldecarvalho-doc <[email protected]>
1 parent 2771da0 commit 20146d3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

pages/edge-services/how-to/configure-waf.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Edge Services WAF is currently in [Public Beta](https://www.scaleway.com/en/beta
1919

2020
An Edge Services **W**eb **A**pplication **F**irewall (WAF) evaluates requests to your Load Balancer origin to determine whether they are potentially malicious. You can choose the [paranoia level](/edge-services/concepts/#paranoia-level) to be used when evaluating requests, and set [exclusions](/edge-services/concepts/#exclusions) to define traffic that shouldn't be filtered by WAF. Requests that are judged to be malicious are blocked or logged, depending on the settings you choose.
2121

22-
This page walks you through the processing of enabling and configuring WAF to protect your Load Balancer origin.
22+
This page walks you through the process of enabling and configuring WAF to protect your Load Balancer origin.
2323

2424
To read more about how WAF works, try our [Understanding WAF](/edge-services/reference-content/understanding-waf/) page.
2525

@@ -41,7 +41,7 @@ To read more about how WAF works, try our [Understanding WAF](/edge-services/ref
4141

4242
<Lightbox src="scaleway-edge-waf-popup.webp" alt="A screenshot of the WAF configuration pop-up in the Scaleway console. Users can select a paranoia level from 1-4, and choose to block or log malicious requests." />
4343

44-
3. Choose the **paranoia level**, from 1 - 4, that is best adapted to your use case. The higher the paranoia level, the more sensitive WAF is to potential threats, and the more likely it is to class a request as malicious. For help with choosing a paranoia level, see our [dedicated documentation](/edge-services/reference-content/understanding-waf/#waf-ruleset-and-paranoia-levels).
44+
3. Choose the **paranoia level**, from 1 - 4, that is best adapted to your use case. The higher the paranoia level, the more sensitive WAF is to potential threats, and the more likely it is to classify a request as malicious. For help with choosing a paranoia level, see our [dedicated documentation](/edge-services/reference-content/understanding-waf/#waf-ruleset-and-paranoia-levels).
4545

4646
<Message type="tip">
4747
After enabling WAF, you will be able to [set exclusions](#how-to-set-exclusions) that filter out requests matching certain criteria from being evaluated by WAF.

0 commit comments

Comments
 (0)