Merge branch 'time_min_update' into 'main'

added a warning about the time-min flag in the submitting jobs page

See merge request !87

docs/running_jobs/submit_jobs.md

@@ -122,6 +122,9 @@ sacctmgr show qos  format=name%20s,priority,grpnodes,maxwall,description%40s
 !!! Tip
     It is a good practice to include the wall time in your submission script. It will help spending less time in the queue. The default maximum walltime is 1 day. Use the ```#SBATCH -- time=DD-HH:MM:SS``` flag to specify the appropriate time. 
 
+!!! Warning
+    Setting `--time-min` may get the job to begin execution earlier than otherwise possible by backfill scheduling . If specified, the job may have its `--time` limit lowered to a value no lower than `--time-min` if doing so permits the job to begin execution earlier. **The job's time limit will not be changed after the job is allocated resources**. Meaning your job must finish before the time set in `--time-min`. The difference between `--time` and `--time-min` can be thought as a safety margin.
+
 If your job ends before the time limit is up, your project will only be charged for the actual time used. It is important to note that short jobs can start faster due to backfill and jobs that require more resources might take longer to start.
 
 Please keep in mind that it is wise to add a margin to the wall time setting to prevent jobs from failing if they run slightly slower than expected for some unforeseen reason.