From 143dc6d1980cf5417a62386b4cb613f16289250f Mon Sep 17 00:00:00 2001
From: Egbert <10352354+egberts@users.noreply.github.com>
Date: Sun, 20 Sep 2020 18:26:10 -0400
Subject: [PATCH] Updated Developing Regex in Fail2ban (markdown)

---
 Developing-Regex-in-Fail2ban.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Developing-Regex-in-Fail2ban.md b/Developing-Regex-in-Fail2ban.md
index ad850b3..123bc49 100644
--- a/Developing-Regex-in-Fail2ban.md
+++ b/Developing-Regex-in-Fail2ban.md
@@ -1,6 +1,6 @@
 So, you’re eager to write a new fail2ban filter and it failed … miserably or you have a new case but unsure how to get the best regex ... fastest.
 
-If the `fail2ban` couldn’t match anything … regardless of whether it is standard fail2ban config or your highly, purportedly, hapzardly-concoted filter config file: this page is for you.
+If the `fail2ban` couldn’t match anything … regardless of whether it is standard fail2ban config or your highly, purportedly, hapzardly-concoted filter config file but you're a Regex expert: this page is for you.
 
 That is what this page offers, specifically developing as well as troubleshooting Regex used by `fail2ban`.