Merge pull request #4458 from bibryam/v1.14

Reworded concurrency control doc

daprdocs/content/en/operations/configuration/control-concurrency.md

@@ -8,14 +8,14 @@ description: "Learn how to control how many requests and events can invoke your
 
 Typically, in distributed computing, you may only want to allow for a given number of requests to execute concurrently. Using Dapr's `app-max-concurrency`, you can control how many requests and events can invoke your application simultaneously.
 
-Default `app-max-concurreny` is set to `-1`, meaning no concurrency.
+Default `app-max-concurreny` is set to `-1`, meaning no concurrency limit is enforced.
 
 ## Different approaches
 
 While this guide focuses on `app-max-concurrency`, you can also limit request rate per second using the **`middleware.http.ratelimit`** middleware. However, it's important to understand the difference between the two approaches:
 
 - `middleware.http.ratelimit`: Time bound and limits the number of requests per second
-- `app-max-concurrency`: Specifies the number of concurrent requests (and events) at any point of time. 
+- `app-max-concurrency`: Specifies the max number of concurrent requests (and events) at any point of time. 
 
 See [Rate limit middleware]({{< ref middleware-rate-limit.md >}}) for more information about that approach.
 
@@ -46,7 +46,7 @@ To set concurrency limits with the Dapr CLI for running on your local dev machin
 dapr run --app-max-concurrency 1 --app-port 5000 python ./app.py
 ```
 
-The above example effectively turns your app into a single concurrent service.
+The above example effectively turns your app into a sequential processing service.
 
 {{% /codetab %}}