dump tutorial slides, format later

Author: s-sajid-ali

docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md

@@ -1,26 +1,24 @@
 # Submitting Jobs on Torch
 
-:::tip [Beginner tutorial available]
+:::tip Beginner tutorial available
 If you are new to using HPC resources and would like to learn about the principles of using the `SLURM` scheduler for submitting batch jobs, please refer to [this section](../13_tutorial_intro_hpc/04_scheduler_fundamentals.mdx). This section focuses on the specifics of the Torch cluster and assumes familiarity with the tutorial.
 :::
 
 
-:::info
-Instead of running interactive jobs on Login nodes, users can run interactive jobs on the HPC Compute nodes using SLURM's `srun` utility. Running interactive jobs on compute nodes does not impact many users and in addition provides access to resources that are not available on the login nodes, such as interactive access to GPUs, high memory, exclusive access to all the resources of a compute node, etc.
-:::
-
-
 ## Partition Management
 - Partitions control stakeholder resource access.
 - No physical nodes are tied to partitions — instead, equivalent compute resources are allocated via partition QoS.
 - Jobs within the same partition cannot exceed their assigned resources (QOSGrpGRES).
 - User GPU Quotas: Each user has a total GPU quota of 24 GPUs for jobs with wall time < 48 hours (QOSMaxGRESPerUser).
 ## Job Submission
-- Do not specify partitions manually.
 - Only request the compute resources (e.g., GPUs, CPUs, memory).
 - Scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests.
 
-:::warning [Low GPU Utilization Policy]
+:::tip Partitions
+Do not specify partitions manually.
+:::
+
+:::warning Low GPU Utilization Policy
 Jobs with low GPU utilization will be automatically cancelled.
 The exact threshold is TBD, but enforcement will be very aggressive.
 :::