From 29f6e6093bccb31aa2811ad83ce42409d1c6eb52 Mon Sep 17 00:00:00 2001
From: Ruben van Staveren <ruben@verweg.com>
Date: Mon, 9 Jan 2023 15:01:06 +0000
Subject: [PATCH] Missed a spot

---
 README.md | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index a645aab..cea12bc 100644
--- a/README.md
+++ b/README.md
@@ -62,12 +62,14 @@ _Of course you can listen on ipv4/ipv6 but you want to protect these addresses f
 
 * Place anchors in pf for jail2ban to use. You probably want to place the early in your existing pf configuration
 
-     anchor "f2b/*"
-     anchor f2b-jail {
-          anchor "jail1_fqdn" to { <addr_jail1>, <addr_extra_jail1>, <addr_extra6_jail1> }
-         anchor "jail2_fqdn" to { <addr_jail2>, <addr_extra_jail2>, <addr_extra6_jail2> }
-         anchor "jail3_fqdn" to { <addr_jail3>, <addr_extra_jail3>, <addr_extra6_jail3> }
-     }
+```
+anchor "f2b/*"
+anchor f2b-jail {
+    anchor "jail1_fqdn" to { <addr_jail1>, <addr_extra_jail1>, <addr_extra6_jail1> }
+    anchor "jail2_fqdn" to { <addr_jail2>, <addr_extra_jail2>, <addr_extra6_jail2> }
+    anchor "jail3_fqdn" to { <addr_jail3>, <addr_extra_jail3>, <addr_extra6_jail3> }
+}
+```
 
 Having seperate anchors per jail makes it possible to have fine grained
 blocking: Something that is harmful to jail2 might be perfectly legit for jail2.