mirror of
https://github.com/gorhill/uBlock.git
synced 2024-11-10 01:02:08 +01:00
removed paragraph rendered obsolete by fix to #101
This commit is contained in:
parent
c197d10055
commit
a040045808
1 changed files with 0 additions and 8 deletions
|
@ -44,14 +44,6 @@ To benefit from the higher efficiency, it is of course not advised to use an
|
|||
inefficient blocker at the same time. µBlock will do as well or better than the
|
||||
popular blockers out there.
|
||||
|
||||
If you install µBlock along another blocker, µBlock will likely show less requests
|
||||
blocked than the other blocker. You might want to [read this](https://github.com/gorhill/uBlock/wiki/Tricks-and-tips#easy-way-to-find-out-what-other-blockers-do-not-block-what-they-should-block)
|
||||
for the explanation.
|
||||
TL;DR: when used along with another blocker, µBlock typically will block and show
|
||||
you what the other blocker **did not** block. If µBlock is used as the lone blocker,
|
||||
it will block everything the other blocker would have blocked,
|
||||
[and more](https://github.com/gorhill/uBlock/wiki/%C2%B5Block-and-others:-Blocking-ads,-trackers,-malwares).
|
||||
|
||||
## Documentation
|
||||
|
||||
I think it is pretty obvious, except for this I suppose:
|
||||
|
|
Loading…
Reference in a new issue