Improve batch-task-fail-event.md documentation consistency

Author: xinlaoda

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

@@ -51,11 +51,11 @@ ms.date: 01/28/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. It's either 'JobManager' indicating it's a job manager task or 'User' indicating it's not a job manager task. It's not emitted for job preparation tasks, job release tasks, or start tasks.|
+|`taskType`|String|The type of the task. It's either 'JobManager' indicating it's a job manager task or 'User' indicating it's not a job manager task. This event isn't emitted for job preparation tasks, job release tasks, or start tasks.|
 |`systemTaskVersion`|Int32|It's 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.|
-|[`multiInstanceSettings`](#multiInstanceSettings)|Complex Type|Specifies that the task is a Multi-Instance Task requiring multiple compute nodes.  See [`multiInstanceSettings`](/rest/api/batchservice/get-information-about-a-task) for details.|
+|[`multiInstanceSettings`](#multiInstanceSettings)|Complex Type|Specifies that the task is a Multi-Instance Task requiring multiple compute nodes. See [`multiInstanceSettings`](/rest/api/batchservice/get-information-about-a-task) for details.|
 |[`constraints`](#constraints)|Complex Type|The execution constraints that apply to this task.|
 |[`executionInfo`](#executionInfo)|Complex Type|Contains information about the execution of the task.|
 
@@ -76,7 +76,7 @@ ms.date: 01/28/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
@@ -86,16 +86,16 @@ ms.date: 01/28/2026
 |`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 at which the task started downloading or deploying them. If the task is restarted or retried, it's 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 a result of user request.<br /><br /> When users remove nodes from a pool (by resizing or shrinking it) or disable a job, they can choose to requeue the running tasks on those nodes for execution. This count tracks how many times the task is requeued for these reasons.|
+|`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 a result of user request.<br /><br /> When users remove nodes from a pool (by resizing or shrinking it) or disable a job, they can choose to requeue the running tasks on those nodes for execution. This count tracks how many times the task is requeued for these reasons.|
 |`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.|