From ebf3a1086cab7ba21cac1fd897a1154d68176bb0 Mon Sep 17 00:00:00 2001
From: David Maisonave <47364845+David-Maisonave@users.noreply.github.com>
Date: Tue, 13 Aug 2024 03:39:17 -0400
Subject: [PATCH] Update README.md

---
 plugins/FileMonitor/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/plugins/FileMonitor/README.md b/plugins/FileMonitor/README.md
index 2587e5c..82332c4 100644
--- a/plugins/FileMonitor/README.md
+++ b/plugins/FileMonitor/README.md
@@ -91,8 +91,8 @@ To configure the schedule or to add new task, edit the **task_scheduler** sectio
       - Starts a (**plugin**) task every 30 minutes.
         - `{"task" : "Create Tags", "pluginId" : "pathParser", "minutes" : 30},`
     - The frequency field does support **days** and **seconds**.
-      - seconds is mainly used for test purposes.
-      - The use of days is discourage, because it only works if FileMonitor is running for X many days non-stop.
+      - **seconds** is mainly used for test purposes.
+      - The use of **days** is discourage, because it only works if FileMonitor is running for X many days non-stop.
         - For example, if days is used with 30 days, FileMonitor would have to be running non-stop for 30 days before the task is activated. If it's restarted at any time durring the 30 days, the count down restarts.
         - It's recommended to use weekday based syntax over using days, because many restarts can occur durring the week or month, and the task will still get started as long as FileMonitor is running durring the scheduled activation time.
   - **weekday Based**