diff --git a/docs.it4i/general/job-arrays.md b/docs.it4i/general/job-arrays.md
index 5d03ba2e560a3439182529fc5fe16801ae96738c..4031770d3c5ddf6e36b7e93b18304aa9194dd567 100644
--- a/docs.it4i/general/job-arrays.md
+++ b/docs.it4i/general/job-arrays.md
@@ -60,7 +60,7 @@ Be aware, that if the myprog.x **is not multithreaded or multi-process (MPI)**,
 
 ## Submiting Job Array
 
-To submit the job array, use the `sbatch --array` command. The 900 jobs of the [example above][3] may be submitted like this:
+To submit the job array, use the `sbatch --array` command. The 900 jobs of the [example above][2] may be submitted like this:
 
 ```console
 $ sbatch -J JOBNAME --array 1-900 ./jobscript
@@ -75,60 +75,26 @@ Check status of the job array using the `squeue --me` command, alternatively `sq
 ```console
 $  squeue --me --long
              JOBID PARTITION     NAME     USER    STATE       TIME TIME_LIMI  NODES NODELIST(REASON)
-2499924_[5-101]      qcpu  myarray   jansik  PENDING       0:00      1:00      1 (Resources)
+2499924_[1-900]      qcpu  myarray   user  PENDING       0:00      02:00:00      1 (Resources)
 ```
-
-When the status is B, it means that some subjobs are already running.
-Check the status of the first 100 subjobs using the `qstat` command.
+Check the status of the tasks using the `squeue` command.
 
 ```console
-$ qstat -a 12345[1-100].dm2
-
-dm2:
-                                                            Req'd Req'd   Elap
-Job ID          Username Queue    Jobname    SessID NDS TSK Memory Time S Time
---------------- -------- --  |---|---| ------ --- --- ------ ----- - -----
-12345[1].dm2    user2    qprod    xx          13516   1 16    --  00:50 R 00:02
-12345[2].dm2    user2    qprod    xx          13516   1 16    --  00:50 R 00:02
-12345[3].dm2    user2    qprod    xx          13516   1 16    --  00:50 R 00:01
-12345[4].dm2    user2    qprod    xx          13516   1 16    --  00:50 Q   --
+$ squeue -j 2499924
+             JOBID PARTITION     NAME     USER    STATE       TIME TIME_LIMI  NODES NODELIST(REASON)
+2499924_1      qcpu  myarray   user  PENDING       0:00      02:00:00      1 (Resources)
      .             .        .      .             .    .   .     .    .   .    .
-     ,             .        .      .             .    .   .     .    .   .    .
-12345[100].dm2 user2    qprod    xx          13516   1 16    --  00:50 Q   --
-```
-
-Delete the entire job array. Running subjobs will be killed, queueing subjobs will be deleted.
-
-```console
-$ qdel 12345[].dm2
-```
-
-Deleting large job arrays may take a while.
-Display status information for all user's jobs, job arrays, and subjobs.
-
-```console
-$ qstat -u $USER -t
+     .             .        .      .             .    .   .     .    .   .    .
+2499924_900      qcpu  myarray   user  PENDING       0:00      02:00:00      1 (Resources)
 ```
 
-Display status information for all user's subjobs.
+Delete the entire job array. Running tasks will be killed, queueing tasks will be deleted.
 
 ```console
-$ qstat -u $USER -tJ
+$ scancel 2499924
 ```
 
-For more information on job arrays, see the [PBSPro Users guide][1].
-
-## Examples
-
-Download the examples in [capacity.zip][2], illustrating the above listed ways to run a huge number of jobs. We recommend trying out the examples before using this for running production jobs.
-
-Unzip the archive in an empty directory on cluster and follow the instructions in the README file-
-
-```console
-$ unzip capacity.zip
-$ cat README
-```
+For more information on job arrays, see the [SLURM guide][1].
 
-[1]: ../pbspro.md
-[2]: capacity.zip
-[3]: #shared-jobscript
+[1]: https://slurm.schedmd.com/job_array.html
+[2]: #shared-jobscript