Add edits

Author: cdpark

articles/container-apps/dapr-component-resiliency.md

@@ -278,7 +278,7 @@ properties: {
 
 | Metadata | Required | Description | Example |
 | -------- | --------- | ----------- | ------- |
-| `maxRetries` | Yes | Maximum retries to be executed for a failed http-request. | `5` |
+| `maxRetries` | Yes | Maximum retries to be executed for a failed http request. | `5` |
 | `retryBackOff` | Yes | Monitors the requests and shut off all traffic to the impacted service when timeout and retry criteria are met. | N/A |
 | `retryBackOff.initialDelayInMilliseconds` | Yes | Delay between first error and first retry. | `1000` |
 | `retryBackOff.maxIntervalInMilliseconds` | Yes | Maximum delay between retries. | `10000` |
@@ -353,7 +353,7 @@ Once debug logs are enabled, use a query similar to the following:
 ```
 ContainerAppConsoleLogs_CL
 | where ContainerName_s == "daprd"
-| where Log_s contains "Resiliency configuration:"
+| where Log_s contains "Resiliency configuration ("
 | project time_t, Category, ContainerAppName_s, Log_s
 | order by time_t desc
 ```

articles/container-apps/dapr-components.md

@@ -57,7 +57,7 @@ metadata:
 
 ## Component scopes
 
-By default, all Dapr-enabled container apps within the same environment load the full set of deployed components. To ensure only the appropriate container apps load components at runtime, application scopes should be used. In the following example, the component is only loaded by the two Dapr-enabled container apps with Dapr application IDs `APP-ID-1` and `APP-ID-2`:
+By default, all Dapr-enabled container apps within the same environment load the full set of deployed components. To ensure only the appropriate container apps load components at runtime, application scopes should be used. In the following example, the component is only loaded by the two Dapr-enabled container apps with Dapr application IDs `APP-ID-1` and `APP-ID-2`.
 
 ```yaml
 componentType: [COMPONENT-TYPE]
@@ -79,7 +79,7 @@ scopes:
 
 # [YAML](#tab/yaml)
 
-To create a Dapr component via the Container Apps CLI, you can use a container apps YAML manifest. When configuring multiple components, you must create and apply a separate YAML file for each component.
+To create a Dapr component by using the Container Apps CLI, you can use a container apps YAML manifest. When configuring multiple components, you must create and apply a separate YAML file for each component.
 
 ```azurecli
 az containerapp env dapr-component set --name <your-environment-name> --resource-group <your-resource-group> --dapr-component-name pubsub --yaml "./pubsub.yaml"
@@ -108,7 +108,7 @@ scopes:
 
 # [Bicep](#tab/bicep)
 
-This resource defines a Dapr component called `dapr-pubsub` via Bicep. The Dapr component is defined as a child resource of the Container Apps environment. To define multiple components, you can add a `daprComponent` resource for each.
+This resource defines a Dapr component called `dapr-pubsub` by using Bicep. The Dapr component is defined as a child resource of the Container Apps environment. To define multiple components, you can add a `daprComponent` resource for each.
 
 ```bicep
 resource daprComponent 'daprComponents@2022-03-01' = {
@@ -141,7 +141,7 @@ resource daprComponent 'daprComponents@2022-03-01' = {
 
 # [ARM](#tab/arm)
 
-This resource defines a Dapr component called `dapr-pubsub` via ARM template.
+This resource defines a Dapr component called `dapr-pubsub` by using an ARM template.
 
 ```json
 {

articles/container-apps/dapr-functions-extension.md

@@ -31,7 +31,7 @@ The [Dapr extension for Azure Functions](../azure-functions/functions-bindings-d
 
 ## Set up the environment
 
-1. In the terminal, sign in to your Azure subscription.
+1. In the terminal, sign in to your Azure account.
 
    ```azurecli
    az login
@@ -102,6 +102,8 @@ In the command:
 - Replace `<quickstart-functionapp-url>` with your actual function app URL. For example: `https://daprext-funcapp.wittyglacier-20884174.eastus.azurecontainerapps.io`.
 - Replace `<quickstart-functionapp-name>` with your function app name.
 
+To find your function app URL, navigate to **Container Appa** in the Azure portal, then select your new container app.
+
 # [PowerShell](#tab/powershell)
 
 ```powershell
@@ -176,11 +178,11 @@ curl --location 'https://<quickstart-functionapp-url.io>/api/retrieveorder'
 
 After you finish with this tutorial, run the following command to delete your resource group, along with all the resources you created.
 
-```
-az group delete --resource-group $RESOURCE_GROUP
+```azurecli
+az group delete --resource-group <resource-group-name>
 ```
 
 ## Related links
 
-- [Learn more about the Dapr extension for Azure Functions](../azure-functions/functions-bindings-dapr.md)
-- [Learn more about connecting Dapr components to your container app](./dapr-component-connection.md)
+- [Dapr Extension for Azure Functions](../azure-functions/functions-bindings-dapr.md)
+- [Connect to Azure services via Dapr components in the Azure portal](./dapr-component-connection.md)