From a4291446e0edf74a577ab0ee2ee5499856bdac19 Mon Sep 17 00:00:00 2001
From: Jan Siwiec <jan.siwiec@vsb.cz>
Date: Wed, 15 Apr 2020 14:07:48 +0200
Subject: [PATCH] Update scalasca.md
---
docs.it4i/software/debuggers/scalasca.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs.it4i/software/debuggers/scalasca.md b/docs.it4i/software/debuggers/scalasca.md
index d31627e3f..cbf22e09a 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>
--
GitLab