Typo

docs.it4i/anselm-cluster-documentation/software/debuggers/scalasca.md

@@ -27,9 +27,9 @@ Instrumentation via " scalasca -instrument" is discouraged. Use [Score-P instrum
 
 ### Runtime measurement
 
-After the application is instrumented, runtime measurement can be performed with the " scalasca -analyze" command. The syntax is:
+After the application is instrumented, runtime measurement can be performed with the `scalasca -analyze` command. The syntax is:
 
-scalasca -analyze [scalasca options][launcher] [launcher options][program] [program options]
+`scalasca -analyze [scalasca options][launcher] [launcher options][program] [program options]`
 
 An example :
 
@@ -39,10 +39,10 @@ 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 save the collected data to. By default, Scalasca saves the data to a directory with prefix scorep\_, followed by name of the executable and launch configuration.**
+-   **-t Enable trace data collection. By default, only summary data are collected.**
+-   **-e <directory> Specify a directory to save the collected data to. By default, Scalasca saves the data to a directory with prefix scorep\_, followed by name of the executable and launch configuration.**
 
-!!! Note "Note"
+!!! Note
 	Scalasca can generate a huge amount of data, especially if tracing is enabled. Please consider saving the data to a [scratch directory](../../storage/storage/).
 
 ### Analysis of reports