diff --git a/docs.it4i/general/slurm-job-submission-and-execution.md b/docs.it4i/general/slurm-job-submission-and-execution.md
index ac122ba26cb050124575c594cf215111bcf31cdf..0db4ec9c245152f3e1d457358a3d494f03665c37 100644
--- a/docs.it4i/general/slurm-job-submission-and-execution.md
+++ b/docs.it4i/general/slurm-job-submission-and-execution.md
@@ -29,7 +29,7 @@ A `man` page exists for all Slurm commands, as well as `--help` command option,
 Slurm provides three different commands for job submission: `salloc`, `sbatch`, and `srun`. Each of those serves a slightly different purpose;
 `salloc` is used to run interactive job - behaviour of this command at IT4Innovation's clusters might differ from behaviour at other clusters, it is alternative to PBS qsub -I command.
 `sbatch` is used to submit a batch script to Slurm, it is alternative to PBS qsub command used without -I option.
-`srun` behaviour of the command depends on whether it was run from inside the job or from outside, from inside of the job command serves as Slurm's native way of executing MPI-enabled applications, from outside of the job command obtains appropriate allocation first and then run a specified command in parallel.
+`srun` behaviour of the command depends on whether it was run from inside of the job or from outside, from inside of the job command serves as Slurm's native way of executing MPI-enabled applications, from outside of the job command obtains appropriate allocation first and then run a specified command in parallel.
 
 ## Batch Mode
 
@@ -50,17 +50,18 @@ To define Slurm job options within the batch script, use `SBATCH` keyword follow
 ```shell
 #SBATCH -A OPEN-00-00
 #SBATCH -p qcpu
-#SBATCH -n 4
+#SBATCH -N 4
+#SBATCH --ntasks-per-node 36
 ```
 
-Here we asked for 4 tasks in total to be executed on partition qcpu using OPEN-00-00's project resources.
+Here we asked for four nodes and for 36 tasks to be executed per node on partition qcpu using OPEN-00-00's project resources.
 
 Job instructions should contain everything you'd like your job to do; that is, every single command the job is supposed to execute:
 
 ```shell
 ml OpenMPI/4.1.4-GCC-11.3.0
 
-srun hostname
+srun hostname | uniq -c
 ```
 
 Combined together, the previous examples make up a following script:
@@ -68,18 +69,18 @@ Combined together, the previous examples make up a following script:
 ```shell
 #!/usr/bin/bash
 #SBATCH -A OPEN-00-00
-#SBATCH -p qcpu
-#SBATCH -n 4
+#SBATCH -N 4
+#SBATCH --ntasks-per-node 36
 
 ml OpenMPI/4.1.4-GCC-11.3.0
 
-srun hostname
+srun hostname | uniq -c
 ```
 
-And by submitting it from the login node of Complementary System
+And by submitting it from the login node of Barbora cluster
 
 ```console
-$ sbatch ./batchscript.sh
+$ sbatch ./script.sh
 Submitted batch job 1511
 ```
 
@@ -87,12 +88,12 @@ we get an output file with the following contents:
 
 ```console
 $ cat slurm-1511.out
-      1 cn1.barbora.it4i.cz
-      3 cn2.barbora.it4i.cz
+      36 cn1.barbora.it4i.cz
+      36 cn2.barbora.it4i.cz
+      36 cn3.barbora.it4i.cz
+      36 cn4.barbora.it4i.cz
 ```
 
-Notice that Slurm spread our job across 2 different nodes; by default, Slurm selects the number of nodes to minimize wait time before job execution. However, sometimes you may want to restrict your job to only a certain minimum or maximum number of nodes (or both). You may also require more time for your calculation to finish than the default allocated time. For an overview of such job options, see table below.
-
 ### Quick Overview of Common Batch Job Options
 
 | Job Option        | Specification                                       |
@@ -181,7 +182,7 @@ srun hostname | sort | uniq -c
 exit
 ```
 
-The `-N`, or `--nodes` option takes two arguments: `minnodes`, minimum number of nodes to allocate, and `maxnodes`, maximum number of nodes to allocate. When only one number is specified, it means to allocate exectly the specified number of nodes. Output of the above batchscript may then look something like this:
+The `-N`, or `--nodes` option takes two arguments: `minnodes`, minimum number of nodes to allocate, and `maxnodes`, maximum number of nodes to allocate. When only one number is specified, it means to allocate exectly the specified number of nodes. Output of the above script may then look something like this:
 
 ```console
 $ cat slurm-1642.out
@@ -670,7 +671,7 @@ Job arrays offer a mechanism for submitting and managing collections of similar
 | `SLURM_ARRAY_TASK_MIN`   | Equals to the lowest job array index value.     |
 | `SLURM_ARRAY_TASK_STEP`  | Equals to the step size of task IDs.            |
 
-Consider following batch script, `batchscript.sh`:
+Consider following batch script, `script.sh`:
 
 ```shell
 #!/bin/sh
@@ -686,7 +687,7 @@ exit
 We can use it to submit 3 jobs in an array
 
 ```shell
-sbatch --array=1-3 batchscript.sh
+sbatch --array=1-3 script.sh
 ```
 
 which would result in 3 output files, by default called `slurm-${SLURM_ARRAY_JOB_ID}_${SLURM_ARRAY_TASK_ID}.out`