Bot and scrapper section done

Author: jdv

crowdsec-docs/unversioned/troubleshooting/usecases.mdx

@@ -107,47 +107,48 @@ Quickly choose among qualified malicious actors regrouped by industry, behaviors
 
 ---
 
-## Web Application Protection
+## Bot and Scraper Management
 
-Quickly protect web applications from the latest CVEs and generic vulnerability exploits using CrowdSec WAF.
+Control aggressive crawlers and scraping tools while preserving legitimate user access using graduated response strategies.  
 
 **Is it for me?**
-Ideal if you want a modern OpenSource WAF solution.  
-Benefit from CrowdSec's Virtual patching catalog while being able to use your existing ModSecurity rules as is.
+Ideal if you're dealing with aggressive bots or scrapers that impact your site performance.
+Good option if you want to prevent illegitimate AI crawlers from visiting your site.
 
 **How it works:**
-- Deploy CrowdSec Security Engine with AppSec module on your reverse proxy or web server.
-- Get CrowdSec Virtual patching collection.
-- Easily scale and identify behaviors accross multiple servers over time.
-- Go further by using your existing appsec rules.
-- Even test CRS rules out of band on your production traffic to easily adapt them to you needs.
-
+- Retrieve AI Crawlers and/or Botnets IPs from CrowdSec Blocklist integrations
+- Block at the edge using your firewall or CDN.  
 
 **References**
-- ...
+- [Blocking at the edge section](#blocking-at-the-edge)
+- [Custom scenario creation](/docs/next/scenarios/create)
+- [AI Crawlers Blocklist ↗️](https://app.crowdsec.net/blocklists/67b3524151bbde7a12b60be0)
+- [Currated Botnet Actors ↗️](https://app.crowdsec.net/blocklists/65a56c160469607d9badb813)
+- [Public Internet Scanners ↗️](https://app.crowdsec.net/blocklists/65f972eb807e06de7a0e3e65)
 
 ---
 
-## Bot and Scraper Management
+## Block Common web attacks fast
 
-Control aggressive crawlers and scraping tools while preserving legitimate user access using graduated response strategies.  
+Quickly protect web applications from the latest CVEs and generic vulnerability exploits using CrowdSec WAF.
 
 **Is it for me?**
-Ideal if you're dealing with aggressive bots or scrapers that impact your site performance.
-Good option if you need granular control over automated traffic without blocking legitimate users or search engines.
+Ideal if you want a modern OpenSource WAF solution.  
+Benefit from CrowdSec's Virtual patching catalog while being able to use your existing ModSecurity rules as is.
 
 **How it works:**
-- Configure behavioral detection scenarios to identify suspicious crawling patterns.
-- Implement graduated responses starting with throttling, escalating to temporary bans.
-- Use specialized AI Crawlers Blocklist to block known malicious crawling IPs.
-- Deploy edge blocking through firewall or CDN integration for immediate protection.
+- Deploy CrowdSec Security Engine with AppSec module on your reverse proxy or web server.
+- Get CrowdSec Virtual patching collection.
+- Easily scale and identify behaviors accross multiple servers over time.
+- Go further by using your existing appsec rules.
+- Even test CRS rules out of band on your production traffic to easily adapt them to you needs.
+
 
 **References**
-- [Import throttle decisions](/docs/next/cscli/cscli_decisions_import)
-- [Custom scenario creation](/docs/next/scenarios/create)
-- [AI Crawlers Blocklist subscription](/u/console/blocklists/subscription/)
-- [Edge integration options](/u/integrations/intro)
-- [Behavioral detection configuration](/docs/next/scenarios/introduction)
+- [Security Engine installation](/u/getting_started/intro)
+- [CrowdSec WAF presentation](/appsec/intro)
+- [Virtual Patching collection ↗️](https://app.crowdsec.net/hub/author/crowdsecurity/collections/appsec-virtual-patching)
+- [CrowdSec WAF article ↗️](https://www.crowdsec.net/blog/crowdsec-waf-the-collaborative-future-of-web-application-security)
 
 ---