From 8edab352eb043daa8b787e97808ff06f10def1c5 Mon Sep 17 00:00:00 2001
From: Egbert <10352354+egberts@users.noreply.github.com>
Date: Wed, 30 Sep 2020 19:01:21 -0400
Subject: [PATCH] Updated Developing Regex in Fail2ban (markdown)

---
 Developing-Regex-in-Fail2ban.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Developing-Regex-in-Fail2ban.md b/Developing-Regex-in-Fail2ban.md
index 3bf7253..8ff14dc 100644
--- a/Developing-Regex-in-Fail2ban.md
+++ b/Developing-Regex-in-Fail2ban.md
@@ -114,7 +114,9 @@ Sadly, latest Bind9 daemon has no configurable field to suppress these false DNS
 
 FIRST PATTERN, FIRST
 ====================
-Hopefully you got that ‘date’ hit. `fail2ban` already provided MANY `datepattern` found in many log files.  Execute something like `fail2ban-regex -v` (please note the important '`-v`' command line option):
+Hopefully you got that ‘date’ hit. `fail2ban` already provided for MANY `datepattern` found in many log files.  
+
+Execute something like `fail2ban-regex -v` (please note the important '`-v`' command line option):
 ```bash
 fail2ban-regex -v /tmp/captured.log /etc/fail2ban/filter.d/named-refused.conf
 ```