diff --git a/docs.it4i/software/debuggers/scalasca.md b/docs.it4i/software/debuggers/scalasca.md
index d31627e3f6df1ea592aa620ed9366b0472d37fc9..cbf22e09aed89b495f6641ea205645ce2ef76e21 100644
--- a/docs.it4i/software/debuggers/scalasca.md
+++ b/docs.it4i/software/debuggers/scalasca.md
@@ -39,8 +39,8 @@ An example:
 
 Some notable Scalasca options are:
 
-* **-t Enable trace data collection. By default, only summary data are collected.**
-* **-e <directory> Specify a directory to which the collected data is saved. By default, Scalasca saves the data to a directory with the scorep\_ prefix, followed by the name of the executable and the launch configuration.**
+* `-t` enables trace data collection. By default, only summary data are collected.
+* `-e <directory>` specifies a directory to which the collected data is saved. By default, Scalasca saves the data to a directory with the scorep\_ prefix, followed by the name of the executable and the launch configuration.
 
 !!! note
     Scalasca can generate a huge amount of data, especially if tracing is enabled. Consider saving the data to a [scratch directory][6].
@@ -55,7 +55,7 @@ To launch the analysis, run:
 scalasca -examine [options] <experiment_directory>
 ```
 
-If you do not wish to launch the GUI tool, use the "-s" option:
+If you do not wish to launch the GUI tool, use the `-s` option:
 
 ```console
 scalasca -examine -s <experiment_directory>