From 661732c80a23a989aec40d8e34f7ce08a5b4c402 Mon Sep 17 00:00:00 2001
From: Jan Siwiec <jan.siwiec@vsb.cz>
Date: Fri, 30 Aug 2024 09:41:53 +0200
Subject: [PATCH] Update vnc.md

---
 .../accessing-the-clusters/graphical-user-interface/vnc.md  | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md b/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md
index 3028f2ae6..f6a9651f6 100644
--- a/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md
+++ b/docs.it4i/general/accessing-the-clusters/graphical-user-interface/vnc.md
@@ -230,7 +230,7 @@ Allow incoming X11 graphics from the compute nodes at the login node:
 Get an interactive session on a compute node (for more detailed info [look here][4]). Forward X11 system using `--x11` option:
 
 ```console
-$ salloc -A PROJECT_ID -q qcpu --x11
+$ salloc -A PROJECT_ID -p qcpu --x11
 ```
 
 Test that the DISPLAY redirection into your VNC session works, by running an X11 application (e.g. XTerm, Intel Advisor, etc.) on the assigned compute node:
@@ -247,12 +247,12 @@ The example described above:
 
 For a [better performance][1] an SSH connection can be used.
 
-Open two Terminals  (_Applications -> System Tools -> Terminal_) as described before.
+Open two Terminals (_Applications -> System Tools -> Terminal_) as described before.
 
 Get an interactive session on a compute node (for more detailed info [look here][4]). Forward X11 system using `--x11` option:
 
 ```console
-$ salloc -A PROJECT_ID -q qcpu --x11
+$ salloc -A PROJECT_ID -p qcpu --x11
 ```
 
 In the second terminal connect to the assigned node and run the X11 application
-- 
GitLab