Merge pull request #229178 from hhunter-ms/hh-29986

[Dapr/ACA] Add release cadence language

Author: prmerger-automator[bot]

articles/container-apps/dapr-overview.md

@@ -11,7 +11,7 @@ ms.date: 01/25/2023
 
 # Dapr integration with Azure Container Apps
 
-The Distributed Application Runtime ([Dapr][dapr-concepts]) is a set of incrementally adoptable features that simplify the authoring of distributed, microservice-based applications. For example, Dapr provides capabilities for enabling application intercommunication, whether through messaging via pub/sub or reliable and secure service-to-service calls. Once Dapr is enabled for a container app, a secondary process will be created alongside your application code that will enable communication with Dapr via HTTP or gRPC.
+The Distributed Application Runtime ([Dapr][dapr-concepts]) is a set of incrementally adoptable features that simplify the authoring of distributed, microservice-based applications. For example, Dapr provides capabilities for enabling application intercommunication, whether through messaging via pub/sub or reliable and secure service-to-service calls. Once Dapr is enabled for a container app, a secondary process is created alongside your application code that enables communication with Dapr via HTTP or gRPC.
 
 Dapr's APIs are built on best practice industry standards, that:
 
@@ -68,7 +68,7 @@ The table below outlines the currently supported list of Dapr sidecar configurat
 | Container Apps CLI        | Template field            | Description                                                                                                                  |
 | ------------------------- | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
 | `--enable-dapr`           | `dapr.enabled`            | Enables Dapr on the container app.                                                                                           |
-| `--dapr-app-port`         | `dapr.appPort`            | The port your application is listening on which will be used by Dapr for communicating to your application                   |
+| `--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-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.                    |
@@ -102,7 +102,7 @@ When using an IaC template, specify the following arguments in the `properties.c
 
 ---
 
-The above Dapr configuration values are considered application-scope changes. When you run a container app in multiple revision mode, changes to these settings won't create a new revision. Instead, all existing revisions will be restarted to ensure they're configured with the most up-to-date values.
+The above Dapr configuration values are considered application-scope changes. When you run a container app in multiple-revision mode, changes to these settings won't create a new revision. Instead, all existing revisions are restarted to ensure they're configured with the most up-to-date values.
 
 ## Dapr components
 
@@ -148,7 +148,7 @@ metadata:
 
 ### Component scopes
 
-By default, all Dapr-enabled container apps within the same environment will load the full set of deployed components. To ensure components are loaded at runtime by only the appropriate container apps, application scopes should be used. In the example below, the component will only be 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 components are loaded at runtime by only the appropriate container apps, application scopes should be used. In the example below, the component is only loaded by the two Dapr-enabled container apps with Dapr application IDs `APP-ID-1` and `APP-ID-2`:
 
 > [!NOTE]
 > Dapr component scopes correspond to the Dapr application ID of a container app, not the container app name.
@@ -213,7 +213,7 @@ scopes:
 ```
 
 > [!NOTE]
-> Kubernetes secrets, Local environment variables and Local file Dapr secret stores are not supported in Container Apps. As an alternative for the upstream Dapr default Kubernetes secret store, container apps provides a platform-managed approach for creating and leveraging Kubernetes secrets.
+> Kubernetes secrets, Local environment variables and Local file Dapr secret stores aren't supported in Container Apps. As an alternative for the upstream Dapr default Kubernetes secret store, container apps provides a platform-managed approach for creating and leveraging Kubernetes secrets.
 
 #### Using Platform-managed Kubernetes secrets
 
@@ -334,6 +334,10 @@ This resource defines a Dapr component called `dapr-pubsub` via ARM.
 
 ---
 
+## Release cadence for Dapr
+
+The latest version of Dapr in Azure Container Apps will be available within six weeks after [the Dapr OSS release][dapr-release].
+
 ## Limitations
 
 ### Unsupported Dapr capabilities
@@ -342,11 +346,11 @@ This resource defines a Dapr component called `dapr-pubsub` via ARM.
 - **Dapr Configuration spec**: Any capabilities that require use of the Dapr configuration spec.
 - **Declarative pub/sub subscriptions**
 - **Any Dapr sidecar annotations not listed above**
-- **Alpha APIs and components**: Azure Container Apps does not guarantee the availability of Dapr alpha APIs and features. If available to use, they are on a self-service, opt-in basis. Alpha APIs and components are provided "as is" and "as available," and are continually evolving as they move toward stable status. Alpha APIs and components are not covered by customer support.
+- **Alpha APIs and components**: Azure Container Apps doesn't guarantee the availability of Dapr alpha APIs and features. If available to use, they are on a self-service, opt-in basis. Alpha APIs and components are provided "as is" and "as available," and are continually evolving as they move toward stable status. Alpha APIs and components aren't covered by customer support.
 
 ### Known limitations
 
-- **Actor reminders**: Require a minReplicas of 1+ to ensure reminders will always be active and fire correctly.
+- **Actor reminders**: Require a minReplicas of 1+ to ensure reminders is always active and fires correctly.
 
 ## Next Steps
 
@@ -374,3 +378,4 @@ Now that you've learned about Dapr and some of the challenges it solves:
 [dapr-args]: https://docs.dapr.io/reference/arguments-annotations-overview/
 [dapr-component]: https://docs.dapr.io/concepts/components-concept/
 [dapr-component-spec]: https://docs.dapr.io/operations/components/component-schema/
+[dapr-release]: https://docs.dapr.io/operations/support/support-release-policy/#supported-versions