2-Slurm/2.1-Batch-job-submission.md

@@ -89,7 +89,7 @@ The title of the last column displayed by `squeue` is "NODELIST(REASON)":
    *  **QOSMaxCpuPerUserLimit**: the maximal number of authorized allocated cores has been reached by *username* ; the job is waiting for some running jobs of *username* to end.
    *  **BeginTime**: the job earliest start time has not been reached yet. Can happen when the job is requeued by Slurm to fix an issue: in this case, Slurm sets a delayed start time for the job.
    *  **Held state**: the job *job_id* is hold by Slurm. To unlock it, do `scontrol release job_id`.
-   *  **QOSMaxCpuPerJobLimit**: if a job specifies a memory per CPU limit that exceeds the partition limit, that job's count of CPUs per task will automatically be increased. This may result in the job failing due to CPU count limits. ***IN THIS CASE, CANCEL YOUR JOB AND RESUBMIT IT WITH THE CORRECT PARAMETERS, OTHERWISE IT JOB WILL PEND FOREVER***.
+   *  **QOSMaxCpuPerJobLimit**: if a job specifies a memory per CPU limit that exceeds the partition limit, that job's count of CPUs per task will automatically be increased. This may result in the job failing due to CPU count limits. ***In this case, cancel your job and resubmit it with the correct parameters, otherwise it will pend forever***.
 
 The following command provides detailed information on a running or recently completed job:
 ```