From 7eb9091bdb5b31278d69dd7c8ebd6197e804fb13 Mon Sep 17 00:00:00 2001
From: gorhill <rhill@raymondhill.net>
Date: Mon, 6 Oct 2014 12:49:40 -0700
Subject: [PATCH] Updated Dynamic filtering (markdown)

---
 Dynamic-filtering.md | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/Dynamic-filtering.md b/Dynamic-filtering.md
index 6d26d97..d39517b 100644
--- a/Dynamic-filtering.md
+++ b/Dynamic-filtering.md
@@ -38,4 +38,10 @@ So in the illustration above we have:
     - Block inline `<script>` tags
     - Do not block 3rd-party `<script>` tags
 
-The user interface is not terribly self-explanatory, but I really want to keep it as uncluttered as possible. Once you read the doc here, using dynamic filtering should require no further explanation.
\ No newline at end of file
+The user interface is not terribly self-explanatory, but I really want to keep it as uncluttered as possible. Once you read the doc here, using dynamic filtering should require no further explanation.
+
+Network requests blocked through dynamic filtering will be reported just as any other in the request log:
+
+![Figure 3](https://raw.githubusercontent.com/gorhill/uBlock/master/doc/img/dynamic-filtering-3.png)
+
+Dynamic filters are always deemed important, thus they will show up with the `important` filter option attached to them. When a network request is blocked because of a dynamic filtering default setting, the hostname will be reported as `*`, as seen in the picture above.
\ No newline at end of file