From b216a8dd4d7e2287e69a14e516e486432b1040a7 Mon Sep 17 00:00:00 2001
From: shamoon <4887959+shamoon@users.noreply.github.com>
Date: Sat, 30 Dec 2023 08:53:26 -0800
Subject: [PATCH] Update usage.md

---
 docs/usage.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/docs/usage.md b/docs/usage.md
index e3897a9e0..69769f9de 100644
--- a/docs/usage.md
+++ b/docs/usage.md
@@ -274,12 +274,13 @@ fields and permissions, which will be merged.
 
 Currently, there are three events that correspond to workflow trigger 'types':
 
-1. Consumption: _before_ a document is consumed, so events can include filters by source (mail, consumption
+1. **Consumption**: _before_ a document is consumed, so events can include filters by source (mail, consumption
    folder or API), file path, file name, mail rule
-2. Added: _after_ a document is added. At this time, file path and source information is no longer available,
-   but the document has had document type, tags, etc. assigned so these can now be used for filtering.
-3. Updated: when a document is updated. Similar to 'added' events, triggers can include filtering by tags, doc
-   type, or correspondent.
+2. **Added**: _after_ a document is added. At this time, file path and source information is no longer available,
+   but the document content has been extracted and metadata such as document type, tags, etc. have been set, so these can now
+   be used for filtering.
+3. **Updated**: when a document is updated. Similar to 'added' events, triggers can include filtering by content matching, tags,
+   doc type, or correspondent.
 
 The following flow diagram illustrates the three trigger types: