Update concepts.mdx

Adding IP Access Rules as part of the https://developers.cloudflare.com/waf/concepts/#rule-execution-order

Author: zeinjaber

src/content/docs/waf/concepts.mdx

@@ -61,12 +61,13 @@ Currently, you cannot manage the [bot score](/bots/concepts/bot-score/) and [att
 
 Cloudflare evaluates different types of rules when processing incoming requests. The rule execution order is the following:
 
-1. [Firewall rules](/firewall/cf-firewall-rules/) (deprecated)
-2. [Custom rulesets](/waf/account/custom-rulesets/)
-3. [Custom rules](/waf/custom-rules/)
-4. [Rate limiting rules](/waf/rate-limiting-rules/)
-5. [WAF Managed Rules](/waf/managed-rules/)
-6. [Cloudflare Rate Limiting](/waf/reference/legacy/old-rate-limiting/) (previous version, deprecated)
+1. [IP Access Rules](/waf/tools/ip-access-rules/)
+2. [Firewall rules](/firewall/cf-firewall-rules/) (deprecated)
+3. [Custom rulesets](/waf/account/custom-rulesets/)
+4. [Custom rules](/waf/custom-rules/)
+5. [Rate limiting rules](/waf/rate-limiting-rules/)
+6. [WAF Managed Rules](/waf/managed-rules/)
+7. [Cloudflare Rate Limiting](/waf/reference/legacy/old-rate-limiting/) (previous version, deprecated)
 
 Rules are evaluated in order. If there is a match for a rule with a [terminating action](/ruleset-engine/rules-language/actions/), the rule evaluation will stop and the action will be executed immediately. Rules with a non-terminating action (such as _Log_) will not prevent subsequent rules from being evaluated and executed. For more information on how rules are evaluated, refer to [Rule evaluation](/ruleset-engine/about/rules/#rule-evaluation) in the Ruleset Engine documentation.