Resolving formatting, word choice, and accessibility

whhender · whhender · commit fce332a9c52d · 2026-02-03T17:45:05.000-05:00
diff --git a/articles/data-factory/control-flow-append-variable-activity.md b/articles/data-factory/control-flow-append-variable-activity.md
@@ -17,13 +17,13 @@ Use the Append Variable activity to add a value to an existing array variable de
 
 ## Create an Append Variable activity with UI
 
-To use a Append Variable activity in a pipeline, complete the following steps:
+To use an Append Variable activity in a pipeline, complete the following steps:
 
 1. Select the background of the pipeline canvas and use the Variables tab to add an array type variable:
 
-   :::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.":::
+    :::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. 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 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 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#expressions-with-parameters).
diff --git a/articles/data-factory/control-flow-web-activity.md b/articles/data-factory/control-flow-web-activity.md
@@ -20,7 +20,7 @@ ms.custom:
 Web Activity can be used to call a custom REST endpoint from an Azure Data Factory or Synapse pipeline. You can pass datasets and linked services to be consumed and accessed by the activity.
 
 > [!NOTE]
-> Web Activity is supported for invoking URLs that are hosted in a private virtual network as well by leveraging self-hosted integration runtime. The integration runtime should have a line of sight to the URL endpoint. 
+> Web Activity is supported for invoking URLs that are hosted in a private virtual network as well by using a self-hosted integration runtime. The integration runtime should have a line of sight to the URL endpoint. 
 
 > [!NOTE]
 > The maximum supported output response payload size is 4 MB.  
@@ -30,11 +30,11 @@ Web Activity can be used to call a custom REST endpoint from an Azure Data Facto
 To use a Web activity in a pipeline, complete the following steps:
 
 1. Search for _Web_ in the pipeline Activities pane, and drag a Web activity to the pipeline canvas.
-1. Select the new Web activity on the canvas if it is not already selected, and its  **Settings** tab, to edit its details.
+1. Select the new Web 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-web-activity/web-activity.png" alt-text="Shows the UI for a Web activity.":::
 
-1. Specify a URL, which can be a literal URL string, 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#expressions-with-parameters).  Provide other details to be submitted with the request.
+1. Specify a URL, which can be a literal URL string, 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#expressions-with-parameters). Provide other details to be submitted with the request.
 1. Use the output from the activity as the input to any other activity, and reference the output anywhere dynamic content is supported in the destination activity.
 
 ## Syntax
@@ -86,26 +86,26 @@ Property | Description | Allowed values | Required
 name | Name of the web activity | String | Yes
 type | Must be set to **WebActivity**. | String | Yes
 method | REST API method for the target endpoint. | String. <br/><br/>Supported Types: "GET", "POST", "PUT", "PATCH", "DELETE" | Yes
-url | Target endpoint and path | String (or expression with resultType of string). The activity will time out at 1 minute with an error if it does not receive a response from the endpoint. You can increase this response timeout up to 10 mins by updating the httpRequestTimeout property | Yes
+url | Target endpoint and path | String (or expression with resultType of string). The activity will time out at 1 minute with an error if it doesn't receive a response from the endpoint. You can increase this response timeout up to 10 mins by updating the httpRequestTimeout property | Yes
 httpRequestTimeout | Response timeout duration | hh:mm:ss with the max value as 00:10:00. If not explicitly specified defaults to 00:01:00 | No
 headers | Headers that are sent to the request. For example, to set the language and type on a request: `"headers" : { "Accept-Language": "en-us", "Content-Type": "application/json" }`. | String (or expression with resultType of string) | No
 body | Represents the payload that is sent to the endpoint.  | String (or expression with resultType of string). <br/><br/>See the schema of the request payload in [Request payload schema](#request-payload-schema) section. | Required for POST/PUT/PATCH methods. Optional for DELETE method.
-authentication | Authentication method used for calling the endpoint. Supported Types are "Basic, Client Certificate, System-assigned Managed Identity, User-assigned Managed Identity, Service Principal." For more information, see [Authentication](#authentication) section. If authentication is not required, exclude this property. | String (or expression with resultType of string) | No
+authentication | Authentication method used for calling the endpoint. Supported Types are "Basic, Client Certificate, System-assigned Managed Identity, User-assigned Managed Identity, Service Principal." For more information, see [Authentication](#authentication) section. If authentication isn't required, exclude this property. | String (or expression with resultType of string) | No
 turnOffAsync | Option to disable invoking HTTP GET on location field in the response header of an HTTP 202 Response. If set true, it stops invoking HTTP GET on http location given in response header. If set false then it continues to invoke HTTP GET call on location given in http response headers. | Allowed values are false (default) and true. | No
-disableCertValidation | Removes server side certificate validation (not recommended unless you are connecting to a trusted server that does not use a standard CA cert). | Allowed values are false (default) and true. | No
+disableCertValidation | Removes server side certificate validation (not recommended unless you're connecting to a trusted server that doesn't use a standard CA cert). | Allowed values are false (default) and true. | No
 datasets | List of datasets passed to the endpoint. | Array of dataset references. Can be an empty array. | Yes
 linkedServices | List of linked services passed to endpoint. | Array of linked service references. Can be an empty array. | Yes
 connectVia | The [integration runtime](./concepts-integration-runtime.md) to be used to connect to the data store. You can use the Azure integration runtime or the self-hosted integration runtime (if your data store is in a private network). If this property isn't specified, the service uses the default Azure integration runtime. | The integration runtime reference. | No 
 
 > [!NOTE]
-> REST endpoints that the web activity invokes must return a response of type JSON. The activity will timeout at 1 minute with an error if it does not receive a response from the endpoint. For endpoints that support [Asynchronous Request-Reply pattern](/azure/architecture/patterns/async-request-reply), the web activity will continue to wait without timing out (upto 7 day) or till the endpoints signals completion of the job. 
+> REST endpoints that the web activity invokes must return a response of type JSON. The activity will time out at 1 minute with an error if it doesn't receive a response from the endpoint. For endpoints that support [Asynchronous Request-Reply pattern](/azure/architecture/patterns/async-request-reply), the web activity continues to wait without timing out (upto 7 day) or until the endpoints signals completion of the job. 
 
 The following table shows the requirements for JSON content:
 
 | Value type | Request body | Response body |
 |---|---|---|
 |JSON object | Supported | Supported |
-|JSON array | Supported <br/>(At present, JSON arrays don't work as a result of a bug. A fix is in progress.) | Unsupported |
+|JSON array | Supported <br/>(Currently, JSON arrays don't work as a result of a bug. A fix is in progress.) | Unsupported |
 | JSON value | Supported | Unsupported |
 | Non-JSON type | Unsupported | Unsupported |
 ||||
@@ -116,7 +116,7 @@ Below are the supported authentication types in the web activity.
 
 ### None
 
-If authentication is not required, do not include the "authentication" property.
+If authentication isn't required, don't include the "authentication" property.
 
 ### Basic
 
@@ -141,7 +141,7 @@ Specify base64-encoded contents of a PFX file and the password.
    "password":"****"
 }
 ```
-Certificate needs to be an x509 certificate. For conversion to PFX file, you can use your favorite utility. For base-64 encoding, you may use following PowerShell snippet.
+Certificate needs to be an x509 certificate. For conversion to PFX file, you can use your favorite utility. For base-64 encoding, you can use following PowerShell snippet.
 
 ```
 $fileContentBytes = get-content 'enr.dev.webactivity.pfx' -AsByteStream
@@ -150,7 +150,7 @@ $fileContentBytes = get-content 'enr.dev.webactivity.pfx' -AsByteStream
 ```
 ### Managed Identity
 
-Specify the resource uri for which the access token will be requested using the managed identity for the data factory or Synapse workspace instance. To call the Azure Resource Management API, use `https://management.azure.com/`. For more information about how managed identities works see the [managed identities for Azure resources overview page](../active-directory/managed-identities-azure-resources/overview.md).
+Specify the resource uri for which the access token will be requested using the managed identity for the data factory or Synapse workspace instance. To call the Azure Resource Management API, use `https://management.azure.com/`. For more information about how managed identities works, see the [managed identities for Azure resources overview page](../active-directory/managed-identities-azure-resources/overview.md).
 
 ```json
 "authentication": {
@@ -160,7 +160,7 @@ Specify the resource uri for which the access token will be requested using the
 ```
 
 > [!NOTE]
-> If your data factory or Synapse workspace is configured with a git repository, you must store your credentials in Azure Key Vault to use basic or client certificate authentication. The service does not store passwords in git.
+> If your data factory or Synapse workspace is configured with a git repository, you must store your credentials in Azure Key Vault to use basic or client certificate authentication. The service doesn't store passwords in git.
 
 ### Service principal
 
@@ -180,7 +180,7 @@ Specify the tenant ID, service principal ID, and service principal key, using a
 ```
 
 ## Request payload schema
-When you use the POST/PUT method, the body property represents the payload that is sent to the endpoint. You can pass linked services and datasets as part of the payload. Here is the schema for the payload:
+When you use the POST/PUT method, the body property represents the payload that is sent to the endpoint. You can pass linked services and datasets as part of the payload. Here's the schema for the payload:
 
 ```json
 {
diff --git a/articles/data-factory/includes/parameterize-linked-service-ui.md b/articles/data-factory/includes/parameterize-linked-service-ui.md
@@ -10,13 +10,13 @@ ms.custom: include file
 
 # [Azure Data Factory](#tab/data-factory)
 
-:::image type="content" source="../media/parameterize-linked-services/parameterize-linked-services-image-1.png" alt-text="Add dynamic content to the Linked Service definition" lightbox="../media/parameterize-linked-services/parameterize-linked-services-image-1.png":::
+:::image type="content" source="../media/parameterize-linked-services/parameterize-linked-services-image-1.png" alt-text="Screenshot highlighting the dynamic content link under the fully qualified domain name box in the linked service." lightbox="../media/parameterize-linked-services/parameterize-linked-services-image-1.png":::
 
-:::image type="content" source="../media/parameterize-linked-services/parameterize-linked-services-image-2.png" alt-text="Create a new parameter" lightbox="../media/parameterize-linked-services/parameterize-linked-services-image-2.png":::
+:::image type="content" source="../media/parameterize-linked-services/parameterize-linked-services-image-2.png" alt-text="Screenshot highlighting the dynamic content box and the + button to create a new parameter." lightbox="../media/parameterize-linked-services/parameterize-linked-services-image-2.png":::
 
 # [Azure Synapse](#tab/synapse-analytics)
 
-:::image type="content" source="../media/parameterize-linked-services/parameterize-linked-services-image-1-synapse.png" alt-text="Add dynamic content to the Linked Service definition" lightbox="../media/parameterize-linked-services/parameterize-linked-services-image-1-synapse.png":::
-:::image type="content" source="../media/parameterize-linked-services/parameterize-linked-services-image-2-synapse.png" alt-text="Create a new parameter" lightbox="../media/parameterize-linked-services/parameterize-linked-services-image-2-synapse.png":::
+:::image type="content" source="../media/parameterize-linked-services/parameterize-linked-services-image-1-synapse.png" alt-text="Screenshot highlighting the dynamic content link under the database name box in the linked service." lightbox="../media/parameterize-linked-services/parameterize-linked-services-image-1-synapse.png":::
+:::image type="content" source="../media/parameterize-linked-services/parameterize-linked-services-image-2-synapse.png" alt-text="Screenshot highlighting the + button to create a new parameter." lightbox="../media/parameterize-linked-services/parameterize-linked-services-image-2-synapse.png":::
 
 ---
diff --git a/articles/data-factory/parameterize-linked-services.md b/articles/data-factory/parameterize-linked-services.md
@@ -92,7 +92,7 @@ All the linked service types are supported for parameterization.
 **Advanced authoring:** For other linked service types that are not in above list, you can parameterize the linked service by editing the JSON on UI:
 
 - In linked service creation/edit blade -> expand "Advanced" at the bottom -> check "Specify dynamic contents in JSON format" checkbox -> specify the linked service JSON payload. 
-- Or, after you create a linked service without parameterization, in [Management hub](author-visually.md#management-hub) -> Linked services -> find the specific linked service -> click "Code" (button "{}") to edit the JSON. 
+- Or, after you create a linked service without parameterization, in [Management hub](author-visually.md#management-hub) -> Linked services -> find the specific linked service -> select the "Code" (button "{}") to edit the JSON. 
 
 Refer to the [JSON sample](#json) to add ` parameters` section to define parameters and reference the parameter using ` @{linkedService().paramName} `.
 
