diff --git a/docs.it4i/software/debuggers/intel-vtune-amplifier.md b/docs.it4i/software/debuggers/intel-vtune-amplifier.md
index b5bf1c36caceb83fe5f1f2898d5fdcad312bed9a..70153b5336a2901d75bce09732b20b04df04f2e9 100644
--- a/docs.it4i/software/debuggers/intel-vtune-amplifier.md
+++ b/docs.it4i/software/debuggers/intel-vtune-amplifier.md
@@ -1,6 +1,3 @@
-!!!warning
-    This page has not been updated yet. The page does not reflect the transition from PBS to Slurm.
-
 # Intel VTune Amplifier XE
 
 ## Introduction
@@ -24,7 +21,7 @@ $ ml av VTune
 
 ## Usage
 
-To profile an application with VTune Amplifier, special kernel modules need to be loaded. The modules are not loaded on the login nodes, thus direct profiling on login nodes is not possible. By default, the kernel modules are not loaded on compute nodes either. In order to have the modules loaded, you need to specify the `vtune=version` PBS resource at job submit. The version is the same as for the environment module. For example, for VTune/2016_update1, use:
+To profile an application with VTune Amplifier, special kernel modules need to be loaded. The modules are not loaded on the login nodes, thus direct profiling on login nodes is not possible. By default, the kernel modules are not loaded on compute nodes either. In order to have the modules loaded, you need to specify the `--gres=vtune:` resource at job submit. The version is the same as for the environment module.
 
 ```console
 $ salloc -p qexp -A PROJECT_ID --nodes=1 --gres=vtune:2020_update3