fix some typos

doc.zih.tu-dresden.de/docs/jobs_and_resources/partitions_and_limits.md

@@ -74,8 +74,8 @@ The available compute nodes are grouped into logical (possibly overlapping) sets
 
 Some partitions/nodes have Simultaneous Multithreading (SMT) enabled. You request for this
 additional threads using the Slurm option `--hint=multithread` or by setting the environment
-varibale `SLURM_HINT=multithread`. Besides the usage of the threads to speed up the computations,
-the memory of the other threads is allocated implicitly, too, and you will allways get
+variable `SLURM_HINT=multithread`. Besides the usage of the threads to speed up the computations,
+the memory of the other threads is allocated implicitly, too, and you will always get
 `Memory per Core`*`number of threads` as memory pledge.
 
 Some partitions have a *interactive* counterpart for interactive jobs. The corresponding partitions

doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md

@@ -341,7 +341,7 @@ Please read the Slurm documentation at https://slurm.schedmd.com/sbatch.html for
 
 You can use chain jobs to **create dependencies between jobs**. This is often useful if a job
 relies on the result of one or more preceding jobs. Chain jobs can also be used to split a long
-runnning job exceeding the batch queues limits into parts and chain these parts. Slurm has an option
+running job exceeding the batch queues limits into parts and chain these parts. Slurm has an option
 `-d, --dependency=<dependency_list>` that allows to specify that a job is only allowed to start if
 another job finished.