edit pass: data-factory-batch2

Author: paulth1

articles/data-factory/how-to-create-tumbling-window-trigger.md

@@ -18,7 +18,9 @@ ms.date: 01/05/2024
 
 This article provides steps to create, start, and monitor a tumbling window trigger. For general information about triggers and the supported types, see [Pipeline execution and triggers](concepts-pipeline-execution-triggers.md).
 
-Tumbling window triggers are a type of trigger that fires at a periodic time interval from a specified start time, while retaining state. Tumbling windows are a series of fixed-sized, nonoverlapping, and contiguous time intervals. A tumbling window trigger has a one-to-one relationship with a pipeline and can only reference a singular pipeline. A tumbling window trigger is a more heavyweight alternative for a schedule trigger. It offers a suite of features for complex scenarios like ([dependency on other tumbling window triggers](#tumbling-window-trigger-dependency), [rerunning a failed job](tumbling-window-trigger-dependency.md#monitor-dependencies), and [setting user retry for pipelines](#user-assigned-retries-of-pipelines)). To further understand the difference between a schedule trigger and a tumbling window trigger, see [Trigger type comparison](concepts-pipeline-execution-triggers.md#trigger-type-comparison).
+Tumbling window triggers are a type of trigger that fires at a periodic time interval from a specified start time, while retaining state. Tumbling windows are a series of fixed-sized, nonoverlapping, and contiguous time intervals. A tumbling window trigger has a one-to-one relationship with a pipeline and can only reference a singular pipeline.
+
+A tumbling window trigger is a more heavyweight alternative for a schedule trigger. It offers a suite of features for complex scenarios like ([dependency on other tumbling window triggers](#tumbling-window-trigger-dependency), [rerunning a failed job](tumbling-window-trigger-dependency.md#monitor-dependencies), and [setting user retry for pipelines](#user-assigned-retries-of-pipelines)). To further understand the difference between a schedule trigger and a tumbling window trigger, see [Trigger type comparison](concepts-pipeline-execution-triggers.md#trigger-type-comparison).
 
 ## Azure Data Factory and Azure Synapse portal experience
 
@@ -97,17 +99,17 @@ The following table provides a high-level overview of the major JSON elements th
 
 | JSON element | Description | Type | Allowed values | Required |
 |:--- |:--- |:--- |:--- |:--- |
-| `type` | The type of the trigger. The `type` is the fixed value `TumblingWindowTrigger`. | String | `TumblingWindowTrigger` | Yes |
-| `runtimeState` | The current state of the trigger run time.<br/>This element is \<readOnly>. | String | `Started`, `Stopped`, `Disabled` | Yes |
-| `frequency` | A string that represents the frequency unit (minutes, hours, or months) at which the trigger recurs. If the `startTime` date values are more granular than the `frequency` value, the `startTime` dates are considered when the window boundaries are computed. For example, if the `frequency` value is hourly and the `startTime` value is 2017-09-01T10:10:10Z, the first window is (2017-09-01T10:10:10Z, 2017-09-01T11:10:10Z). | String | `Minute`, `Hour`, `Month`  | Yes |
-| `interval` | A positive integer that denotes the interval for the `frequency` value, which determines how often the trigger runs. For example, if the `interval` is 3 and the `frequency` is `hour`, the trigger recurs every 3 hours. <br/>The minimum window interval is 5 minutes. | Integer | A positive integer. | Yes |
-| `startTime`| The first occurrence, which can be in the past. The first trigger interval is (`startTime`, `startTime` + `interval`). | `DateTime` | A `DateTime` value. | Yes |
+| `type` | The type of the trigger. The `type` is the fixed value `TumblingWindowTrigger`. | `String` | `TumblingWindowTrigger` | Yes |
+| `runtimeState` | The current state of the trigger run time.<br/>This element is \<readOnly>. | `String` | `Started`, `Stopped`, `Disabled` | Yes |
+| `frequency` | A string that represents the frequency unit (minutes, hours, or months) at which the trigger recurs. If the `startTime` date values are more granular than the `frequency` value, the `startTime` dates are considered when the window boundaries are computed. For example, if the `frequency` value is `hourly` and the `startTime` value is 2017-09-01T10:10:10Z, the first window is (2017-09-01T10:10:10Z, 2017-09-01T11:10:10Z). | `String` | `Minute`, `Hour`, `Month`  | Yes |
+| `interval` | A positive integer that denotes the interval for the `frequency` value, which determines how often the trigger runs. For example, if the `interval` is `3` and the `frequency` is `hour`, the trigger recurs every 3 hours. <br/>The minimum window interval is 5 minutes. | `Integer` | A positive integer. | Yes |
+| `startTime`| The first occurrence, which can be in the past. The first trigger interval is (`startTime`, `startTime + interval`). | `DateTime` | A `DateTime` value. | Yes |
 | `endTime`| The last occurrence, which can be in the past. | `DateTime` | A `DateTime` value. | Yes |
-| `delay` | The amount of time to delay the start of data processing for the window. The pipeline run is started after the expected execution time plus the amount of `delay`. The `delay` defines how long the trigger waits past the due time before triggering a new run. The `delay` doesn’t alter the window `startTime`. For example, a `delay` value of 00:10:00 implies a delay of 10 minutes. | `Timespan`<br/>(hh:mm:ss)  | A `timespan` value where the default is 00:00:00. | No |
-| `maxConcurrency` | The number of simultaneous trigger runs that are fired for windows that are ready. For example, to backfill hourly runs for yesterday results in 24 windows. If `maxConcurrency` = 10, trigger events are fired only for the first 10 windows (00:00-01:00 - 09:00-10:00). After the first 10 triggered pipeline runs are complete, trigger runs are fired for the next 10 windows (10:00-11:00 - 19:00-20:00). Continuing with this example of `maxConcurrency` = 10, if there are 10 windows ready, there are 10 total pipeline runs. If only one window is ready, only one pipeline runs. | Integer | An integer between 1 and 50. | Yes |
-| `retryPolicy: Count` | The number of retries before the pipeline run is marked as `Failed`.  | Integer | An integer, where the default is 0 (no retries). | No |
-| `retryPolicy: intervalInSeconds` | The delay between retry attempts specified in seconds. | Integer | The number of seconds, where the default is 30. The minimum value is 30. | No |
-| `dependsOn: type` | The type of `TumblingWindowTriggerReference`. Required if a dependency is set. | String |  `TumblingWindowTriggerDependencyReference`, `SelfDependencyTumblingWindowTriggerReference` | No |
+| `delay` | The amount of time to delay the start of data processing for the window. The pipeline run is started after the expected execution time plus the amount of delay. The delay defines how long the trigger waits past the due time before triggering a new run. The delay doesn't alter the window `startTime`. For example, a `delay` value of 00:10:00 implies a delay of 10 minutes. | `Timespan`<br/>(hh:mm:ss)  | A `timespan` value where the default is `00:00:00`. | No |
+| `maxConcurrency` | The number of simultaneous trigger runs that are fired for windows that are ready. For example, to backfill hourly runs for yesterday results in 24 windows. If `maxConcurrency` = 10, trigger events are fired only for the first 10 windows (00:00-01:00 - 09:00-10:00). After the first 10 triggered pipeline runs are complete, trigger runs are fired for the next 10 windows (10:00-11:00 - 19:00-20:00). Continuing with this example of `maxConcurrency` = 10, if there are 10 windows ready, there are 10 total pipeline runs. If only one window is ready, only one pipeline runs. | `Integer` | An integer between 1 and 50. | Yes |
+| `retryPolicy: Count` | The number of retries before the pipeline run is marked as `Failed`.  | `Integer` | An integer, where the default is 0 (no retries). | No |
+| `retryPolicy: intervalInSeconds` | The delay between retry attempts specified in seconds. | `Integer` | The number of seconds, where the default is 30. The minimum value is `30`. | No |
+| `dependsOn: type` | The type of `TumblingWindowTriggerReference`. Required if a dependency is set. | `String` |  `TumblingWindowTriggerDependencyReference`, `SelfDependencyTumblingWindowTriggerReference` | No |
 | `dependsOn: size` | The size of the dependency tumbling window. | `Timespan`<br/>(hh:mm:ss)  | A positive `timespan` value where the default is the window size of the child trigger.  | No |
 | `dependsOn: offset` | The offset of the dependency trigger. | `Timespan`<br/>(hh:mm:ss) |  A `timespan` value that must be negative in a self-dependency. If no value is specified, the window is the same as the trigger itself. | Self-Dependency: Yes<br/>Other: No  |
 

articles/data-factory/tumbling-window-trigger-dependency.md

@@ -74,9 +74,9 @@ The following table provides the list of attributes needed to define a tumbling
 
 | Property name | Description  | Type | Required |
 |---|---|---|---|
-| type  | All the existing tumbling window triggers are displayed in this dropdown list. Choose the trigger to take dependency on.  | `TumblingWindowTriggerDependencyReference` or `SelfDependencyTumblingWindowTriggerReference` | Yes |
-| offset | Offset of the dependency trigger. Provide a value in the timespan format. Both negative and positive offsets are allowed. This property is mandatory if the trigger is depending on itself. In all other cases, it's optional. Self-dependency should always be a negative offset. If no value is specified, the window is the same as the trigger itself. | Timespan<br/>(hh:mm:ss) | Self-Dependency: Yes<br/>Other: No |
-| size | Size of the dependency tumbling window. Provide a positive timespan value. This property is optional. | Timespan<br/>(hh:mm:ss) | No  |
+| `type`  | All the existing tumbling window triggers are displayed in this dropdown list. Choose the trigger to take dependency on.  | `TumblingWindowTriggerDependencyReference` or `SelfDependencyTumblingWindowTriggerReference` | Yes |
+| `offset` | Offset of the dependency trigger. Provide a value in the timespan format. Both negative and positive offsets are allowed. This property is mandatory if the trigger is depending on itself. In all other cases, it's optional. Self-dependency should always be a negative offset. If no value is specified, the window is the same as the trigger itself. | Timespan<br/>(hh:mm:ss) | Self-Dependency: Yes<br/>Other: No |
+| `size` | Size of the dependency tumbling window. Provide a positive timespan value. This property is optional. | Timespan<br/>(hh:mm:ss) | No  |
 
 > [!NOTE]
 > A tumbling window trigger can depend on a maximum of five other triggers.
@@ -139,15 +139,15 @@ The following scenarios show the use of tumbling window dependency properties.
 
 ### Dependency on another tumbling window trigger
 
-The following example shows a daily telemetry processing job that depends on another daily job aggregating the last seven days output and generates seven-day rolling window streams.
+The following example shows a daily telemetry processing job that depends on another daily job aggregating the last seven days of output and generates seven-day rolling window streams.
 
 :::image type="content" source="media/tumbling-window-trigger-dependency/tumbling-window-dependency-05.png" alt-text="Diagram that shows a dependency example.":::
 
 ### Dependency on itself
 
 The following example shows a daily job with no gaps in the output streams of the job.
 
-:::image type="content" source="media/tumbling-window-trigger-dependency/tumbling-window-dependency-06.png" alt-text="Diagram that shows a self-dependency example.":::
+:::image type="content" source="media/tumbling-window-trigger-dependency/tumbling-window-dependency-06.png" alt-text="Diagram that shows a self-dependency example with no gaps in the output streams.":::
 
 ## Monitor dependencies
 
@@ -180,4 +180,4 @@ To rerun a window in the Gantt chart view, select the solid color box for the wi
 
 ## Related content
 
-[Create a tumbling window trigger](how-to-create-tumbling-window-trigger.md)
+- [Create a tumbling window trigger](how-to-create-tumbling-window-trigger.md)