diff --git a/docs.it4i/general/slurm-job-submission-and-execution.md b/docs.it4i/general/slurm-job-submission-and-execution.md
index fb2402e4ca3ce1fc18a710c80115a4dcd342ac97..e166d60150132a7bbc445c54f74ef69865b09c78 100644
--- a/docs.it4i/general/slurm-job-submission-and-execution.md
+++ b/docs.it4i/general/slurm-job-submission-and-execution.md
@@ -1,7 +1,7 @@
 # Job Submission and Execution
 
 !!! warning
-    Don't use the `#SBATCH -- exclusive` parameter as it is already included in the SLURM configuration.<br><br>
+    Don't use the `#SBATCH --exclusive` parameter as it is already included in the SLURM configuration.<br><br>
     Use the `#SBATCH --mem=` parameter **on `qfat` only**. On `cpu_` queues, whole nodes are allocated.
     Accelerated nodes (`gpu_` queues) are divided each into eight parts with corresponding memory.
 
@@ -81,7 +81,7 @@ Run interactive job, with X11 forwarding:
 $ salloc -A PROJECT-ID -p qcpu_exp --x11
 ```
 
-To finish the interactive job, you can either use the `exit` keyword, or Ctrl+D (`^D`) control sequence.
+To finish the interactive job, use the Ctrl+D (`^D`) control sequence.
 
 !!! warning
     Do not use `srun` for initiating interactive jobs, subsequent `srun`, `mpirun` invocations would block forever.
@@ -153,7 +153,7 @@ Example output of the job:
 ### Job Environment Variables
 
 Slurm provides useful information to the job via environment variables.
-Environment variables are available on all nodes allocated to job when accessed via Slurm supported means (srun, compatible mpirun).
+Environment variables are available on all nodes allocated to job when accessed via Slurm supported means (`srun`, compatible `mpirun`).
 
 See all Slurm variables
 
@@ -321,7 +321,7 @@ Delete all my pending jobs for a project PROJECT-ID:
 $ scancel --me -t pending -A PROJECT-ID
 ```
 
-## Faq
+## Troubleshooting
 
 ### Invalid Account