edits, final

Author: ktoliver

articles/azure-functions/durable/durable-functions-configure-durable-functions-with-credentials.md

@@ -27,22 +27,22 @@ To complete this quickstart, you need:
 
 If you don't have an existing Durable Functions project deployed in Azure, we recommend that you start with one of the following quickstarts:
 
-* [Create your first Durable Functions app - C#](durable-functions-isolated-create-first-csharp.md)
-* [Create your first Durable Functions app - JavaScript](quickstart-js-vscode.md)
-* [Create your first Durable Functions app - Python](quickstart-python-vscode.md)
-* [Create your first Durable Functions app - PowerShell](quickstart-powershell-vscode.md)
-* [Create your first Durable Functions app - Java](quickstart-java.md)
+* [Create a Durable Functions app - C#](durable-functions-isolated-create-first-csharp.md)
+* [Create a Durable Functions app - JavaScript](quickstart-js-vscode.md)
+* [Create a Durable Functions app - Python](quickstart-python-vscode.md)
+* [Create a Durable Functions app - PowerShell](quickstart-powershell-vscode.md)
+* [Create a Durable Functions app - Java](quickstart-java.md)
 
 ## Configure your app to use managed identity credentials
 
-Your app can use a [managed identity](../../app-service/overview-managed-identity.md) to easily access other Microsoft Entra-protected resources, such as Azure Key Vault. Managed identity access is supported in the [Durable Functions extension](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.DurableTask) version 2.7.0 and later.
+Your app can use a [managed identity](../../app-service/overview-managed-identity.md) to easily access other Microsoft Entra-protected resources, such as an instance of Azure Key Vault. Managed identity access is supported in the [Durable Functions extension](https://www.nuget.org/packages/Microsoft.Azure.WebJobs.Extensions.DurableTask) version 2.7.0 and later.
 
 > [!NOTE]
 > A managed identity is available to apps only when they execute in Azure. When an app is configured to use identity-based connections, a locally executing app instead uses your *developer credentials* to authenticate with Azure resources. Then, when the app is deployed in Azure, it uses your managed identity configuration.
 
 ### Enable a managed identity
 
-To begin, enable a managed identity for your application. Your function app must have either a *system assigned managed identity* or a *user assigned managed identity*. To enable a managed identity for your function app, and to learn more about the differences between the two types of identities, see the [managed identity overview](../../app-service/overview-managed-identity.md).
+To begin, enable a managed identity for your application. Your function app must have either a *system-assigned managed identity* or a *user-assigned managed identity*. To enable a managed identity for your function app, and to learn more about the differences between the two types of identities, see the [managed identity overview](../../app-service/overview-managed-identity.md).
 
 ### Assign access roles to the managed identity
 
@@ -107,7 +107,7 @@ Before you can use your app's managed identity, make some changes to the app con
 
 ## Configure your app to use client secret credentials
 
-Registering a client application in Microsoft Entra ID is another way you can configure access to an Azure service for your Durable Functions app. In the following steps, you use client secret credentials for authentication to your Azure Storage account. Function apps can use this method both locally and in Azure. Using a client secret credential is *less recommended* than using managed identity credentials because a client secret is more complicated to configure and manage. A client secret credential also requires sharing a secret credential with the Azure Functions service.
+Registering a client application in Microsoft Entra ID is another way you can configure access to an Azure service for your Durable Functions app. In the following steps, you use client secret credentials for authentication to your Azure Storage account. Function apps can use this method both locally and in Azure. Using a client secret credential is *less recommended* than using managed identity credentials because a client secret is more complex to set up and manage. A client secret credential also requires sharing a secret credential with the Azure Functions service.
 
 <a name='register-a-client-application-on-azure-active-directory'></a>
 
@@ -125,7 +125,7 @@ Registering a client application in Microsoft Entra ID is another way you can co
 
    1. *Copy the secret value to use later*.
 
-      The secret value doesn't appear again after you leave the pane, so be sure that you *copy the secret and save it*.
+      The secret's value doesn't appear again after you leave the pane, so be sure that you *copy the secret and save it*.
 
    :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-01.png" alt-text="Screenshot that shows the Add a client secret pane." lightbox="media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-01.png":::
 
@@ -196,6 +196,6 @@ In the Azure portal, run and test the application. To run and test the app local
 
    * **AzureWebJobsStorage__tenantId**: The tenant ID that the Microsoft Entra application is registered in. Get this GUID value on the Microsoft Entra application pane.
 
-   The values to use for the client ID and the tenant ID appear on your client application Overview pane. The client secret value is the one that you saved in an earlier step. The client secret value isn't available after the pane is refreshed.
+   The values to use for the client ID and the tenant ID appear on your client application Overview pane. The client secret value is the one that you saved in an earlier step. The client secret's value isn't available after the pane is refreshed.
 
    :::image type="content" source="media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-04.png" alt-text="Screenshot that shows the tenant ID and client ID on a Microsoft Entra application pane." lightbox="media/durable-functions-configure-df-with-credentials/durable-functions-client-secret-scenario-04.png":::

articles/azure-functions/durable/durable-functions-isolated-create-first-csharp.md

@@ -12,7 +12,7 @@ ms.custom: mode-other, devdivchpfy22, vscode-azure-extension-update-complete, de
 
 # Quickstart: Create a C# Durable Functions app
 
-Durable Functions is a feature of [Azure Functions](../functions-overview.md). Use Durable Functions to write stateful functions in a serverless environment. Durable Functions manages state, checkpoints, and restarts in your application.
+Use Durable Functions, a feature of [Azure Functions](../functions-overview.md), to write stateful functions in a serverless environment. Durable Functions manages state, checkpoints, and restarts in your application.
 
 Like Azure Functions, Durable Functions supports two process models for .NET class library functions. To learn more about the two processes, see [Differences between in-process and isolated worker process .NET Azure Functions](../dotnet-isolated-in-process-differences.md).
 

articles/azure-functions/durable/durable-functions-monitor.md

@@ -30,7 +30,7 @@ The monitor pattern refers to a flexible *recurring* process in a workflow - for
 
 This sample monitors a location's current weather conditions and alerts a user by SMS when the skies are clear. You could use a regular timer-triggered function to check the weather and send alerts. However, one problem with this approach is **lifetime management**. If only one alert should be sent, the monitor needs to disable itself after clear weather is detected. The monitoring pattern can end its own execution, among other benefits:
 
-* Monitors run on intervals, not schedules: a timer trigger *runs* every hour; a monitor *waits* one hour between actions. A monitor's actions will not overlap unless specified, which can be important for long-running tasks.
+* Monitors run on intervals, not schedules: a timer trigger *runs* every hour; a monitor *waits* one hour between actions. A monitor's actions won't overlap unless specified, which can be important for long-running tasks.
 * Monitors can have dynamic intervals: the wait time can change based on some condition.
 * Monitors can terminate when some condition is met or be terminated by another process.
 * Monitors can take parameters. The sample shows how the same weather-monitoring process can be applied to any requested location and phone number.
@@ -47,7 +47,7 @@ This sample monitors a location's current weather conditions and alerts a user b
 
 This sample involves using the Weather Underground API to check current weather conditions for a location.
 
-The first thing you need is a Weather Underground account. You can create one for free at [https://www.wunderground.com/signup](https://www.wunderground.com/signup). Once you have an account, you will need to acquire an API key. You can do so by visiting [https://www.wunderground.com/weather/api](https://www.wunderground.com/weather/api/?MR=1), then selecting Key Settings. The Stratus Developer plan is free and sufficient to run this sample.
+The first thing you need is a Weather Underground account. You can create one for free at [https://www.wunderground.com/signup](https://www.wunderground.com/signup). Once you have an account, you need to acquire an API key. You can do so by visiting [https://www.wunderground.com/weather/api](https://www.wunderground.com/weather/api/?MR=1), then selecting Key Settings. The Stratus Developer plan is free and sufficient to run this sample.
 
 Once you have an API key, add the following **app setting** to your function app.
 
@@ -69,30 +69,30 @@ This article explains the following functions in the sample app:
 
 [!code-csharp[Main](~/samples-durable-functions/samples/precompiled/Monitor.cs?range=41-78,97-115)]
 
-The orchestrator requires a location to monitor and a phone number to send a message to when the whether becomes clear at the location. This data is passed to the orchestrator as a strongly typed `MonitorRequest` object.
+The orchestrator requires a location to monitor and a phone number to send a message to when the weather becomes clear at the location. This data is passed to the orchestrator as a strongly typed `MonitorRequest` object.
 
 # [JavaScript](#tab/javascript)
 
 The **E3_Monitor** function uses the standard *function.json* for orchestrator functions.
 
 :::code language="javascript" source="~/azure-functions-durable-js/samples/E3_Monitor/function.json":::
 
-Here is the code that implements the function:
+Here's the code that implements the function:
 
 :::code language="javascript" source="~/azure-functions-durable-js/samples/E3_Monitor/index.js":::
 
 ---
 
 This orchestrator function performs the following actions:
 
-1. Gets the **MonitorRequest** consisting of the *location* to monitor and the *phone number* to which it will send an SMS notification.
+1. Gets the **MonitorRequest** consisting of the *location* to monitor and the *phone number* to which it sends an SMS notification.
 2. Determines the expiration time of the monitor. The sample uses a hard-coded value for brevity.
 3. Calls **E3_GetIsClear** to determine whether there are clear skies at the requested location.
 4. If the weather is clear, calls **E3_SendGoodWeatherAlert** to send an SMS notification to the requested phone number.
 5. Creates a durable timer to resume the orchestration at the next polling interval. The sample uses a hard-coded value for brevity.
 6. Continues running until the current UTC time passes the monitor's expiration time, or an SMS alert is sent.
 
-Multiple orchestrator instances can run simultaneously by calling the orchestrator function multiple times. The location to monitor and the phone number to send an SMS alert to can be specified. Finally, do note that the orchestrator function is *not* running while waiting for the timer, so you will not get charged for it.
+Multiple orchestrator instances can run simultaneously by calling the orchestrator function multiple times. The location to monitor and the phone number to send an SMS alert to can be specified. Finally, do note that the orchestrator function isn't* running while waiting for the timer, so you won't get charged for it.
 ### E3_GetIsClear activity function
 
 As with other samples, the helper activity functions are regular functions that use the `activityTrigger` trigger binding. The **E3_GetIsClear** function gets the current weather conditions using the Weather Underground API and determines whether the sky is clear.
@@ -107,7 +107,7 @@ The *function.json* is defined as follows:
 
 :::code language="javascript" source="~/azure-functions-durable-js/samples/E3_GetIsClear/function.json":::
 
-And here is the implementation.
+And here's the implementation.
 
 :::code language="javascript" source="~/azure-functions-durable-js/samples/E3_GetIsClear/index.js":::
 
@@ -130,7 +130,7 @@ Its *function.json* is simple:
 
 :::code language="javascript" source="~/azure-functions-durable-js/samples/E3_SendGoodWeatherAlert/function.json":::
 
-And here is the code that sends the SMS message:
+And here's the code that sends the SMS message:
 
 :::code language="javascript" source="~/azure-functions-durable-js/samples/E3_SendGoodWeatherAlert/index.js":::
 
@@ -157,7 +157,7 @@ RetryAfter: 10
 {"id": "f6893f25acf64df2ab53a35c09d52635", "statusQueryGetUri": "https://{host}/runtime/webhooks/durabletask/instances/f6893f25acf64df2ab53a35c09d52635?taskHub=SampleHubVS&connection=Storage&code={systemKey}", "sendEventPostUri": "https://{host}/runtime/webhooks/durabletask/instances/f6893f25acf64df2ab53a35c09d52635/raiseEvent/{eventName}?taskHub=SampleHubVS&connection=Storage&code={systemKey}", "terminatePostUri": "https://{host}/runtime/webhooks/durabletask/instances/f6893f25acf64df2ab53a35c09d52635/terminate?reason={text}&taskHub=SampleHubVS&connection=Storage&code={systemKey}"}
 ```
 
-The **E3_Monitor** instance starts and queries the current weather conditions for the requested location. If the weather is clear, it calls an activity function to send an alert; otherwise, it sets a timer. When the timer expires, the orchestration will resume.
+The **E3_Monitor** instance starts and queries the current weather conditions for the requested location. If the weather is clear, it calls an activity function to send an alert; otherwise, it sets a timer. When the timer expires, the orchestration resumes.
 
 You can see the orchestration's activity by looking at the function logs in the Azure Functions portal.
 
@@ -177,15 +177,15 @@ You can see the orchestration's activity by looking at the function logs in the
 2018-03-01T01:14:54.030 Function completed (Success, Id=561d0c78-ee6e-46cb-b6db-39ef639c9a2c, Duration=62ms)
 ```
 
-The orchestration completes once its timeout is reached or clear skies are detected. You can also use the `terminate` API inside another function or invoke the **terminatePostUri** HTTP POST webhook referenced in the 202 response above. To use the webhook, replace `{text}` with the reason for the early termination. The HTTP POST URL will look roughly as follows:
+The orchestration completes once its timeout is reached or clear skies are detected. You can also use the `terminate` API inside another function or invoke the **terminatePostUri** HTTP POST webhook referenced in the preceding 202 response. To use the webhook, replace `{text}` with the reason for the early termination. The HTTP POST URL looks roughly as follows:
 
 ```
 POST https://{host}/runtime/webhooks/durabletask/instances/f6893f25acf64df2ab53a35c09d52635/terminate?reason=Because&taskHub=SampleHubVS&connection=Storage&code={systemKey}
 ```
 
 ## Next steps
 
-This sample has demonstrated how to use Durable Functions to monitor an external source's status using [durable timers](durable-functions-timers.md) and conditional logic. The next sample shows how to use external events and [durable timers](durable-functions-timers.md) to handle human interaction.
+This sample demonstrates how to use Durable Functions to monitor an external source's status using [durable timers](durable-functions-timers.md) and conditional logic. The next sample shows how to use external events and [durable timers](durable-functions-timers.md) to handle human interaction.
 
 > [!div class="nextstepaction"]
-> [Run the human interaction sample](durable-functions-phone-verification.md)
+> [Run the human interaction sample](durable-functions-phone-verification.md)

articles/azure-functions/durable/quickstart-java.md

@@ -12,7 +12,7 @@ zone_pivot_groups: create-java-durable-options
 
 # Quickstart: Create a Java Durable Functions app
 
-Durable Functions is a feature of [Azure Functions](../functions-overview.md). Use Durable Functions to write stateful functions in a serverless environment. Durable Functions manages state, checkpoints, and restarts in your application.
+Use Durable Functions, a feature of [Azure Functions](../functions-overview.md), to write stateful functions in a serverless environment. Durable Functions manages state, checkpoints, and restarts in your application.
 
 In this quickstart, you create and test a "hello world" Durable Functions app in Java.
 

articles/azure-functions/durable/quickstart-js-vscode.md

@@ -12,7 +12,7 @@ zone_pivot_groups: functions-nodejs-model
 
 # Quickstart: Create a JavaScript Durable Functions app
 
-Durable Functions is a feature of [Azure Functions](../functions-overview.md). Use Durable Functions to write stateful functions in a serverless environment. You install Durable Functions by installing the [Azure Functions extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions) in Visual Studio Code. The extension manages state, checkpoints, and restarts in your application.
+Use Durable Functions, a feature of [Azure Functions](../functions-overview.md), to write stateful functions in a serverless environment. You install Durable Functions by installing the [Azure Functions extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azurefunctions) in Visual Studio Code. The extension manages state, checkpoints, and restarts in your application.
 
 In this quickstart, you use the Durable Functions extension in Visual Studio Code to locally create and test a "hello world" Durable Functions app in Azure Functions. The Durable Functions app orchestrates and chains together calls to other functions. Then, you publish the function code to Azure. The tools you use are available via the Visual Studio Code extension.