Skip to content

Commit 750f1cb

Browse files
Update scale-app.md
1 parent 618a076 commit 750f1cb

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/container-apps/scale-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ Scaling is driven by three different categories of triggers:
5555

5656
With an HTTP scaling rule, you have control over the threshold of concurrent HTTP requests that determines how your container app revision scales.
5757

58-
In the following example, the revision scales out up to five replicas and can scale in to zero. The scaling threshold is set to 100 concurrent requests.
58+
In the following example, the revision scales out up to five replicas and can scale in to zero. The scaling property is set to 100 concurrent requests per second.
5959

6060
### Example
6161

@@ -435,7 +435,7 @@ If you don't create a scale rule, the default scale rule is applied to your cont
435435
| HTTP | 0 | 10 |
436436

437437
> [!IMPORTANT]
438-
> Make sure you create a scale rule or set `minReplicas` to 1 or more if you don't enable ingress. If ingress is disabled and all you have is the default limits and rule, then your container app will scale to zero and have no way of starting back up.
438+
> Make sure you create a scale rule or set `minReplicas` to 1 or more if you don't enable ingress. If ingress is disabled and you don't define a `minReplicas` or a custom scale rule, then your container app will scale to zero and have no way of starting back up.
439439
440440
## Considerations
441441

0 commit comments

Comments
 (0)