Further improvements to batch-task-complete-event.md

Author: xinlaoda

articles/batch/batch-task-complete-event.md

@@ -51,7 +51,7 @@ ms.date: 01/29/2026
 |------------------|----------|-----------|
 |`jobId`|String|The ID of the job containing the task.|
 |`id`|String|The ID of the task.|
-|`taskType`|String|The type of the task. This can either be 'JobManager' indicating it's a job manager task or 'User' indicating it isn't a job manager task. Note that this event isn't emitted for job preparation tasks, job release tasks, or start tasks.|
+|`taskType`|String|The type of the task. The task type can either be 'JobManager' indicating it's a job manager task or 'User' indicating it isn't a job manager task. This event isn't emitted for job preparation tasks, job release tasks, or start tasks.|
 |`systemTaskVersion`|Int32|The internal retry counter on a task. Internally the Batch service can retry a task to account for transient issues. These issues can include internal scheduling errors or attempts to recover from compute nodes in a bad state.|
 |`requiredSlots`|Int32|The required slots to run the task.|
 |[`nodeInfo`](#nodeInfo)|Complex Type|Contains information about the compute node on which the task ran.|
@@ -76,25 +76,25 @@ ms.date: 01/29/2026
 
 |Element name|Type|Notes|
 |------------------|----------|-----------|
-|`maxTaskRetryCount`|Int32|The maximum number of times the task may be retried. The Batch service retries a task if its exit code is nonzero.<br /><br /> This value specifically controls the number of retries. The Batch service tries the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a task up to 4 times (one initial try and 3 retries).<br /><br /> If the maximum retry count is 0, the Batch service doesn't retry tasks.<br /><br /> If the maximum retry count is -1, the Batch service retries tasks without limit.<br /><br /> The default value is 0 (no retries).|
+|`maxTaskRetryCount`|Int32|The maximum number of times the task might be retried. The Batch service retries a task if its exit code is nonzero.<br /><br /> This value specifically controls the number of retries. The Batch service tries the task once, and might then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a task up to four times (one initial try and three retries).<br /><br /> If the maximum retry count is 0, the Batch service doesn't retry tasks.<br /><br /> If the maximum retry count is -1, the Batch service retries tasks without limit.<br /><br /> The default value is 0 (no retries).|
 
 ###  <a name="executionInfo"></a> executionInfo
 
 |Element name|Type|Notes|
 |------------------|----------|-----------|
-|`startTime`|DateTime|The time when the task started running. 'Running' corresponds to the **running** state, so if the task specifies resource files or application packages, then the start time reflects the time when the task started downloading or deploying these. If the task restarted or retried, this is the most recent time at which the task started running.|
+|`startTime`|DateTime|The time when the task started running. 'Running' corresponds to the **running** state, so if the task specifies resource files or application packages, then the start time reflects the time when the task started downloading or deploying these resource files or application packages. If the task restarted or retried, this is the most recent time at which the task started running.|
 |`endTime`|DateTime|The time when the task completed.|
-|`exitCode`|Int32|The exit code of the task.  If the task failed before it started running, then exitCode is null.|
-|`retryCount`|Int32|The number of times the task is retried by the Batch service. The task is retried if it exits with a nonzero exit code, up to the specified MaxTaskRetryCount.|
-|`requeueCount`|Int32|The number of times the task is requeued by the Batch service as the result of a user request.<br /><br /> When you remove nodes from a pool (by resizing or shrinking it) or disable a job, you can choose to requeue the running tasks on those nodes for execution. This count tracks how many times the task requeued for these reasons.|
-|`result`|String|The task result string, it could be "Success" or "Failure".|
+|`exitCode`|Int32|The exit code of the task. If the task failed before it started running, then exitCode is null.|
+|`retryCount`|Int32|The number of times the Batch service retired the task. The task is retried if it exits with a nonzero exit code, up to the specified MaxTaskRetryCount.|
+|`requeueCount`|Int32|The number of times the Batch service requeued the task as the result of a user request.<br /><br /> When you remove nodes from a pool (by resizing or shrinking it) or disable a job, you can choose to requeue the running tasks on those nodes for execution. It count tracks how many times the task requeued.|
+|`result`|String|The task result string, it could be "Success" or "Failure"|
 |[`schedulingError`](#schedulingError)|Complex Type|Contain detailed information about error.|
 
 ###  <a name="schedulingError"></a> schedulingError
 
 |Element name|Type|Notes|
 |------------------|----------|-----------|
-|`category`|String|The error category, e.g. "UserError".|
-|`code`|String|The error code, e.g. "FailureExitCode".|
+|`category`|String|The error category, for example "UserError".|
+|`code`|String|The error code, for example "FailureExitCode".|
 |`message`|String|The error message.|
 |`details`|Array|The error details.|