From 9f30a2d27d7857695a205923b9d5d3f516ce69f3 Mon Sep 17 00:00:00 2001 From: Seth Malaki Date: Fri, 8 Mar 2024 09:09:03 +0000 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Christopher Tauchen --- calico-enterprise/threat/web-application-firewall.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/calico-enterprise/threat/web-application-firewall.mdx b/calico-enterprise/threat/web-application-firewall.mdx index 3fe306c26c..3c96a4b7db 100644 --- a/calico-enterprise/threat/web-application-firewall.mdx +++ b/calico-enterprise/threat/web-application-firewall.mdx @@ -222,7 +222,7 @@ By default WAF will not block a request even if it has matching rule violations. For basic customizations, it's best to add it after all the includes in `tigera.conf`. In fact, this is the reason why the `SecRuleEngine` directive and the rest of [our customizations](https://github.com/tigera/operator/blob/master/pkg/render/applicationlayer/embed/coreruleset/tigera.conf#L8-L17) are situated there. -An example is adding a sampling mode. For that, the tigera.conf will look like this: +An example is adding a sampling mode. For that, the `tigera.conf` will look like this: ```bash # coreruleset activation