diff --git a/6.-jail.local.md b/06.-jail.local.md
similarity index 97%
rename from 6.-jail.local.md
rename to 06.-jail.local.md
index f06dec4..29f49c7 100644
--- a/6.-jail.local.md
+++ b/06.-jail.local.md
@@ -59,7 +59,7 @@ This is where you tell F2B exactly what to do when it finds a reason to ban a sy
 
 '*action*' is performed each time a system should be banned.  There are several predefined actions listed in the *jail.conf* file which you can use and are often sufficient for most setups.  Read the comments in that file to understand what each predefined action does.  In my case, I like getting an email along with a few lines from the log telling me what they did to get banned.
 
-Within '*action*' is '*banaction*' which is a link over to a specific configuration file telling F2B what to do on the system to enforce the ban.  In this setup, we direct F2B to look at the ufw.conf file to see how to modify UFW's rules so it drops packets from the offending system.  [Details here](https://git.asifbacchus.app/asif/fail2banUFW/wiki/9.-UFW-action-file).
+Within '*action*' is '*banaction*' which is a link over to a specific configuration file telling F2B what to do on the system to enforce the ban.  In this setup, we direct F2B to look at the ufw.conf file to see how to modify UFW's rules so it drops packets from the offending system.  [Details here](https://git.asifbacchus.app/asif/fail2banUFW/wiki/09.-UFW-action-file).
 
 The general setup as described above is as follows: