Skip to content

Commit 7af524c

Browse files
committed
docs(srv): update
1 parent 5f64f9f commit 7af524c

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

pages/serverless-containers/reference-content/containers-autoscaling.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ categories:
1616

1717
## Benefits of autoscaling
1818

19-
Autoscaling offers several benefits, including improved responsiveness and cost efficiency. By automatically adjusting the number of instances of your resource based on current demand, you ensure that your applications can handle varying loads without manual intervention. This not only enhances user experience by maintaining performance levels but also helps in reducing costs by only using resources when necessary. Additionally, autoscaling helps in optimal resource utilization, minimizing the risk of performance degradation during peak times.
19+
[Autoscaling](/serverless-containers/concepts/#autoscaling) offers several benefits, including improved responsiveness and cost efficiency. By automatically adjusting the number of instances of your resource based on current demand, you ensure that your applications can handle varying loads without manual intervention. This not only enhances user experience by maintaining performance levels but also helps in reducing costs by only using resources when necessary. Additionally, autoscaling helps in optimal resource utilization, minimizing the risk of performance degradation during peak times.
2020

2121
## Minimum and maximum scales
2222

2323
### Minimum scale (min-scale)
2424

25-
The this parameter sets the lowest value your resource is allowed to scale down to:
25+
This parameter sets the lowest value your resource is allowed to scale down to:
2626

2727
- If you set a value of `0`, all instances of your resource will be terminated after 15 minutes of inactivity.
2828

@@ -32,7 +32,7 @@ Customizing the minimum scale for Serverless can help ensure that an instance re
3232

3333
### Maximum scale (max-scale)
3434

35-
This parameter sets the maximum number of instances of your resource. You should adjust it based on your resource's traffic spikes, keeping in mind that you may wish to limit the max scale to manage costs effectively.``
35+
This parameter sets the maximum number of instances of your resource. You should adjust it based on your resource's traffic spikes, keeping in mind that you may wish to limit the max scale to manage costs effectively.
3636

3737
When the maximum scale is reached, new requests are queued for processing. When the queue is full, the resource returns `503` errors for requests received beyond this point.
3838

pages/serverless-functions/reference-content/functions-autoscaling.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ categories:
1616

1717
## Benefits of autoscaling
1818

19-
Autoscaling offers several benefits, including improved responsiveness and cost efficiency. By automatically adjusting the number of instances of your resource based on current demand, you ensure that your applications can handle varying loads without manual intervention. This not only enhances user experience by maintaining performance levels but also helps in reducing costs by only using resources when necessary. Additionally, autoscaling helps in optimal resource utilization, minimizing the risk of performance degradation during peak times.
19+
[Autoscaling](/serverless-functions/concepts/#autoscaling) offers several benefits, including improved responsiveness and cost efficiency. By automatically adjusting the number of instances of your resource based on current demand, you ensure that your applications can handle varying loads without manual intervention. This not only enhances user experience by maintaining performance levels but also helps in reducing costs by only using resources when necessary. Additionally, autoscaling helps in optimal resource utilization, minimizing the risk of performance degradation during peak times.
2020

2121
## Minimum and maximum scales
2222

2323
### Minimum scale (min-scale)
2424

25-
The this parameter sets the lowest value your resource is allowed to scale down to:
25+
This parameter sets the lowest value your resource is allowed to scale down to:
2626

2727
- If you set a value of `0`, all instances of your resource will be terminated after 15 minutes of inactivity.
2828

0 commit comments

Comments
 (0)