Fixed review issues

jonburchel · jonburchel · commit ae1ec996d1c4 · 2022-01-27T19:50:13.000-05:00
diff --git a/articles/data-factory/concepts-pipeline-execution-triggers.md b/articles/data-factory/concepts-pipeline-execution-triggers.md
@@ -159,7 +159,7 @@ Triggers are another way that you can execute a pipeline run. Triggers represent
 
 - Event-based trigger: A trigger that responds to an event.
 
-Pipelines and triggers have a many-to-many relationship (except for the tumbling window trigger).Multiple triggers can kick off a single pipeline, or a single trigger can kick off multiple pipelines. In the following trigger definition, the **pipelines** property refers to a list of pipelines that are triggered by the particular trigger. The property definition includes values for the pipeline parameters.
+Pipelines and triggers have a many-to-many relationship (except for the tumbling window trigger). Multiple triggers can kick off a single pipeline, or a single trigger can kick off multiple pipelines. In the following trigger definition, the **pipelines** property refers to a list of pipelines that are triggered by the particular trigger. The property definition includes values for the pipeline parameters.
 ### Basic trigger definition
 
 ```json
@@ -393,10 +393,10 @@ The following table provides a comparison of the tumbling window trigger and sch
 
 ## Event-based trigger
 
-An event-based trigger runs pipelines in response to an event. There are two flavors of event based triggers.
+An event-based trigger runs pipelines in response to an event. There are two flavors of event-based triggers.
 
 * _Storage event trigger_ runs a pipeline against events happening in a Storage account, such as the arrival of a file, or the deletion of a file in Azure Blob Storage account.
-* _Custom event trigger_ processes and handles [custom topics](../event-grid/custom-topics.md) in Event Grid
+* _Custom event trigger_ processes and handles [custom articles](../event-grid/custom-topics.md) in Event Grid
 
 For more information about event-based triggers, see [Storage Event Trigger](how-to-create-event-trigger.md) and [Custom Event Trigger](how-to-create-custom-event-trigger.md).
 
diff --git a/articles/data-factory/control-flow-system-variables.md b/articles/data-factory/control-flow-system-variables.md
@@ -80,7 +80,7 @@ These system variables can be referenced anywhere in the trigger JSON for trigge
 
 | Variable Name | Description
 | --- | --- |
-| @triggerBody().event.eventType | Type of events that triggered the Custom Event Trigger run. Event type is customer defined field and take on any values of string type. |
+| @triggerBody().event.eventType | Type of events that triggered the Custom Event Trigger run. Event type is customer-defined field and take on any values of string type. |
 | @triggerBody().event.subject | Subject of the custom event that caused the trigger to fire. |
 | @triggerBody().event.data._keyName_ | Data field in custom event is a free from JSON blob, which customer can use to send messages and data. Please use data._keyName_ to reference each field. For example, @triggerBody().event.data.callback returns the value for the _callback_ field stored under _data_. |
 | @trigger().startTime | Time at which the trigger fired to invoke the pipeline run. |
diff --git a/articles/data-factory/how-to-create-custom-event-trigger.md b/articles/data-factory/how-to-create-custom-event-trigger.md
@@ -110,9 +110,9 @@ As of today custom event trigger supports a __subset__ of [advanced filtering op
 * StringIn
 * StringNotIn
 
-Click **+New** to add new filter conditions. 
+Select **+New** to add new filter conditions. 
 
-Additionally, custom event triggers obey the [same limitations as event grid](../event-grid/event-filtering.md#limitations), including:
+Additionally, custom event triggers obey the [same limitations as Event Grid](../event-grid/event-filtering.md#limitations), including:
 
 * 5 advanced filters and 25 filter values across all the filters per custom event trigger
 * 512 characters per string value
@@ -128,7 +128,7 @@ The following table provides an overview of the schema elements that are related
 
 | JSON element | Description | Type | Allowed values | Required |
 |---|----------------------------|---|---|---|
-| `scope` | The Azure Resource Manager resource ID of the event grid topic. | String | Azure Resource Manager ID | Yes |
+| `scope` | The Azure Resource Manager resource ID of the Event Grid topic. | String | Azure Resource Manager ID | Yes |
 | `events` | The type of events that cause this trigger to fire. | Array of strings    |  | Yes, at least one value is expected. |
 | `subjectBeginsWith` | The `subject` field must begin with the provided pattern for the trigger to fire. For example, _factories_ only fire the trigger for event subjects that start with *factories*. | String   | | No |
 | `subjectEndsWith` | The `subject` field must end with the provided pattern for the trigger to fire. | String   | | No |
@@ -143,7 +143,7 @@ Azure Data Factory uses Azure role-based access control (RBAC) to prohibit unaut
 
 To successfully create or update a custom event trigger, you need to sign in to Data Factory with an Azure account that has appropriate access. Otherwise, the operation will fail with an _Access Denied_ error.
 
-Data Factory doesn't require special permission to your Event Grid. You also do *not* need to assign special Azure RBAC permission to the Data Factory service principal for the operation.
+Data Factory doesn't require special permission to your Event Grid. You also do *not* need to assign special Azure RBAC role permission to the Data Factory service principal for the operation.
 
 Specifically, you need `Microsoft.EventGrid/EventSubscriptions/Write` permission on `/subscriptions/####/resourceGroups//####/providers/Microsoft.EventGrid/topics/someTopics`.
 
