diff --git a/docs.it4i/software/debuggers/cube.md b/docs.it4i/software/debuggers/cube.md
index e42a55fc4e7cbd416405d78c9bf2625807919552..f6a4ddb06f01beef8fc9b6632fb6f4ec1eb3b593 100644
--- a/docs.it4i/software/debuggers/cube.md
+++ b/docs.it4i/software/debuggers/cube.md
@@ -14,7 +14,7 @@ Each dimension is organized in a tree, for example the time performance metric i
 
 \*Figure 1. Screenshot of CUBE displaying data from Scalasca.\*
 
-Each node in the tree is colored by severity (the color scheme is displayed at the bottom of the window, ranging from the least severe blue to the most severe being red). For example in Figure 1, we can see that most of the point-to-point MPI communication happens in routine exch_qbc, colored red.
+Each node in the tree is colored by severity (the color scheme is displayed at the bottom of the window, ranging from the least severe blue to the most severe being red). For example in Figure 1, we can see that most of the point-to-point MPI communication happens in the `exch_qbc` routine, colored red.
 
 ## Installed Versions
 
@@ -30,7 +30,7 @@ CUBE is a graphical application. Refer to the Graphical User Interface documenta
 !!! note
     Analyzing large data sets can consume large amount of CPU and RAM. Do not perform large analysis on login nodes.
 
-After loading the appropriate module, simply launch the cube command, or alternatively you can use Scalasca -examine command to launch the GUI. Note that for Scalasca data sets, if you do not analyze the data with `scalasca -examine` before opening them with CUBE, not all performance data will be available.
+After loading the appropriate module, simply launch the cube command, or alternatively you can use the `scalasca -examine` command to launch the GUI. Note that for Scalasca data sets, if you do not analyze the data with `scalasca -examine` before opening them with CUBE, not all performance data will be available.
 
 References
 1\.  [Download link][a]