acrolinx

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

Author: hhunter-ms

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

@@ -6,15 +6,15 @@ ms.author: hannahhunter
 ms.reviewer: nickgreenf
 ms.service: azure-container-apps
 ms.topic: how-to 
-ms.date: 08/02/2024
+ms.date: 12/11/2024
 ms.custom: template-tutorial, service-connector, build-2023, engagement
 ---
 
 # Connect to Azure services via Dapr components in the Azure portal
 
 You can easily connect Dapr APIs to [backing Azure services](./dapr-overview.md#dapr-components) using a combination of [Service Connector](../service-connector/overview.md) and [Dapr](https://docs.dapr.io/). This feature creates Dapr components on your behalf with valid metadata and authenticated identity to access the Azure service.  
 
-In this guide, you'll connect Dapr Pub/Sub API to an Azure Service Bus by:
+In this guide, you connect Dapr Pub/Sub API to an Azure Service Bus by:
 > [!div class="checklist"]
 > - Select pub/sub as the API 
 > - Specify Azure Service Bus as the service and required properties like namespace, queue name, and identity
@@ -45,7 +45,7 @@ For example, for a pub/sub Azure Service Bus component, you'll start with the fo
 
 | Field | Example | Description |
 | ----- | ------- | ----------- |
-| Component name | mycomponent | Enter a name for your Dapr component. The name must match the component referenced in your application code. |
+| Component name | `mycomponent` | Enter a name for your Dapr component. The name must match the component referenced in your application code. |
 | Building block | Pub/sub | Select the [building block/API](https://docs.dapr.io/developing-applications/building-blocks/) for your component from the drop-down. |
 | Component type | Service Bus | Select a component type from the drop-down. |
 
@@ -54,9 +54,9 @@ The component creation pane populates with different fields depending on the bui
 | Field | Example | Description |
 | ----- | ------- | ----------- |
 | Subscription | My subscription | Select your Azure subscription |
-| Namespace | mynamespace | Select the Service Bus namespace |
+| Namespace | `mynamespace` | Select the Service Bus namespace |
 | Authentication | User assigned managed identity | Select the subscription that contains the component you're looking for. Recommended: User assigned managed identity. |
-| User assigned managed identity | testidentity | Select an existing identity from the drop-down. If you don’t  already have one, you can create a new managed identity client ID. |  
+| User assigned managed identity | `testidentity` | Select an existing identity from the drop-down. If you don’t  already have one, you can create a new managed identity client ID. |  
 
 :::image type="content" source="media/dapr-component-connection/add-pubsub-component.png" alt-text="Screenshot of the Azure platform showing the Basics tab of adding a Dapr Pub/sub component.":::
 

articles/container-apps/enable-dapr.md

@@ -1,6 +1,6 @@
 ---
 title: Enable Dapr on an existing container app
-description: Learn more about enabling Dapr on your Azure Container App service to develop applications.
+description: Enable Dapr on your existing Azure Container App service.
 ms.author: hannahhunter
 author: hhunter-ms
 ms.service: azure-container-apps
@@ -24,7 +24,7 @@ The following table outlines the currently supported list of Dapr sidecar config
 | `--enable-dapr`           | `dapr.enabled`            | Enables Dapr on the container app.                                                                                           |
 | `--dapr-app-port`         | `dapr.appPort`            | The port your application is listening on which is used by Dapr for communicating to your application                   |
 | `--dapr-app-protocol`     | `dapr.appProtocol`        | Tells Dapr which protocol your application is using. Valid options are `http` or `grpc`. Default is `http`.                  |
-| `--dapr-app-id`           | `dapr.appId`              | A unique Dapr identifier for your container app used for service discovery, state encapsulation and the pub/sub consumer ID. |
+| `--dapr-app-id`           | `dapr.appId`              | A unique Dapr identifier for your container app used for service discovery, state encapsulation, and the pub/sub consumer ID. |
 | `--dapr-max-request-size` | `dapr.httpMaxRequestSize` | Set the max size of request body http and grpc servers to handle uploading of large files. Default is 4 MB.                    |
 | `--dapr-read-buffer-size` | `dapr.httpReadBufferSize` | Set the max size of http header read buffer in to handle when sending multi-KB headers. The default 4 KB.                    |
 | `--dapr-api-logging`      | `dapr.enableApiLogging`   | Enables viewing the API calls from your application to the Dapr sidecar.                                                     |

articles/container-apps/microservices-dapr-azure-resource-manager.md

@@ -5,15 +5,15 @@ services: container-apps
 author: hhunter-ms
 ms.service: azure-container-apps
 ms.topic: quickstart
-ms.date: 12/04/2024
+ms.date: 12/11/2024
 ms.author: cshoe
 ms.custom: devx-track-bicep, devx-track-arm-template, devx-track-azurepowershell
 zone_pivot_groups: container-apps
 ---
 
 # Quickstart: Deploy a Dapr application to Azure Container Apps with an Azure Resource Manager or Bicep template
 
-[Dapr](./dapr-overview.md) (Distributed Application Runtime) helps developers build resilient, reliable microservices. In this quickstart, you learn how to enable Dapr sidecars to run alongside microservices container apps that produce and consume messages and store them in an Azure Blob Storage state store. Using either Azure Resource Manager or Bicep templates,  you'll:
+[Dapr](./dapr-overview.md) (Distributed Application Runtime) helps developers build resilient, reliable microservices. In this quickstart, you enable Dapr sidecars to run alongside two container apps that produce and consume messages, stored in an Azure Blob Storage state store. Using either Azure Resource Manager or Bicep templates,  you'll:
 
 > [!div class="checklist"]
 >
@@ -132,7 +132,7 @@ This command deploys:
    - A user-assigned identity with access to the Azure Blob storage via a Storage Data Contributor role assignment
 - A Dapr component of `"type": "state.azure.blobstorage"` scoped for use by the `nodeapp` for storing state.
 - The Dapr-enabled, headless `pythonapp` that invokes the `nodeapp` service using Dapr service invocation.
-- A Microsot Entra ID role assignment for the Node.js app used by the Dapr component to establish a connection to Blob storage.
+- A Microsoft Entra ID role assignment for the Node.js app used by the Dapr component to establish a connection to Blob storage.
 
 ## Verify the result
 
@@ -202,7 +202,7 @@ nodeapp               Got a new order! Order ID: 63    PrimaryResult  2021-10-22
 
 ## Clean up resources
 
-Since `pythonapp` continuously makes calls to `nodeapp` with messages that get persisted into your configured state store, it is important to complete these cleanup steps to avoid ongoing billable operations.
+Since `pythonapp` continuously makes calls to `nodeapp` with messages that get persisted into your configured state store, it's important to complete these cleanup steps to avoid ongoing billable operations.
 
 If you'd like to delete the resources created as a part of this walkthrough, run the following command.