diff --git a/Home.md b/Home.md
index d1e6668..2a6b514 100644
--- a/Home.md
+++ b/Home.md
@@ -17,7 +17,7 @@
   - [Fail2ban does not ban and logs include iptables v...: unknown option "-w"](How-fail2ban-works)
 
 * #### Configuration
-  - [Proper fail2ban configuration](Properly-fail2ban-configuration)
+  - [Proper fail2ban configuration](Proper-fail2ban-configuration)
   - [Fail2ban Troubleshooting](Troubleshooting)
   - [How fail2ban substitution resp. runtime interpolation works](How-fail2ban-substitution-resp.-runtime-interpolation-works)
 ---
diff --git a/How-fail2ban-works.md b/How-fail2ban-works.md
index 117d10a..ad1faff 100644
--- a/How-fail2ban-works.md
+++ b/How-fail2ban-works.md
@@ -3,14 +3,14 @@ But you can write resp. configure your own action to [ban something other as hos
 
 Fail2Ban comes out-of-the-box ready to read many standard log files, such as those for sshd and Apache, and is easy to configure to read any log file you choose, for any error you choose.
 
-**But fail2ban is just a tool, so it should be [properly configured](Properly-fail2ban-configuration).**
+**But fail2ban is just a tool, so it should be [properly configured](Proper-fail2ban-configuration).**
 
 ***
 **[Q]** Fail2ban does not detect some authentication failures resp. banning does not occurred
 <details><summary>Answer</summary>
 
 **[A]** There can be many reasons:
-- corresponding jail for scanning the log file or systemd journal is not enabled (or idle). See [here](Properly-fail2ban-configuration) how the jail can be enabled.
+- corresponding jail for scanning the log file or systemd journal is not enabled (or idle). See [here](Proper-fail2ban-configuration) how the jail can be enabled.
 - the proper path to the log files (parameter `logpath`) resp. proper journal control parameter `journalmatch` should be set for this jail.
 - the IP goes to ban if it makes at least `maxretry` failures within `findtime` seconds. So if you've configured `maxretry=5` and `findtime=10m` (default values) then it needs at least 5 failures (5 attempts) within 10 minutes to ban an IP.<br/>
 Each failure (attempt) will be logged in `fail2ban.log` as:<br/>
diff --git a/Properly-fail2ban-configuration.md b/Proper-fail2ban-configuration.md
similarity index 100%
rename from Properly-fail2ban-configuration.md
rename to Proper-fail2ban-configuration.md
diff --git a/Troubleshooting.md b/Troubleshooting.md
index 7a01d86..978902c 100644
--- a/Troubleshooting.md
+++ b/Troubleshooting.md
@@ -1,4 +1,4 @@
-Please read [proper fail2ban configuration](Properly-fail2ban-configuration) carefully before and follow the instructions there.<br/>
+Please read [proper fail2ban configuration](Proper-fail2ban-configuration) carefully before and follow the instructions there.<br/>
 Many issues are configuration-related and can be relative easy rectified by the adjustment of the configuration.
 
 ***
diff --git a/_Sidebar.md b/_Sidebar.md
index 1fe767c..9b8176c 100644
--- a/_Sidebar.md
+++ b/_Sidebar.md
@@ -6,6 +6,6 @@
 ---
 ### FAQ
 * #### Configuration
-  - [Proper fail2ban configuration](Properly-fail2ban-configuration)
+  - [Proper fail2ban configuration](Proper-fail2ban-configuration)
   - [Fail2ban Troubleshooting](Troubleshooting)
   - [How fail2ban substitution resp. runtime interpolation works](How-fail2ban-substitution-resp.-runtime-interpolation-works)
\ No newline at end of file