From 590eef0d44d0c052b6f67609077993e7655bf4f0 Mon Sep 17 00:00:00 2001
From: Matteo Luppi <100372313+lups2000@users.noreply.github.com>
Date: Wed, 28 Feb 2024 23:04:45 +0100
Subject: [PATCH] fix docs (#6696)

#### Description

close #6682

#### Checklist

 - [ ] I have updated tests where applicable.
 - [ ] I have added an entry to the CHANGELOG.
---
 docs/src/content/howto-ignoredomains.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/docs/src/content/howto-ignoredomains.md b/docs/src/content/howto-ignoredomains.md
index bcdff4f07..a5954717e 100644
--- a/docs/src/content/howto-ignoredomains.md
+++ b/docs/src/content/howto-ignoredomains.md
@@ -15,9 +15,7 @@ mitmproxy's interception mechanism:
   and mitmproxy's interception leads to errors. For example, the Twitter app,
   Windows Update or the Apple App Store fail to work if mitmproxy is active.
 - **Convenience:** You really don't care about some parts of the traffic and
-  just want them to go away. Note that mitmproxy's "Limit" option is often the
-  better alternative here, as it is not affected by the limitations listed
-  below.
+  just want them to go away. Note that mitmproxy's [view_filter]({{< relref "concepts-options/#view_filter" >}}) option is often the better alternative here, as it is not affected by the limitations listed below.
 
 If you want to peek into (SSL-protected) non-HTTP connections, check out the
 **tcp_proxy** feature. If you want to ignore traffic from mitmproxy's processing