Travis build: 27

manuscript/ha-docker-swarm/docker-swarm-mode.md

@@ -62,13 +62,13 @@ To add a manager to this swarm, run the following command:
 Run the command provided on your second node to join it to the swarm as a manager. After adding the second node, the output of ```docker node ls``` (on either host) should reflect two nodes:
 
 
-````
+```
 [root@ds2 davidy]# docker node ls
 ID                           HOSTNAME                STATUS  AVAILABILITY  MANAGER STATUS
 b54vls3wf8xztwfz79nlkivt8    ds1.funkypenguin.co.nz  Ready   Active        Leader
 xmw49jt5a1j87a6ihul76gbgy *  ds2.funkypenguin.co.nz  Ready   Active        Reachable
 [root@ds2 davidy]#
-````
+```
 
 Repeat the process to add your third node.
 

manuscript/ha-docker-swarm/registry.md

@@ -103,9 +103,9 @@ To:
 ```
 
 Then restart docker by running:
-````
+```
 systemctl restart docker-latest
-````
+```
 
 !!! tip ""
     Note the extra comma required after "false" above

manuscript/ha-docker-swarm/shared-storage-gluster.md

@@ -55,7 +55,7 @@ mount -a && mount
 Atomic doesn't include the Gluster server components.  This means we'll have to run glusterd from within a container, with privileged access to the host. Although convoluted, I've come to prefer this design since it once again makes the OS "disposable", moving all the config into containers and code.
 
 Run the following on each host:
-````
+```
 docker run \
    -h glusterfs-server \
    -v /etc/glusterfs:/etc/glusterfs:z \
@@ -67,7 +67,7 @@ docker run \
    --restart=always \
    --name="glusterfs-server" \
    gluster/gluster-centos
-````
+```
 ### Create trusted pool
 
 On a single node (doesn't matter which), run ```docker exec -it glusterfs-server bash``` to launch a shell inside the container.