acrolinx

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

Author: hhunter-ms

articles/container-apps/dapr-keda-scaling.md

@@ -10,7 +10,7 @@ ms.date: 04/17/2023
 
 # Scale Dapr applications with KEDA scalers
 
-[Azure Container Apps automatically scales HTTP traffic to zero.](./scale-app.md) Since Dapr pub/sub and bindings are not HTTP traffic, you can use [KEDA scalers](https://keda.sh/) to scale your application and its [Dapr](https://docs.dapr.io/) sidecar up and down based on the number of inbound events and messages waiting to be processed. 
+[Azure Container Apps automatically scales HTTP traffic to zero.](./scale-app.md) However, to scale non-HTTP traffic (like [Dapr](https://docs.dapr.io/) pub/sub and bindings), you can use [KEDA scalers](https://keda.sh/) to scale your application and its Dapr sidecar up and down, based on the number of pending inbound events and messages. 
 
 This guide demonstrates how to configure the scale rules of a Dapr pub/sub application with a KEDA messaging scaler. For context, refer to the corresponding sample pub/sub applications:
 - [Microservice communication using pub/sub sample application in **C#**](https://github.com/Azure-Samples/pubsub-dapr-csharp-servicebus)
@@ -30,9 +30,9 @@ Let's take a look at how to apply the scaling rules in a Dapr application.
 
 ## Publisher container app
 
-The `checkout` publisher is a headless service that runs indefinitely and never scales out to zero. 
+The `checkout` publisher is a headless service that runs indefinitely and never scales down to zero. 
 
-By default, [the Container Apps runtime assigns an HTTP-based scale rule to applications](./scale-app.md) which drives scaling based on the number of incoming HTTP requests. In the following example, `minReplicas` is set to `1`. This configuration ensures the container app doesn't follow the default behavior of scaling to zero when there is no incoming HTTP traffic. 
+By default, [the Container Apps runtime assigns an HTTP-based scale rule to applications](./scale-app.md), which drives scaling based on the number of incoming HTTP requests. In the following example, `minReplicas` is set to `1`. This configuration ensures the container app doesn't follow the default behavior of scaling to zero with no incoming HTTP traffic. 
 
 ```bicep
 resource checkout 'Microsoft.App/containerApps@2022-03-01' = {
@@ -57,7 +57,7 @@ resource checkout 'Microsoft.App/containerApps@2022-03-01' = {
 
 ## Subscriber container app
 
-The `order-processor` subscriber app below includes a custom scale rule that monitors a resource of type `azure-servicebus`. With this rule, the app (and its sidecar) will scale up and down as needed based on the number of pending messages in the Bus.
+The following `order-processor` subscriber app includes a custom scale rule that monitors a resource of type `azure-servicebus`. With this rule, the app (and its sidecar) scales up and down as needed based on the number of pending messages in the Bus.
 
 ```bicep
 resource orders 'Microsoft.App/containerApps@2022-03-01' = {
@@ -142,7 +142,7 @@ Notice the `messageCount` property on the scaler's configuration:
 
 This property tells the scaler how many messages each instance of the application can process at the same time. In this example, the value is set to `30`, indicating that there should be one instance of the application created for each group of 30 messages waiting in the topic.
 
-For example, if 150 messages are waiting, KEDA scales the app out to five instances. The `maxReplicas` property is set to `10`, meaning even if the number of messages in the topic was very large, the scaler will never create more than `10` instances of this application. This setting ensures you don't scale up too much and accrue too much cost.
+For example, if 150 messages are waiting, KEDA scales the app out to five instances. The `maxReplicas` property is set to `10`, meaning even with a large number of messages in the topic, the scaler never creates more than `10` instances of this application. This setting ensures you don't scale up too much and accrue too much cost.
 
 ## Next steps