From ba242344f2731dfb197683a03cbb2f3475369cb5 Mon Sep 17 00:00:00 2001
From: Jan Siwiec <jan.siwiec@vsb.cz>
Date: Wed, 15 Apr 2020 11:46:00 +0200
Subject: [PATCH] Update allinea-performance-reports.md

---
 .../software/debuggers/allinea-performance-reports.md     | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/docs.it4i/software/debuggers/allinea-performance-reports.md b/docs.it4i/software/debuggers/allinea-performance-reports.md
index 40ec88417..892ddd9e3 100644
--- a/docs.it4i/software/debuggers/allinea-performance-reports.md
+++ b/docs.it4i/software/debuggers/allinea-performance-reports.md
@@ -20,21 +20,19 @@ The module sets up environment variables, required for using the Allinea Perform
 
 ## Usage
 
-Use the perf-report wrapper on your (MPI) program.
-
-Instead of [running your MPI program the usual way][1], use the perf report wrapper:
+Instead of [running your MPI program the usual way][1], use the `perf-report` wrapper:
 
 ```console
 $ perf-report mpirun ./mympiprog.x
 ```
 
-The MPI program will run as usual. The perf-report creates two additional files, in \*.txt and \*.html format, containing the performance report. Note that demanding MPI codes should be run within [the queue system][2].
+The MPI program will run as usual. `perf-report` creates two additional files, in \*.txt and \*.html format, containing the performance report. Note that demanding MPI code should be run within [the queue system][2].
 
 ## Example
 
 In this example, we will be profiling the mympiprog.x MPI program, using Allinea performance reports. Assume that the code is compiled with Intel compilers and linked against Intel MPI library:
 
-First, we allocate some nodes via the express queue:
+First, we allocate nodes via the express queue:
 
 ```console
 $ qsub -q qexp -l select=2:ppn=24:mpiprocs=24:ompthreads=1 -I
-- 
GitLab