From eeff301079d3adcc1baebe4965e4e799bb4ad96f Mon Sep 17 00:00:00 2001
From: Dmitry Seregin <105th@users.noreply.github.com>
Date: Fri, 4 Aug 2023 14:51:41 +0400
Subject: [PATCH] Update docs/general/ad-filtering/create-own-filters.md

Co-authored-by: Nikita Gorskikh <57908117+ngorskikh@users.noreply.github.com>
---
 docs/general/ad-filtering/create-own-filters.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/general/ad-filtering/create-own-filters.md b/docs/general/ad-filtering/create-own-filters.md
index dfda07f2eba..b19d612a76e 100644
--- a/docs/general/ad-filtering/create-own-filters.md
+++ b/docs/general/ad-filtering/create-own-filters.md
@@ -608,7 +608,7 @@ The rule corresponds to the main frame document requests, i.e. HTML documents th
 
 By default, AdGuard does not block the requests that are loaded in the browser tab (e.g. "main frame bypass"). The idea is not to prevent pages from loading as the user clearly indicated that they want this page to be loaded. However, if the `$document` modifier is specified explicitly, AdGuard does not use that logic and prevents the page load. Instead, it responds with a "blocking page".
 
-When used with an exclusion rule (`@@`), this modifier completely disables blocking on the corresponding pages. It is equivalent to using the `$elemhide`, `$content`, `$urlblock`, `$jsinject`, `$extension` modifiers simultaneously, but only if this modifier is written in the rule and not added hidden, for example in the rule `@@example.com$removeheader`, which implicitly adds `$document`.
+When used with an exclusion rule (`@@`), this modifier completely disables blocking on the corresponding pages. It is equivalent to using the `$elemhide`, `$content`, `$urlblock`, `$jsinject`, `$extension` modifiers simultaneously, but only if this modifier is written in the rule and not added implicitly, for example in the rule `@@example.com$removeheader`, which implicitly adds `$document`.
 
 **Examples**