From 3e619557444afe96f598246570db9d3623fe1388 Mon Sep 17 00:00:00 2001
From: gorhill <rhill@raymondhill.net>
Date: Tue, 7 Oct 2014 07:07:30 -0700
Subject: [PATCH] Updated Dynamic filtering (markdown)

---
 Dynamic-filtering.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Dynamic-filtering.md b/Dynamic-filtering.md
index ddeda87..70f67a0 100644
--- a/Dynamic-filtering.md
+++ b/Dynamic-filtering.md
@@ -1,6 +1,6 @@
 Dynamic filtering, introduced in version 0.7.0.0, allows a user to filter dynamically certain classes of requests. Currently, `script` and `iframe` objects can be dynamically filtered, i.e. filtered on or off without having to create a custom filter.
 
-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 behavior on some sites.
+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.
 
 Of course, blocking portion of a page may cause page breakage, sometimes benign, sometimes severe. It is up to the user to choose how to make use of this feature.