From ad4150741a7c7f88baa6d8dae95afa437287893f Mon Sep 17 00:00:00 2001
From: Chris Caron <lead2gold@gmail.com>
Date: Fri, 15 Feb 2019 15:33:14 -0500
Subject: [PATCH] Updated Development_API (markdown)

---
 Development_API.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/Development_API.md b/Development_API.md
index fb2094f..b074c50 100644
--- a/Development_API.md
+++ b/Development_API.md
@@ -72,9 +72,8 @@ apobj.notify(
 #### Leverage Tagging
 If you associated tags with your notification services when you called **add()** earlier, you can leverage it's full potential through the **notify()** function here. Tagging however allows you to trigger notifications only when a criteria is met. The tagging logic can be interpreted as follows:
 
-| apprise.notify(tag=**match**)  | Tag Representation       |
-| -------------------------------- | ------------------------ |
-| _None_                           |  All Notifications (_this is the default_)
+| apprise.notify(tag=_match_)      | Notify Services Having Tag(s): |
+| -------------------------------- | ------------------------------ |
 | "TagA"                           |  TagA
 | "TagA, TagB"                     |  TagA **OR** TagB
 | ['TagA', 'TagB']                 |  TagA **OR** TagB