diff --git a/docs/applications/singularity.md b/docs/applications/singularity.md
index 07d0d70..b3fec0c 100644
--- a/docs/applications/singularity.md
+++ b/docs/applications/singularity.md
@@ -82,7 +82,8 @@ In this example, singularity will be used to run an instance of the [deepvariant
 
 To pull the docker container:
 
-```module load singularity/3.8.3
+```
+module load singularity/3.8.3
 singularity pull --name deepvariant-1.3.0.sif docker://google/deepvariant:1.3.0
 ```
 The singularity image is located in the install directory:
@@ -183,4 +184,4 @@ FAQ
 
 ### Why can't I use Docker?
 
-Docker images are not secure becuase they allow users to gain root access to the compute nodes. Singularity effectively runs as the user running the command, and does not result in elevated access. Also, docker interacts with the slurm job scheduler in a way that causes resource requests and usages to not match up, making it difficult to keep job queueing fair for all users. In that the clusters are multi-user systems, we want to make sure people can work without worry that others are accessing their data or unfairly using up resources.
\ No newline at end of file
+Docker images are not secure becuase they allow users to gain root access to the compute nodes. Singularity effectively runs as the user running the command, and does not result in elevated access. Also, docker interacts with the slurm job scheduler in a way that causes resource requests and usages to not match up, making it difficult to keep job queueing fair for all users. In that the clusters are multi-user systems, we want to make sure people can work without worry that others are accessing their data or unfairly using up resources.