dump tutorial slides, format later

Author: s-sajid-ali

docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md

@@ -20,15 +20,13 @@ Do not specify partitions manually, except for preemption which is described lat
 Jobs with low GPU utilization will be automatically canceled. The exact threshold is TBD, but enforcement will be very aggressive.
 :::
 
+## Preemptible jobs on Torch
+On Torch, users may run "preemptible" jobs on stakeholder resources that their group does not own. This allows the stakeholder resources to be utilized by non-stakeholders which may otherwise be idle. To make the best use of these resources, you are encouraged to adopt checkpoint/restart to allow for resumption of the workload in subsequent jobs.
 
 :::info Preemption Policy
 Jobs become eligible for preemption after 1 hour of runtime. Jobs will not be canceled within the first hour.
 :::
 
-## Preemptible jobs on Torch
-On Torch, users may run "preemptible" jobs on stakeholder resources that their group does not own. This allows the stakeholder resources to be utilized by non-stakeholders which may otherwise be idle. To make the best use of these resources, you are encouraged to adopt checkpoint/restart to allow for resumption of the workload in subsequent jobs.
-
-
 The preemption order is:
 -   Stakeholder jobs have highest priority, can preempt GPU jobs from public users or other stakeholders
 -   GPU jobs can preempt CPU-only jobs running on GPU nodes