Fix for review

Author: jgphpc

docs/images/devtools/vihps/logo_scalasca.png

@@ -5,32 +5,32 @@ The [VI-HPS](https://www.vi-hps.org/tools) Institute (Virtual Institute for High
 
 ## [Score-P](https://www.vi-hps.org/projects/score-p/overview/overview.html)
 
-![logo_scorep](../../images/devtools/vihps/logo_scorep.png){ width="5%"}
+[Score-P](https://www.vi-hps.org/projects/score-p/overview/overview.html)
 is a highly scalable instrumentation and measurement infrastructure for profiling, event tracing, and online analysis. It supports a wide range of HPC platforms and programming models. Score-P provides core measurement services for a range of specialized analysis tools, such as Vampir, Scalasca and others.
 
 ## [Vampir](https://www.vi-hps.org/tools/vampir.html) 
 
-![logo_vampir](../../images/devtools/vihps/logo_vampir.png){ width="5%"}
+[Vampir](https://www.vi-hps.org/tools/vampir.html) 
 is a performance visualizer that allows to quickly study the program runtime behavior at a fine level of details. This includes the display of detailed performance event recordings over time in timelines and aggregated profiles. Interactive navigation and zooming are the key features of the tool, which help to quickly identify inefficient or faulty parts of a program.
 
 !!! info
     While Score-P does not require a license, [Vampir](https://vampir.eu/licensing) does. CSCS standard license allows to read trace files with up to 256 concurrent threads of execution.
 
     The Vampir GUI is currently available only on `x86-64` CPU based systems and is not provided via a uenv (more details in the Quickstart guide below).
-    You can use Score-P to generate OTF2 traces files on Alps compute nodes and then visualize the results with Vampir on a x86-64 CPU based system (for instance Eiger, LUMI or your own license). 
+    You can use Score-P to generate OTF2 traces files on Alps compute nodes and then visualize the results with Vampir on a x86-64 CPU based system (for instance Eiger, LUMI or using your own license). 
 
 ## [Cube and Scalasca](http://www.vi-hps.org/tools/scalasca.html)
 
-![logo_scalasca](../../images/devtools/vihps/logo_scalasca.png){ width="5%"}
- support the performance optimization of parallel programs with a collection of scalable trace-based tools for in-depth analyses of concurrent behavior. The analysis identifies potential performance bottlenecks - in particular those concerning communication and synchronization - and offers guidance in exploring their causes.
+[Cube and Scalasca](http://www.vi-hps.org/tools/scalasca.html)
+support the performance optimization of parallel programs with a collection of scalable trace-based tools for in-depth analyses of concurrent behavior. The analysis identifies potential performance bottlenecks - in particular those concerning communication and synchronization - and offers guidance in exploring their causes.
 
 ## Quickstart guide
 
 The VI-HPS uenv is named `scorep` and it can be loaded into your environment as explained here and in the [uenv documentation][ref-uenv].
 
-??? example "Finding and pulling available `scorep` versions"
+!!! example "Finding and pulling available `scorep` versions"
 
-    ```bash
+    ```console
     uenv image find scorep
     # uenv                 arch   system  id                 size(MB) date
     # scorep/9.2-gcc12:v1  gh200  daint   bfd3b46d30404f2c   7,602    2025-07-14
@@ -42,7 +42,7 @@ The VI-HPS uenv is named `scorep` and it can be loaded into your environment as
 
     This uenv is configured to be mounted in the `/user-environment` path.
 
-??? example "Start the `scorep` uenv"
+!!! example "Start the `scorep` uenv"
 
     ```bash
     uenv start scorep/9.2-gcc13:v1 -v default
@@ -59,7 +59,7 @@ The VI-HPS uenv is named `scorep` and it can be loaded into your environment as
     1. Test that everything has been mounted correctly and that the tools are in the PATH
     2. A PDF version of the user guide is available in the uenv.
 
-??? example "Recompile your code with `scorep` on Alps"
+!!! example "Recompile your code with `scorep` on Alps"
 
     ```bash
     # Building with CMake requires the following steps
@@ -76,7 +76,7 @@ The VI-HPS uenv is named `scorep` and it can be loaded into your environment as
         cmake --build build
     ```
 
-??? example "Run your application with `scorep` on Alps"
+!!! example "Run your application with `scorep` on Alps"
 
     Pick one of the report type in your jobscript before running the executable compiled with `scorep`:
 
@@ -123,16 +123,14 @@ The VI-HPS uenv is named `scorep` and it can be loaded into your environment as
         ```
 
         !!! info
-        - Tracing allows more detailed analysis but will also make your simulation run longer than with profiling,
-        - `scorep-score` allows to estimate the size of an OTF2 tracefile from a CUBE profile,
-          it can also help to reduce the overhead of tracing via filtering:
-
-        ```bash
-        scorep-score -g profile.cubex # generate filter file
-        scorep-score -f initial_scorep.filter profile.cubex
-        export SCOREP_FILTERING_FILE='initial_scorep.filter'
-        ```
-
-        The [user guide](https://perftools.pages.jsc.fz-juelich.de/cicd/scorep/tags/scorep-9.2/html/group__SCOREP__User.html#gaab4b3ccc2b169320c1d3bf7fe19165f9) provides more details about how to reduce overhead.
+            - Tracing allows more detailed analysis but will also make your simulation run longer than with profiling,
+            - `scorep-score` allows to estimate the size of an OTF2 tracefile from a CUBE profile,
+              it can also help to reduce the overhead of tracing via filtering:
+            ```bash
+            scorep-score -g profile.cubex # generate filter file
+            scorep-score -f initial_scorep.filter profile.cubex
+            export SCOREP_FILTERING_FILE='initial_scorep.filter'
+            ```
+            - The [user guide](https://perftools.pages.jsc.fz-juelich.de/cicd/scorep/tags/scorep-9.2/html/group__SCOREP__User.html#gaab4b3ccc2b169320c1d3bf7fe19165f9) provides more details about how to reduce overhead.
 
         ![sphexa_vampir](../../images/devtools/vihps/sphexa_vampir.png){ width="90%"}