diff --git a/docs.it4i/software/debuggers/intel-vtune-profiler.md b/docs.it4i/software/debuggers/intel-vtune-profiler.md
index 5562557c54ee9d2ecca7d8264c143f5c449ac3d0..6f28f2b1c3ea28dde3a02620be3018632bd4344c 100644
--- a/docs.it4i/software/debuggers/intel-vtune-profiler.md
+++ b/docs.it4i/software/debuggers/intel-vtune-profiler.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 Profiler
 
 ## Introduction
@@ -22,13 +19,13 @@ $ ml av VTune
 
 ## Usage
 
-To profile an application with VTune Profiler, 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, to use VTune/2020_update3:
+To profile an application with VTune Profiler, 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` resource at job submission. The version is the same as for the environment module. For example, to use VTune/2020_update3:
 
 ```console
-$ qsub -q qexp -A OPEN-0-0 -I -l select=1,vtune=2020_update3
+$ salloc -p qcpu_exp -A OPEN-0-0 --nodes=1 --gres=vtune:2020_update3
 ```
 
-For VTune/2022.2.0-intel-2021b use `vtune=2022_2_0` parameter.
+For VTune/2022.2.0-intel-2021b use `vtune:2022_2_0` parameter.
 
 After that, you can verify that the modules `sep*`, `pax`, and `vtsspp` are present in the kernel: