diff --git a/docs.it4i/software/intel/intel-suite/intel-integrated-performance-primitives.md b/docs.it4i/software/intel/intel-suite/intel-integrated-performance-primitives.md
index 7a622ab6b95799b3e42de48026064e7ca0488d12..dc5e831aee90ad1c67734e1e906661afb793c2d9 100644
--- a/docs.it4i/software/intel/intel-suite/intel-integrated-performance-primitives.md
+++ b/docs.it4i/software/intel/intel-suite/intel-integrated-performance-primitives.md
@@ -2,7 +2,7 @@
 
 ## Intel Integrated Performance Primitives
 
-Intel Integrated Performance Primitives version 9.0.1 compiled for AVX2 vector instructions is available via the ipp  module. IPP is a very rich library of highly optimized algorithmic building blocks for media and data applications. This includes signal, image, and frame processing algorithms, such as FFT, FIR, Convolution, Optical Flow, Hough transform, Sum, MinMax, as well as cryptographic functions, linear algebra functions, and many more.
+Intel Integrated Performance Primitives version 9.0.1 compiled for AVX2 vector instructions is available via the `ipp`  module. IPP is a very rich library of highly optimized algorithmic building blocks for media and data applications. This includes signal, image, and frame processing algorithms, such as FFT, FIR, Convolution, Optical Flow, Hough transform, Sum, MinMax, as well as cryptographic functions, linear algebra functions, and many more.
 
 Check out IPP before implementing own math functions for data processing, as it is likely already there.
 
@@ -55,7 +55,7 @@ int main(int argc, char* argv[])
 }
 ```
 
-Compile the example above, using any compiler and the ipp module:
+Compile the example above, using any compiler and the `ipp` module:
 
 ```console
 $ ml intel
@@ -63,7 +63,7 @@ $ ml ipp
 $ icc testipp.c -o testipp.x -lippi -lipps -lippcore
 ```
 
-You will need the ipp module loaded to run the IPP-enabled executable. This may be avoided, by compiling library search paths into the executable:
+You will need the `ipp` module loaded to run an IPP-enabled executable. This may be avoided, by compiling library search paths into the executable:
 
 ```console
 $ ml intel