Fix a couple formatting issues.

ipfs.md

@@ -15,6 +15,7 @@ These instructions are going to require a bit of elbow grease in the command lin
 - Start your demon.
 - Pin the directory resolved by way of IPNS.
 
+
 ### Installing the Daemon
 
 This step will vary, depending on how your distribution packages things. Here are some of the common ones that I did a bit of research for.
@@ -26,6 +27,7 @@ Void Linux
 Slint/Slackware and Other Distros I Hadn't Thought of
 : Consult the instructions at: <https://github.com/ipfs/kubo>
 
+
 ### Initializing your Daemon
 
 This is pretty easy, all you need to do here is:
@@ -34,6 +36,7 @@ This is pretty easy, all you need to do here is:
 ipfs init
 ```
 
+
 ### Opening the Ports
 
 In order for your node to be able to talk to other nodes on the IPFS network, you will need to allow port 4001/tcp and 4001/udp through your firewall. In addition, you may also need to forward those ports to the box should UPNP not be working.
@@ -46,6 +49,7 @@ For some distributions, a user service is already shipped, so starting the daemo
 ipfs daemon
 ```
 
+
 ### Sync the Archive
 
 Now that yu have the IPFS node running, you can now get the archive and pin a copy locally by way of its IPNS key.
@@ -54,12 +58,14 @@ Now that yu have the IPFS node running, you can now get the archive and pin a co
 ipfs pin add /ipns/k51qzi5uqu5dg7ndb48x1v9hzp98vg6wncrbhps16a8yn3eh4nqis7v384jh20
 ```
 
+
 To ensure you have the latest archive, run the pin on a periodic interval. Additionally, if your node is slow in updating, as mine was, you can resolve the resolve the ipns entry by hand and pipe that into pin add.
 
 ```bash
 ipfs name resolve --nocache /ipns/k51qzi5uqu5dg7ndb48x1v9hzp98vg6wncrbhps16a8yn3eh4nqis7v384jh20 | ipfs pin add
 ```
 
+
 To automate this process, you can add it to your crontab:
 
 ```bash