From 70da54a3aa6e78a47e626f35723ef7cdd957d2ad Mon Sep 17 00:00:00 2001
From: Raymond Hill <gorhill@users.noreply.github.com>
Date: Fri, 21 Aug 2015 09:47:44 -0400
Subject: [PATCH] Updated Dynamic filtering: Benefits of blocking 3rd party
 iframe tags (markdown)

---
 ...mic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Dynamic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md b/Dynamic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md
index 798d99d..063c8c4 100644
--- a/Dynamic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md
+++ b/Dynamic-filtering:-Benefits-of-blocking-3rd-party-iframe-tags.md
@@ -6,7 +6,7 @@
 
 ### Malware protection
 
-`iframe` tags are very often used by malware code on compromised web sites. The most recent example of this is ~~[jquery.com](http://blog.jquery.com/2014/09/24/update-on-jquery-com-compromises/)~~ [Firefox's javascript-based PDF reader](https://blog.mozilla.org/security/2015/08/06/firefox-exploit-found-in-the-wild/).
+`iframe` tags are very often used by malware code on compromised web sites. A recent example of this is ~~[jquery.com](http://blog.jquery.com/2014/09/24/update-on-jquery-com-compromises/)~~ [Firefox's javascript-based PDF reader](https://blog.mozilla.org/security/2015/08/06/firefox-exploit-found-in-the-wild/).
 
 Using 3rd-party-sourced `<iframe>` to inject exploit on a user's computer is quite a common technique: