acrolinx blockers

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

articles/azure-functions/durable/durable-functions-storage-providers.md

@@ -10,7 +10,7 @@ ms.author: azfuncdf
 
 # Durable Functions storage providers
 
-Durable Functions is a set of Azure Functions triggers and bindings that are internally powered by the [Durable Task Framework](https://github.com/Azure/durabletask) (DTFx). DTFx supports various backend storage providers, including the Azure Storage provider used by Durable Functions. Starting in Durable Functions **v2.5.0**, users can configure their function apps to use DTFx storage providers other than the Azure Storage provider.
+Durable Functions is a set of Azure Functions triggers and bindings that are internally powered by the [Durable Task Framework](https://github.com/Azure/durabletask) (DTFx). DTFx supports various backend storage providers, including the Azure Storage provider used by Durable Functions. As of Durable Functions **v2.5.0**, users can configure their function apps to use DTFx storage providers other than the Azure Storage provider.
 
 > [!NOTE]
 > The default Azure Storage provider for Durable Functions is the easiest to use since it requires no extra configuration. However, there are cost, scalability, and data management tradeoffs that may favor the use of an alternate backend provider.
@@ -22,11 +22,11 @@ Durable Functions supports two types of backend providers: "Bring your own (BYO)
 
 ## <a name="dts"></a>Durable task scheduler (preview)
 
-The durable task scheduler is a fuly managed, high performance backend provider for Durable Functions. It was designed and built from scratch with help from Microsoft Research. This new provider aims to provide the best user experience in aspects such as management, observability, performance, and security.  
+The durable task scheduler is a fully managed, high performance backend provider for Durable Functions. It was designed and built from scratch with help from Microsoft Research. This new provider aims to provide the best user experience in aspects such as management, observability, performance, and security.  
 
 The key benefits of the durable task scheduler include:
 
-* Significantly lower management and operation overhead compared to BYO backend providers
+* Lower management and operation overhead compared to BYO backend providers
 * First-class observability and management [dashboard](./durable-task-scheduler/durable-task-scheduler-dashboard.md) provided out-of-the-box. 
 * Supports the highest throughput of all backends today.
 * Support for authentication using managed identity.
@@ -50,15 +50,15 @@ The key benefits of the Azure Storage provider include:
 The source code for the DTFx components of the Azure Storage storage provider can be found in the [Azure/durabletask](https://github.com/Azure/durabletask/tree/main/src/DurableTask.AzureStorage) GitHub repo.
 
 > [!NOTE]
-> Standard general purpose Azure Storage accounts are required when using the Azure Storage provider. All other storage account types are not supported. We highly recommend using legacy v1 general purpose storage accounts because the newer v2 storage accounts can be significantly more expensive for Durable Functions workloads. For more information on Azure Storage account types, see the [Storage account overview](../../storage/common/storage-account-overview.md) documentation.
+> Standard general purpose Azure Storage accounts are required when using the Azure Storage provider. All other storage account types are not supported. We highly recommend using legacy v1 general purpose storage accounts because the newer v2 storage accounts can be more expensive for Durable Functions workloads. For more information on Azure Storage account types, see the [Storage account overview](../../storage/common/storage-account-overview.md) documentation.
 
 ## <a name="netherite"></a>Netherite
 
-The Netherite storage backend was designed and developed by [Microsoft Research](https://www.microsoft.com/research). It uses [Azure Event Hubs](../../event-hubs/event-hubs-about.md) and the [FASTER](https://www.microsoft.com/research/project/faster/) database technology on top of [Azure Page Blobs](../../storage/blobs/storage-blob-pageblob-overview.md). The design of Netherite enables significantly higher-throughput processing of orchestrations and entities compared to other providers. In some benchmark scenarios, throughput was shown to increase by more than an order of magnitude when compared to the default Azure Storage provider.
+The Netherite storage backend was designed and developed by [Microsoft Research](https://www.microsoft.com/research). It uses [Azure Event Hubs](../../event-hubs/event-hubs-about.md) and the [FASTER](https://www.microsoft.com/research/project/faster/) database technology on top of [Azure Page Blobs](../../storage/blobs/storage-blob-pageblob-overview.md). The design of Netherite enables higher-throughput processing of orchestrations and entities compared to other providers. In some benchmark scenarios, throughput was shown to increase by more than an order of magnitude when compared to the default Azure Storage provider.
 
 The key benefits of the Netherite storage provider include:
 
-* Significantly higher throughput at lower cost compared to other storage providers.
+* Higher throughput at lower cost compared to other storage providers.
 * Supports price-performance optimization, allowing you to scale-up performance as-needed.
 * Supports up to 32 data partitions with Event Hubs Basic and Standard SKUs.
 * More cost-effective than other providers for high-throughput workloads.

articles/azure-functions/durable/durable-task-scheduler/develop-with-durable-task-scheduler.md

@@ -3,15 +3,15 @@ title: Develop with the Azure Functions durable task scheduler (preview)
 description: Learn how to develop with the Azure Functions durable task scheduler and task hub resources
 author: lilyjma
 ms.topic: how-to
-ms.date: 03/17/2025
+ms.date: 03/19/2025
 ms.author: jiayma
 ms.reviewer: azfuncdf
 zone_pivot_groups: dts-devexp
 ---
 
 # Develop with the Azure Functions durable task scheduler (preview)
 
-The Azure Functions durable task scheduler is a highly performant, fully-managed backend provider for durable functions with an [out-of-the-box monitoring dashboard](./durable-task-scheduler-dashboard.md). In this article, you'll learn how to:
+The Azure Functions durable task scheduler is a highly performant, fully managed backend provider for durable functions with an [out-of-the-box monitoring dashboard](./durable-task-scheduler-dashboard.md). In this article, you learn how to:
 
 > [!div class="checklist"]
 > * Create a scheduler and task hub. 
@@ -28,7 +28,7 @@ Learn more about durable task scheduler [features](./durable-task-scheduler.md#f
 
 ## Set up the CLI
 
-1. Login to the Azure CLI and make sure you have the latest installed.
+1. Log in to the Azure CLI and make sure you have the latest installed.
 
     ```azurecli
     az login
@@ -41,7 +41,7 @@ Learn more about durable task scheduler [features](./durable-task-scheduler.md#f
     az extension add --name durabletask
     ```
 
-1. If you've already installed the durable task scheduler CLI extension, upgrade to the latest version.
+1. If you already installed the durable task scheduler CLI extension, upgrade to the latest version.
 
     ```azurecli
     az extension add --upgrade --name durabletask
@@ -62,7 +62,7 @@ Learn more about durable task scheduler [features](./durable-task-scheduler.md#f
    docker run -itP mcr.microsoft.com/dts/dts-emulator:v0.0.5
    ```
 
-    The command above exposes a single task hub named `default`. If you need more than one task hub, you can set the environment variable `DTS_TASK_HUB_NAMES` on the container to a comma-delimited list of task hub names like below:
+    This command exposes a single task hub named `default`. If you need more than one task hub, you can set the environment variable `DTS_TASK_HUB_NAMES` on the container to a comma-delimited list of task hub names like in the following command:
 
     ```bash
     docker run -itP -e DTS_TASK_HUB_NAMES=taskhub1,taskhub2,taskhub3 mcr.microsoft.com/dts/dts-emulator:v0.0.5
@@ -194,7 +194,7 @@ You can create a scheduler and a task hub as part of the Function app creation o
     az durabletask scheduler list --subscription <SUBSCRIPTION_ID>
     ```
 
-1. You can narrow results down to a specific resource group by adding the `--resource-group` flag.
+1. You can narrow down results to a specific resource group by adding the `--resource-group` flag.
 
     ```azurecli
     az durabletask scheduler list --subscription <SUBSCRIPTION_ID> --resource-group <RESOURCE_GROUP_NAME>
@@ -264,18 +264,18 @@ You can see all the task hubs created in a scheduler on the **Overview** of the
 
 ## Configure identity-based authentication for app to access durable task scheduler
 
-Durable task scheduler **only** supports either *user-assigned* or *system-assigned* managed identity authentication. **User-assigned identities are recommended,** as they aren't tied to the lifecycle of the app and can be reused after the app is de-provisioned.
+Durable task scheduler **only** supports either *user-assigned* or *system-assigned* managed identity authentication. **User-assigned identities are recommended,** as they aren't tied to the lifecycle of the app and can be reused after the app is deprovisioned.
 
 The following are the durable task scheduler related roles you can grant to an identity:
 
  - **Durable Task Data Contributor**: Role for all data access operations. This role is a superset of all other roles. 
  - **Durable Task Worker**: Role used by worker applications to interact with the durable task scheduler. Assign this role if your app is used *only* for processing orchestrations, activities, and entities. 
- - **Durable Task Data Reader**: Role to read all durable task scheduler data. Assign this role if you only need listing of orchestrations and entities payloads. 
+ - **Durable Task Data Reader**: Role to read all durable task scheduler data. Assign this role if you only need a list of orchestrations and entities payloads. 
 
 > [!NOTE]
 > Most durable functions apps would require the Durable Task Data Contributor role. 
 
-The sections below demonstrate how to grant permissions to an identity resource and configure your durable functions app to use the identity for access to schedulers and task hubs. 
+The following sections demonstrate how to grant permissions to an identity resource and configure your durable functions app to use the identity for access to schedulers and task hubs. 
 
 ### Assign RBAC (role-based access control) to managed identity resource 
 
@@ -384,7 +384,7 @@ Now that the identity has the required RBAC to access durable task scheduler, yo
 
 Add these two environment variables to app setting:
   - `TASKHUB_NAME`: name of task hub
-  - `DURABLE_TASK_SCHEDULER_CONNECTION_STRING`: the format of the string is `"Endpoint={scheduler point};Authentication=ManagedIdentity;ClientID={client id}"`, where *endpoint* is the scheduler endpoint and *client id* is the identity's client ID. 
+  - `DURABLE_TASK_SCHEDULER_CONNECTION_STRING`: the format of the string is `"Endpoint={scheduler point};Authentication=ManagedIdentity;ClientID={client id}"`, where `Endpoint` is the scheduler endpoint and `client id` is the identity's client ID. 
 
 ::: zone pivot="az-cli"
 
@@ -395,7 +395,7 @@ Add these two environment variables to app setting:
     az durabletask scheduler show --resource-group RESOURCE_GROUP_NAME --name DTS_NAME --query 'properties.endpoint' --output tsv
     ```
 
-    To get client id of managed identity.
+    To get the client ID of managed identity.
     ```azurecli
     az identity show --name MANAGED_IDENTITY_NAME --resource-group RESOURCE_GROUP_NAME --query 'clientId' --output tsv
     ```
@@ -434,7 +434,7 @@ Add these two environment variables to app setting:
 
 ## Accessing durable task scheduler dashboard
 
-First, follow instructions below to gain access to the [durable task scheduler dashboard](./durable-task-scheduler-dashboard.md) by assigning the required role to your *developer identity (email)*. After granting access, go to `https://dashboard.durabletask.io/` and fill out the required information about your scheduler and task hub to see the dashboard. 
+Assign the required role to your *developer identity (email)* to gain access to the [durable task scheduler dashboard](./durable-task-scheduler-dashboard.md). 
 
 ::: zone pivot="az-cli" 
 
@@ -493,6 +493,8 @@ First, follow instructions below to gain access to the [durable task scheduler d
     }
     ```
 
+1. After granting access, go to `https://dashboard.durabletask.io/` and fill out the required information about your scheduler and task hub to see the dashboard. 
+ 
 ::: zone-end 
 
 ::: zone pivot="az-portal" 

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler-dashboard.md

@@ -7,11 +7,11 @@ ms.date: 03/17/2025
 
 # Debug and manage orchestrations using the Azure Functions durable task scheduler dashboard (preview)
 
-Observe, manage, and debug your task hub or scheduler's orchestations effectively using the durable task scheduler dashboard. The dashboard is available when you run the [durable task scheduler emulator](./durable-task-scheduler.md#emulator-for-local-development) locally or create a scheduler resource on Azure. 
+Observe, manage, and debug your task hub or scheduler's orchestrations effectively using the durable task scheduler dashboard. The dashboard is available when you run the [durable task scheduler emulator](./durable-task-scheduler.md#emulator-for-local-development) locally or create a scheduler resource on Azure. 
 - **Running locally** doesn't require authentication. 
 - **Creating a scheduler resource on Azure** requires that you [assign the *Durable Task Data Contributor* role to your identity](./develop-with-durable-task-scheduler.md#accessing-durable-task-scheduler-dashboard). You can then access the dashboard via either:
   - The task hub's dashboard endpoint URL in the Azure portal
-  - Navigate to `https://dashboard.durabletask.io/` and your task hub endpoint to connect to it.  
+  - Navigate to `https://dashboard.durabletask.io/` combined with your task hub endpoint.  
 
 ## Monitor orchestration progress and execution history
 
@@ -25,9 +25,9 @@ View orchestration inputs and outputs:
 
 ## Detailed view of orchestration execution
 
-You can drill into orchestration instances to view execution details and activity progress, which can help in diagnosing problems or gaining visibility into the status of an orchestration.
+You can drill into orchestration instances to view execution details and activity progress. This view helps you diagnose problems or gain visibility into the status of an orchestration.
 
-For example, the following shows the *Timeline* view of an orchestration execution. In this "ProcessDocument" orchestration, the "WriteDoc" activity retried three times (unsuccessfully) with five seconds in between retry.
+In the following image, the *Timeline* view of an orchestration execution. In this "ProcessDocument" orchestration, the "WriteDoc" activity retried three times (unsuccessfully) with five seconds in between retry.
 
 :::image type="content" source="media/durable-task-scheduler-dashboard/orchestration-timeline.png" alt-text="Screenshot of the dashboard showing the orchestration execution timeline.":::
 

articles/azure-functions/durable/durable-task-scheduler/durable-task-scheduler.md

@@ -2,7 +2,7 @@
 title: Azure Functions durable task scheduler backend for durable functions (preview)
 description: Learn about the characteristics of the Azure Functions durable task scheduler backend.
 ms.topic: conceptual
-ms.date: 03/17/2025
+ms.date: 03/19/2025
 ms.author: azfuncdf
 author: hhunter-ms
 ms.subservice: durable
@@ -32,9 +32,9 @@ The following diagram shows the architecture of the durable task scheduler backe
 
 The durable task scheduler runs in Azure as a separate resource from the app. This separation allows the scheduler to scale independently of the app and provides better isolation between the two components. This isolation is important for several reasons:
 
-- **Reduced resource consumption:** BYO storage providers can consume a significant amount of CPU and memory resources. This resource consumption is due to the overhead of managing partitions and other complex state store interactions. By using a managed scheduler instead of a BYO storage provider, your app instances can run more efficiently and with less resource contention.
+- **Reduced resource consumption:** BYO storage providers can consume a significant amount of CPU and memory resources. This resource consumption is due to the overhead of managing partitions and other complex state store interactions. Using a managed scheduler instead of a BYO storage provider allows your app instances to run more efficiently and with less resource contention.
 
-- **Fault isolation:** Stability or availability issues in the durable task scheduler will not affect the stability or availability of your connected apps. With BYO storage providers, instability in the backend provider (which is a complex component) can create instability in the app logic. By separating the scheduler from the app, you can reduce the risk of cascading failures and improve overall reliability.
+- **Fault isolation:** Stability or availability issues in the durable task scheduler won't affect the stability or availability of your connected apps. With BYO storage providers, instability in the backend provider (which is a complex component) can create instability in the app logic. By separating the scheduler from the app, you can reduce the risk of cascading failures and improve overall reliability.
 
 - **Independent scaling:** The scheduler resource can be scaled independently of the app, allowing for better infrastructure resource management and cost optimization. For example, multiple apps can share the same scheduler resource, improving overall resource utilization. This capability is especially useful for organizations with multiple teams or projects that require durable functions.
 
@@ -44,7 +44,7 @@ The durable task scheduler runs in Azure as a separate resource from the app. Th
 
 Your durable function apps connect to the scheduler resource via a gRPC connection. The endpoint address is in the form `{scheduler-name}.{region}.durabletask.io`. For example, `myscheduler-123.westus2.durabletask.io`. The connection is secured using TLS and the app's identity is used to authenticate the connection.
 
-Work items are streamed from the scheduler to the app using a push model, removing the need for polling and improving end-to-end latency. Your apps can process multiple work items in parallel and will send responses back to the scheduler when the corresponding orchestration, activity, or entity task is complete.
+Work items are streamed from the scheduler to the app using a push model, removing the need for polling and improving end-to-end latency. Your apps can process multiple work items in parallel and send responses back to the scheduler when the corresponding orchestration, activity, or entity task is complete.
 
 ### State management
 
@@ -133,7 +133,7 @@ This benchmark showed that the durable task scheduler is roughly **five times fa
 
 - **Scheduler quota:** You can currently create up to **five schedulers per region** per subscription.
 
-- **Max payload size:** The durable task scheduler has a maximum payload size restrictions for the following JSON-serialized data types:
+- **Max payload size:** The durable task scheduler has a maximum payload size restriction for the following JSON-serialized data types:
 
     | Data type | Max size |
     | --------- | -------- |

articles/azure-functions/durable/durable-task-scheduler/includes/assign-dev-identity-rbac-portal.md

@@ -36,5 +36,6 @@ author: lilyjma
 
 1. Click **Review + assign** to finish assigning the role. 
 
+1. Once the role is assigned, click **Overview** on the left menu of the task hub resource and navigate to the dashboard URL located at the top *Essentials* section. 
 
 

articles/azure-functions/durable/durable-task-scheduler/includes/assign-rbac-portal.md

@@ -27,7 +27,7 @@ ms.date: 03/17/2025
 
 1. For **Members**, click **+ Select members**.
 
-1. In the **Select managed identities** pane, expand the **Managed identity** drop down and select **User-assigned managed identity**.
+1. In the **Select managed identities** pane, expand the **Managed identity** drop-down and select **User-assigned managed identity**.
 
     :::image type="content" source="../media/configure-durable-task-scheduler/members-tab.png" alt-text="Screenshot of selecting the user-assigned managed identity type you're going to use in the portal.":::