From dc412f36aa61b5575b724eaf9fd423328e793df7 Mon Sep 17 00:00:00 2001
From: Michael Knobloch <m.knobloch@fz-juelich.de>
Date: Mon, 6 Mar 2017 10:15:43 +0100
Subject: [PATCH] Fixed wording

---
 Profiling-scorep-Vampir.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Profiling-scorep-Vampir.md b/Profiling-scorep-Vampir.md
index 35e7ddd..bd31615 100644
--- a/Profiling-scorep-Vampir.md
+++ b/Profiling-scorep-Vampir.md
@@ -1,8 +1,8 @@
 # Profiling with Score-P and Friends
 
-Score-P allows for detailed instrumentation of an application using CPU and/or GPU. The generated scoring can be analyzed with CUBE, Scalasca, or Vampir.
+Score-P allows for detailed instrumentation of an application using CPU and/or GPU. The generated profiles can be analyzed with CUBE.  If OTF2 traces were created, those can be analyzed automatically with Scalasca or manually with Vampir.
 
-## Generating Scores
+## Generating Performance Reports
 
 ### Modules
 
@@ -58,7 +58,7 @@ Score-P reports and traces are the basis for analyses with Cube, Scalasca, or Va
 
 ### Lightweight and Superficial: `scorep-score`
 
-For a *quick and dirty* look at the score, e.g. for validating that something happened at all, `scorep-score` can be used.
+For a *quick and dirty* look at the performance data, e.g. for validating that something happened at all, `scorep-score` can be used.
 
 ```
 scorep-score scorep-20170302_0919_1488442762831800//profile.cubex
-- 
GitLab