diff --git a/docs.it4i/software/tools/singularity.md b/docs.it4i/software/tools/singularity.md
index 3c9142a07b55aa94a50130a696662cc4e40492af..fd3003b3e7b1a8bbd4f084d01d9b47bfd3540c89 100644
--- a/docs.it4i/software/tools/singularity.md
+++ b/docs.it4i/software/tools/singularity.md
@@ -63,7 +63,7 @@ Cleaning up...
 
 ## Launching the Container
 
-The interactive shell can be invoked by the **shell** command. This is useful for development purposes. To make changes inside the container permanent use **-w | --writable** option.
+The interactive shell can be invoked by the `singularity shell` command. This is useful for development purposes. To make changes inside the container permanent use `-w | --writable` option.
 
 ```console
 hra0031@login4:~$ singularity shell -w ubuntu.img
@@ -76,7 +76,7 @@ DISTRIB_CODENAME=xenial
 DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"
 ```
 
-To execute command inside container (without interactive shell) use **exec** command.
+To execute command inside container (without interactive shell) use `singularity exec` command.
 
 ```
 hra0031@login4:~$ singularity exec ubuntu.img cat /etc/lsb-release
@@ -86,7 +86,7 @@ DISTRIB_CODENAME=xenial
 DISTRIB_DESCRIPTION="Ubuntu 16.04.3 LTS"
 ```
 
-Singularity image can contain a runscript. This script is executed inside container after the **run** command is used. The runscript is mostly used to run an application for which is the container build, in the following example it is **fortune | cowsay** command.
+Singularity image can contain a runscript. This script is executed inside container after the `singularity run` command is used. The runscript is mostly used to run an application for which is the container build, in the following example it is **fortune | cowsay** command.
 
 ```
 hra0031@login4:~$ singularity run ubuntu.img
@@ -102,7 +102,7 @@ hra0031@login4:~$ singularity run ubuntu.img
 
 ## Accessing /HOME and /SCRATCH Within Container
 
-By default, user home directory is mounted inside the container, therefore you can access your files directly. If you need access to **/SCRATCH** storage for your computation, this must by mounted be **-B | --bind** option.
+By default, user home directory is mounted inside the container, therefore you can access your files directly. If you need access to **/SCRATCH** storage for your computation, this must be mounted by `-B | --bind` option.
 
 !!!Warning
       Be aware, that the mounted folder has to exist inside the container or the container image has to be writable!