diff --git a/crowdsec-docs/unversioned/getting_started/post_installation/whitelists.mdx b/crowdsec-docs/unversioned/getting_started/post_installation/whitelists.mdx
index 4504595fe..7a6d35ae4 100644
--- a/crowdsec-docs/unversioned/getting_started/post_installation/whitelists.mdx
+++ b/crowdsec-docs/unversioned/getting_started/post_installation/whitelists.mdx
@@ -13,7 +13,7 @@ By default CrowdSec will whitelist private LAN IP addresses via [this parser](ht
 
 In this guide we will cover how to create some whitelists and how to apply them to your CrowdSec instance.
 
-However, we can't cover every possible use case, so if you have a specific one that isn't covered here, please refer to [detailed whitelist documentation](/docs/next/whitelist/intro)
+However, we can't cover every possible use case, so if you have a specific one that isn't covered here, please refer to [detailed whitelist documentation](/docs/next/log_processor/whitelist/intro)
 
 :::info
 We use "event" as a term to describe a log line that is currently being processed by CrowdSec. An "event" can be a log line from a log file, or an "overflow" from a scenario.