Acrolinx

jonburchel · jonburchel · commit b71325087c44 · 2024-09-26T14:28:33.000-04:00
diff --git a/articles/data-factory/control-flow-append-variable-activity.md b/articles/data-factory/control-flow-append-variable-activity.md
@@ -24,9 +24,9 @@ To use a Append Variable activity in a pipeline, complete the following steps:
    :::image type="content" source="media/control-flow-activities-common/add-pipeline-array-variable.png" alt-text="Shows an empty pipeline canvas with the Variables tab selected having an array type variable named TestVariable.":::
 
 2. Search for _Append Variable_ in the pipeline Activities pane, and drag an Append Variable activity to the pipeline canvas.
-1. Select the Append Variable activity on the canvas if it is not already selected, and its  **Variables** tab, to edit its details.
+1. Select the Append Variable activity on the canvas if it isn't already selected, and its  **Variables** tab, to edit its details.
 1. Select the variable for the Name property.
-1. Enter an expression for the value, which will be appended to the array in the variable.  This can be a literal string expression, or any combination of dynamic [expressions, functions](control-flow-expression-language-functions.md), [system variables](control-flow-system-variables.md), or [outputs from other activities](how-to-expression-language-functions.md#examples-of-using-parameters-in-expressions).
+1. Enter an expression for the value, which is appended to the array in the variable. This can be a literal string expression, or any combination of dynamic [expressions, functions](control-flow-expression-language-functions.md), [system variables](control-flow-system-variables.md), or [outputs from other activities](how-to-expression-language-functions.md#examples-of-using-parameters-in-expressions).
 
    :::image type="content" source="media/control-flow-append-variable-activity/append-variable.png" alt-text="Shows the UI for an Append Variable activity.":::
 
@@ -41,7 +41,7 @@ Name | Name of the activity in pipeline | Yes
 Description | Text describing what the activity does | No
 Type | Activity Type is AppendVariable | Yes
 Value | String literal or expression object value used to append into specified variable | Yes
-VariableName | Name of the variable that will be modified by activity, the variable must be of type ‘Array’ | Yes
+VariableName | Name of the variable to be modified by activity, the variable must be of type ‘Array’ | Yes
 
 ## Related content
 Learn about a related control flow activity: 
diff --git a/articles/data-factory/control-flow-fail-activity.md b/articles/data-factory/control-flow-fail-activity.md
@@ -21,11 +21,11 @@ You might occasionally want to throw an error in a pipeline intentionally. A [Lo
 To use a Fail activity in a pipeline, complete the following steps:
 
 1. Search for _Fail_ in the pipeline Activities pane, and drag a Fail activity to the pipeline canvas.
-1. Select the new Fail activity on the canvas if it is not already selected, and its  **Settings** tab, to edit its details.
+1. Select the new Fail activity on the canvas if it isn't already selected, and its  **Settings** tab, to edit its details.
 
    :::image type="content" source="media/control-flow-fail-activity/fail-activity.png" alt-text="Shows the UI for a Fail activity.":::
 
-1. Enter a failure message and error code. These can be literal string expressions, or any combination of dynamic [expressions, functions](control-flow-expression-language-functions.md), [system variables](control-flow-system-variables.md), or [outputs from other activities](how-to-expression-language-functions.md#examples-of-using-parameters-in-expressions).
+1. Enter a failure message and error code. These values can be literal string expressions, or any combination of dynamic [expressions, functions](control-flow-expression-language-functions.md), [system variables](control-flow-system-variables.md), or [outputs from other activities](how-to-expression-language-functions.md#examples-of-using-parameters-in-expressions).
 
 ## Syntax
 
@@ -47,25 +47,25 @@ To use a Fail activity in a pipeline, complete the following steps:
 | --- | --- | --- | --- |
 | name | The name of the Fail activity. | String | Yes |
 | type | Must be set to **Fail**. | String | Yes |
-| message | The error message that surfaced in the Fail activity. It can be dynamic content that's evaluated at runtime. | String | Yes |
-| errorCode | The error code that categorizes the error type of the Fail activity. It can be dynamic content that's evaluated at runtime. | String | Yes |
+| message | The error message that surfaced in the Fail activity. It can be dynamic content to be evaluated at runtime. | String | Yes |
+| errorCode | The error code that categorizes the error type of the Fail activity. It can be dynamic content to be evaluated at runtime. | String | Yes |
 | | |
 
 ## Understand the Fail activity error code
 
-The error message and error code of a Fail activity are ordinarily set by users. To understand the specific meanings of the error codes, contact the pipeline developer. However, in the following edge cases, Azure Data Factory sets the error message and/or error code.
+Pipeline authors ordinarily set the error message and error code of the Fail activity. To understand the specific meanings of the error codes, contact the pipeline developer. However, in the following edge cases, Azure Data Factory sets the error message and/or error code.
 
 | Situation description | Error message | Error code |
 | --- | --- | --- |
-The (dynamic) content in `message` and `errorCode` is interpreted correctly. | The error message that's set by the user | The error code that's set by the user |
+The (dynamic) content in `message` and `errorCode` is interpreted correctly. | The error message set by the user | The error code set by the user |
 The dynamic content in both `message` and `errorCode` can't be interpreted. | "Failed to interpret _<activity_name>_ fail message or error code" | `ErrorCodeNotString` |
-| The dynamic content in `message` can't be interpreted as a string. | "_<activity_name>_ fail message parameter could not be interpreted as a string" | The error code that's set by the user |
-| The dynamic content in `message` resolves to null, an empty string, or white spaces. | "Failed to interpret _<activity_name>_ fail message or error code" | The error code that's set by the user |
-| The dynamic content in `errorCode` can't be interpreted as a string. | The error message that's set by the user | `ErrorCodeNotString` |
-| The dynamic content in `errorCode` resolves to null, an empty string, or white spaces. | The error message that's set by the user | `ErrorCodeNotString` |
+| The dynamic content in `message` can't be interpreted as a string. | "_<activity_name>_ fail message parameter couldn't be interpreted as a string" | The error code  set by the user |
+| The dynamic content in `message` resolves to null, an empty string, or white spaces. | "Failed to interpret _<activity_name>_ fail message or error code" | The error code set by the user |
+| The dynamic content in `errorCode` can't be interpreted as a string. | The error message set by the user | `ErrorCodeNotString` |
+| The dynamic content in `errorCode` resolves to null, an empty string, or white spaces. | The error message set by the user | `ErrorCodeNotString` |
 | The value for `message` or `errorCode` that's provided by the user isn't string-able.* | Pipeline _fails_ with: "Invalid value for property <`errorCode`/`message`>" | |
-| The `message` field is missing.* | "Fail message was not provided" | The error code that's set by the user |
-| The `errorCode` field is missing.* | The error message that's set by the user | `ErrorCodeNotString` |
+| The `message` field is missing.* | "Fail message wasn't provided" | The error code set by the user |
+| The `errorCode` field is missing.* | The error message set by the user | `ErrorCodeNotString` |
 | | |
 
 \* This situation shouldn't occur if the pipeline is developed with the web user interface (UI) of Data Factory.
diff --git a/articles/data-factory/control-flow-switch-activity.md b/articles/data-factory/control-flow-switch-activity.md
@@ -20,11 +20,11 @@ The Switch activity provides the same functionality that a switch statement prov
 
 To use a Switch activity in a pipeline, complete the following steps:
 1. Search for _Switch_ in the pipeline Activities pane, and add a Switch activity to the pipeline canvas.
-1. Select the Switch activity on the canvas if it is not already selected, and its  **Activities** tab, to edit its details.
+1. Select the Switch activity on the canvas if it isn't already selected, and its  **Activities** tab, to edit its details.
 1. Enter an expression for the Switch to evaluate.  This can be any combination of dynamic [expressions, functions](control-flow-expression-language-functions.md), [system variables](control-flow-system-variables.md), or [outputs from other activities](how-to-expression-language-functions.md#examples-of-using-parameters-in-expressions).
-1. Select **Add case** to add additional cases.  If no case matches, the Default case activity will be used.
+1. Select **Add case** to add more cases.  If no case matches, the Default case activity is used.
 1. Enter the value for the new case.
-1. Select the Edit button to add activities that will be executed when the expression evaluates to the matched case.
+1. Select the Edit button to add activities that are executed when the expression evaluates to the matched case.
 
 :::image type="content" source="media/control-flow-switch-activity/switch-activity-ui.png" alt-text="Shows the UI for a Switch activity with numbered indications of each step to configure it.":::
 
@@ -83,7 +83,7 @@ defaultActivities | Set of activities that are executed when the expression eval
 
 ## Example
 
-The pipeline in this example copies data from an input folder to an output folder. The output folder is determined by the value of pipeline parameter: routeSelection.
+The pipeline in this example copies data from an input folder to an output folder. The pipeline parameter **routeSelection** determines the output folder.
 
 > [!NOTE]
 > This section provides JSON definitions and sample PowerShell commands to run the pipeline. For a walkthrough with step-by-step instructions to create a Data Factory pipeline by using Azure PowerShell and JSON definitions, see [tutorial: create a data factory by using Azure PowerShell](quickstart-create-data-factory-powershell.md).
@@ -294,7 +294,7 @@ The pipeline sets the **folderPath** to the value of either **outputPath1** or *
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
-These commands assume that you've saved the JSON files into the folder: C:\ADF. 
+These commands assume you saved the JSON files into the folder: C:\ADF.
 
 ```powershell
 Connect-AzAccount
diff --git a/articles/data-factory/control-flow-validation-activity.md b/articles/data-factory/control-flow-validation-activity.md
@@ -14,14 +14,14 @@ ms.date: 09/26/2024
 # Validation activity in Azure Data Factory and Synapse Analytics pipelines
 [!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
 
-You can use a Validation in a pipeline to ensure the pipeline only continues execution once it has validated the attached dataset reference exists, that it meets the specified criteria, or timeout has been reached.
+You can use a Validation in a pipeline to ensure the pipeline only continues execution once it validates the attached dataset reference exists, that it meets the specified criteria, or times out.
 
 ## Create a Validation activity with UI
 
 To use a Validation activity in a pipeline, complete the following steps:
 
 1. Search for _Validation_ in the pipeline Activities pane, and drag a Validation activity to the pipeline canvas.
-1. Select the new Validation activity on the canvas if it is not already selected, and its  **Settings** tab, to edit its details.
+1. Select the new Validation activity on the canvas if it isn't already selected, and its  **Settings** tab, to edit its details.
 :::image type="content" source="media/control-flow-validation-activity/validation-activity.png" alt-text="Screenshot shows the UI for a Validation activity.":::
 1. Select a dataset, or define a new one by selecting the New button.  For file based datasets like the delimited text example above, you can select either a specific file, or a folder.  When a folder is selected, the Validation activity allows you to ignore validation of the existence of child items in the folder, or require whether child items exist or not.
 1. The output of the Validation activity can be used as an input to any other activities, and referenced within those activities for any of their properties using dynamic expressions.
@@ -65,10 +65,10 @@ To use a Validation activity in a pipeline, complete the following steps:
 |-------- | ----------- | -------------- | --------|
 |name | Name of the 'Validation' activity | String | Yes |
 |type | Must be set to  **Validation**. | String | Yes |
-|dataset | Activity will block execution until it has validated this dataset reference exists and that it meets the specified criteria, or timeout has been reached. Dataset provided should support "MinimumSize" or "ChildItems" property. | Dataset reference | Yes |
+|dataset | Activity blocks execution until it has validated this dataset reference exists and that it meets the specified criteria, or timeout has been reached. Dataset provided should support "MinimumSize" or "ChildItems" property. | Dataset reference | Yes |
 |timeout | Specifies the timeout for the activity to run. If no value is specified, default value is 12 hours ("0.12:00:00"). Format is d.hh:mm:ss | String | No |
 |sleep | A delay in seconds between validation attempts. If no value is specified, default value is 10 seconds. | Integer | No |
-|childItems | Checks if the folder has child items. Can be set to-true : Validate that the folder exists and that it has items. Blocks until at least one item is present in the folder or timeout value is reached.-false: Validate that the folder exists and that it is empty. Blocks until folder is empty or until timeout value is reached. If no value is specified, activity will block until the folder exists or until timeout is reached. | Boolean | No |
+|childItems | Checks if the folder has child items.<br/>**true**: Validates the folder exists and has items. Blocks until at least one item is present in the folder or timeout value is reached.<br/>**false**: Validates the folder exists and is empty. Blocks until folder is empty or until timeout value is reached. If no value is specified, activity will block until the folder exists or until timeout is reached. | Boolean | No |
 |minimumSize | Minimum size of a file in bytes. If no value is specified, default value is 0 bytes | Integer | No |
 
 
diff --git a/articles/data-factory/data-flow-alter-row.md b/articles/data-factory/data-flow-alter-row.md
diff --git a/articles/data-factory/self-hosted-integration-runtime-auto-update.md b/articles/data-factory/self-hosted-integration-runtime-auto-update.md