diff --git a/articles/data-factory/how-to-create-schedule-trigger.md b/articles/data-factory/how-to-create-schedule-trigger.md
@@ -206,7 +206,7 @@ This section shows you how to use Azure CLI to create, start, and monitor a sche
 
 ### Sample Code
 
-1. In your working direactory, create a JSON file named **MyTrigger.json** with the trigger's properties. For this example use the following content:
+1. In your working directory, create a JSON file named **MyTrigger.json** with the trigger's properties. For this example use the following content:
 
     > [!IMPORTANT]
     > Before you save the JSON file, set the value of the **startTime** element to the current UTC time. Set the value of the **endTime** element to one hour past the current UTC time.
@@ -252,31 +252,31 @@ This section shows you how to use Azure CLI to create, start, and monitor a sche
     - The trigger is associated with the **Adfv2QuickStartPipeline** pipeline. To associate multiple pipelines with a trigger, add more **pipelineReference** sections.
     - The pipeline in the Quickstart takes two **parameters** values: **inputPath** and **outputPath**. And you pass values for these parameters from the trigger.
 
-1. Create a trigger by using the [az datafactory trigger create](/cli/azure/datafactory/trigger#az_datafactory_trigger_create) command:
+1. Create a trigger by using the [az data factory trigger create](/cli/azure/datafactory/trigger#az_datafactory_trigger_create) command:
 
     ```azurecli
     az datafactory trigger create --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory"  --name "MyTrigger" --properties @MyTrigger.json  
     ```
 
-1. Confirm that the status of the trigger is **Stopped** by using the [az datafactory trigger show](/cli/azure/datafactory/trigger#az_datafactory_trigger_show) command:
+1. Confirm that the status of the trigger is **Stopped** by using the [az data factory trigger show](/cli/azure/datafactory/trigger#az_datafactory_trigger_show) command:
 
     ```azurecli
     az datafactory trigger show --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory" --name "MyTrigger" 
     ```
 
-1. Start the trigger by using the [az datafactory trigger start](/cli/azure/datafactory/trigger#az_datafactory_trigger_start) command:
+1. Start the trigger by using the [az data factory trigger start](/cli/azure/datafactory/trigger#az_datafactory_trigger_start) command:
 
     ```azurecli
     az datafactory trigger start --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory" --name "MyTrigger" 
     ```
 
-1. Confirm that the status of the trigger is **Started** by using the [az datafactory trigger show](/cli/azure/datafactory/trigger#az_datafactory_trigger_show) command:
+1. Confirm that the status of the trigger is **Started** by using the [az data factory trigger show](/cli/azure/datafactory/trigger#az_datafactory_trigger_show) command:
 
     ```azurecli
     az datafactory trigger show --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory" --name "MyTrigger" 
     ```
 
-1. Get the trigger runs in Azure CLI by using the [az datafactory trigger-run query-by-factory](/cli/azure/datafactory/trigger-run#az_datafactory_trigger_run_query_by_factory) command. To get information about the trigger runs, execute the following command periodically. Update the **last-updated-after** and  **last-updated-before** values to match the values in your trigger definition:
+1. Get the trigger runs in Azure CLI by using the [az data factory trigger-run query-by-factory](/cli/azure/datafactory/trigger-run#az_datafactory_trigger_run_query_by_factory) command. To get information about the trigger runs, execute the following command periodically. Update the **last-updated-after** and  **last-updated-before** values to match the values in your trigger definition:
 
     ```azurecli
     az datafactory trigger-run query-by-factory --resource-group "ADFQuickStartRG" --factory-name "ADFTutorialFactory" --filters operand="TriggerName" operator="Equals" values="MyTrigger" --last-updated-after "2017-12-08T00:00:00" --last-updated-before "2017-12-08T01:00:00"
@@ -472,7 +472,7 @@ The following table provides a high-level overview of the major schema elements
 |:--- |:--- |
 | **startTime** | A Date-Time value. For simple schedules, the value of the **startTime** property applies to the first occurrence. For complex schedules, the trigger starts no sooner than the specified **startTime** value. <br> For UTC time zone, format is `'yyyy-MM-ddTHH:mm:ssZ'`, for other time zone, format is `'yyyy-MM-ddTHH:mm:ss'`. |
 | **endTime** | The end date and time for the trigger. The trigger doesn't execute after the specified end date and time. The value for the property can't be in the past. This property is optional.  <br> For UTC time zone, format is `'yyyy-MM-ddTHH:mm:ssZ'`, for other time zone, format is `'yyyy-MM-ddTHH:mm:ss'`. |
-| **timeZone** | The time zone the trigger is created in. This setting impact **startTime**, **endTime**, and **schedule**. See [list of supported time zone](#time-zone-option) |
+| **timeZone** | The time zone the trigger is created in. This setting affects **startTime**, **endTime**, and **schedule**. See [list of supported time zone](#time-zone-option) |
 | **recurrence** | A recurrence object that specifies the recurrence rules for the trigger. The recurrence object supports the **frequency**, **interval**, **endTime**, **count**, and **schedule** elements. When a recurrence object is defined, the **frequency** element is required. The other elements of the recurrence object are optional. |
 | **frequency** | The unit of frequency at which the trigger recurs. The supported values include "minute," "hour," "day," "week," and "month." |
 | **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 "week," the trigger recurs every 3 weeks. |
diff --git a/articles/data-factory/how-to-use-trigger-parameterization.md b/articles/data-factory/how-to-use-trigger-parameterization.md
@@ -29,15 +29,15 @@ This section shows you how to pass meta data information from trigger to pipelin
 
 1. Go to the **Authoring Canvas** and edit a pipeline
 
-1. Click on the blank canvas to bring up pipeline settings. Do not select any activity. You may need to pull up the setting panel from the bottom of the canvas, as it may have been collapsed
+1. Select on the blank canvas to bring up pipeline settings. Don’t select any activity. You may need to pull up the setting panel from the bottom of the canvas, as it may have been collapsed
 
 1. Select **Parameters** section and select **+ New** to add parameters
 
     :::image type="content" source="media/how-to-use-trigger-parameterization/01-create-parameter.png" alt-text="Screen shot of pipeline setting showing how to define parameters in pipeline.":::
 
 1. Add triggers to pipeline, by clicking on **+ Trigger**.
 
-1. Create or attach a trigger to the pipeline, and click **OK**
+1. Create or attach a trigger to the pipeline, and select **OK**
 
 1. In the following page, fill in trigger meta data for each parameter. Use format defined in [System Variable](control-flow-system-variables.md) to retrieve trigger information. You don't need to fill in the information for all parameters, just the ones that will assume trigger metadata values. For instance, here we assign trigger run start time to *parameter_1*.
 
