diff --git a/_posts/2015-10-18-tip-opening-and-closing-ports-needed-by-a-systemd-service.markdown b/_posts/2015-10-18-tip-opening-and-closing-ports-needed-by-a-systemd-service.markdown
index c997778..2bc16d6 100644
--- a/_posts/2015-10-18-tip-opening-and-closing-ports-needed-by-a-systemd-service.markdown
+++ b/_posts/2015-10-18-tip-opening-and-closing-ports-needed-by-a-systemd-service.markdown
@@ -25,10 +25,10 @@ I didn't feel comfortable to give this user control the firewall. However, the s
 
 > Takes a boolean argument. If true, the permission-related execution options, as configured with User= and similar options (see systemd.exec(5) for more information), are only applied to the process started with ExecStart=, and not to the various other ExecStartPre=, ExecStartPost=, ExecReload=, ExecStop=, and ExecStopPost= commands. If false, the setting is applied to all configured commands the same way. Defaults to false.
 
+
 Exactly what I needed! And thus, I amended the unit file as follows:
 
 ````systemd
-
 [Unit]
 Description=Mumble Server (Murmur)
 Requires=network-online.target