diff --git a/src/blog/8.14.25.md b/src/blog/8.14.25.md
index 747ab89..3d16006 100644
--- a/src/blog/8.14.25.md
+++ b/src/blog/8.14.25.md
@@ -14,15 +14,16 @@ image: "/assets/images/8.14.25/junos+opnsense.jpg"
 <br/>
 Most people know that DHCP (Dynamic Host Configuration Protocol) is a protocol used to dynamically allocate IP addresses. But did you know that it can be used to configure other host device settings? Network device vendors like Junip... *ermm*, HPE Networking... take advantage of DHCP to implement "Zero Touch Provisioning" and even perform software upgrades for out-of-the-box devices. Here I will show you how to use OPNsense with Dnsmasq DHCP to "auto-provision" your Junos devices.
 
+---
 
 ## Requirements
 
-* An OPNsense device with Dnsmasq DHCP enabled<sup>[[1]](#bottom)</sup>
-* An understanding of OPNsense firewall rules<sup>[[2]](#bottom)</sup>
-* An (S)FTP server in your network reachable by the Junos devices
-* A Junos base configuration file saved on the (S)FTP server.
-* At least one zeroized Junos device
-* A hex converter. [Link to the one I used here](https://www.rapidtables.com/convert/number/ascii-to-hex.html).<sup>[[3]](#bottom)</sup>
+* At least one zeroized Junos device.
+* A Junos base configuration file saved on an (S)FTP server.
+* An (S)FTP server in your network reachable by the Junos device(s).
+* An OPNsense device with Dnsmasq DHCP enabled<sup>[[1]](#bottom)</sup>.
+* An understanding of OPNsense firewall rules<sup>[[2]](#bottom)</sup>.
+* A hex converter. [Link to the one I used here](https://www.rapidtables.com/convert/number/ascii-to-hex.html).<sup>[[3]](#bottom)</sup>.
 
 ---