From 37e44367198bec388cfb5106a68eead467f32104 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Roman=20Sl=C3=ADva?= <roman.sliva@vsb.cz>
Date: Sat, 22 Jul 2023 09:04:56 +0200
Subject: [PATCH] Update slurm-job-submission-and-execution.md

---
 docs.it4i/general/slurm-job-submission-and-execution.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs.it4i/general/slurm-job-submission-and-execution.md b/docs.it4i/general/slurm-job-submission-and-execution.md
index e5a31a6c9..71db2ce46 100644
--- a/docs.it4i/general/slurm-job-submission-and-execution.md
+++ b/docs.it4i/general/slurm-job-submission-and-execution.md
@@ -38,6 +38,8 @@ On Complementary systems only some queues/partitions provide full node allocatio
 
 ## Running Interactive Jobs
 
+Sometimes you may want to run your job interactively, for example for debugging, running your commands one by one from the command line.
+
 Run interactive job - queue qcpu_exp, one node by default, one task by default:
 
 ```console
@@ -63,6 +65,8 @@ To finish the interactive job, you can either use the `exit` keyword, or Ctrl+D
 
 ## Running Batch Jobs
 
+Batch jobs is the standard way of running jobs and utilizing HPC clusters.
+
 ### Job Script
 
 Create example batch script called script.sh with the following content:
-- 
GitLab