diff --git a/docs.it4i/software/debuggers/allinea-ddt.md b/docs.it4i/software/debuggers/allinea-ddt.md
index 5c837b23d27a615cb40491c4ea81ba670e670927..ae984fbe1d8398e47e62ba437929eaba85fa69bc 100644
--- a/docs.it4i/software/debuggers/allinea-ddt.md
+++ b/docs.it4i/software/debuggers/allinea-ddt.md
@@ -47,13 +47,13 @@ $ mpif90 -g -O0 -o test_debug test.f
 Before debugging, you need to compile your code with these flags:
 
 !!! note
-    \- **g**: Generates extra debugging information usable by GDB. -**g3** includes even more debugging information. This option is available for GNU and Intel C/C++ and Fortran compilers.
+    `-g`: Generates extra debugging information usable by GDB. `-g3` includes even more debugging information. This option is available for GNU and Intel C/C++ and Fortran compilers.
 
-    \- **O0**: Suppresses all optimizations.
+    `-O0`: Suppresses all optimizations.
 
 ## Starting a Job With DDT
 
-Be sure to log in with an X window forwarding enabled. This could mean using the -X in the ssh:
+Be sure to log in with an X window forwarding enabled. This could mean using the `-X` in the `ssh`:
 
 ```console
 $ ssh -X username@anselm.it4i.cz
@@ -61,23 +61,23 @@ $ ssh -X username@anselm.it4i.cz
 
 Another options is to access the login node using VNC. See the detailed information on how to [use graphic user interface on Anselm][1].
 
-From the login node, an interactive session **with X windows forwarding** (-X option) can be started by the following command:
+From the login node, an interactive session **with X windows forwarding** (the `-X` option) can be started by the following command:
 
 ```console
 $ qsub -I -X -A NONE-0-0 -q qexp -lselect=1:ncpus=16:mpiprocs=16,walltime=01:00:00
 ```
 
-Then launch the debugger with the ddt command followed by the name of the executable to debug:
+Then launch the debugger with the `ddt` command followed by the name of the executable to debug:
 
 ```console
 $ ddt test_debug
 ```
 
-A submission window appears with a prefilled path to the executable to debug. Select the number of MPI processors and/or OpenMP threads on which to run, then press run. Command line arguments to a program can be entered to the "Arguments " box.
+A submission window appears with a prefilled path to the executable to debug. Select the number of MPI processors and/or OpenMP threads on which to run, then press run. Command line arguments to a program can be entered to the Arguments field.
 
 ![](../../img/ddt1.png)
 
-To start the debugging directly without the submission window, the user can specify the debugging and execution parameters from the command line. For example, the number of MPI processes is set by the "-np 4" option. Skipping the dialog is done by the "-start" option. To see the list of the "ddt" command line parameters, run "ddt --help".
+To start the debugging directly without the submission window, the user can specify the debugging and execution parameters from the command line. For example, the number of MPI processes is set by the `-np 4` option. Skipping the dialog is done by the `-start` option. To see the list of the `ddt` command line parameters, run `ddt --help`.
 
 ```console
 ddt -start -np 4 ./hello_debug_impi