From a49e78b7ca40372c8f2a8809ce1425f11b9f0d8d Mon Sep 17 00:00:00 2001
From: gorhill <rhill@raymondhill.net>
Date: Sat, 25 Oct 2014 10:43:45 -0700
Subject: [PATCH] Updated Dynamic filtering (markdown)

---
 Dynamic-filtering.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Dynamic-filtering.md b/Dynamic-filtering.md
index b438f9b..c0e17ad 100644
--- a/Dynamic-filtering.md
+++ b/Dynamic-filtering.md
@@ -2,7 +2,9 @@ Dynamic filtering, introduced in version 0.7.0.0, allows a user to filter dynami
 
 This feature is not suited for users who like an install-and-forget blocker. Thus it is tucked away by default, and all dynamic filters are turned off by default.
 
-**Dynamic filtering is targeted toward users who wish to have that additional bit of control about where their browser is allowed to connect and what it is allowed to execute, see it as a _extremely_ simplified (yet useful) _NoScript_ or _HTTP Switchboard_.**
+**DO NOT USE IF YOU DO NOT UNDERSTAND HOW IT WORKS.**
+
+Dynamic filtering is targeted toward users who wish to have that additional bit of control about where their browser is allowed to connect and what it is allowed to execute, see it as a _extremely_ simplified (yet useful) _NoScript_ or _HTTP Switchboard_.
 
 Dynamic filtering is a useful feature security-wise. For example, blocking 3rd-party `<iframe>` by default would have protected users in the case of the [jQuery.com malware attack](http://www.riskiq.com/resources/blog/jquerycom-malware-attack-puts-privileged-enterprise-it-accounts-risk). Disabling inline javascript is also often useful to work around anti-blockers on some sites. Using dynamic filtering can help speed up _significantly_ how fast web pages load.