Index: pages/filters.html |
diff --git a/pages/filters.html b/pages/filters.html |
index c10c8b5a912dba2419ddda87be520ff5771d97b7..8baf71fc9eb833e0239a4c77cec862a3a477ad1e 100644 |
--- a/pages/filters.html |
+++ b/pages/filters.html |
@@ -17,7 +17,7 @@ title=Writing Adblock Plus filters |
<h3 id="whitelist">{{s8 Defining exception rules}}</h3> |
- <p>{{s9 Sometimes you will notice that one of your filters that is usually working quite well blocks in some case blocks something that it shouldn't be blocking. You don't want to remove this filter but you still don't want it to match in this one case.}}</p> |
+ <p>{{s9 Once in a while you may notice that one of your filters, that normally works well, is blocking something that it shouldn't block. You don't want to remove this filter but you still don't want it to match in this one case.}}</p> |
juliandoucette
2017/02/21 15:24:08
This change doesn't match the change proposed in t
juliandoucette
2017/04/05 11:47:29
1. Please reply to comments inline instead of usin
|
<p>{{s10 That's what exception rules are good for — they allow you to define cases where filters shouldn't be applied. For example if you are unhappy with your filter <code><fix>adv</fix></code> blocking <code><fix>http://example.com/advice.html</fix></code>, you can define an exception rule <code><fix>@@advice</fix></code>. Exception rules are no different from filter rules, you can use wildcards or regular expressions. You only have to precede them by <code><fix>@@</fix></code> to indicate an exception rule.}}</p> |