Apply suggestions from code review

Co-authored-by: Rowena Jones <[email protected]>

Author: nerda-codes

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

@@ -46,14 +46,14 @@ When the maximum scale is reached, new requests are queued for processing. When
 
 ### Autoscaler behavior
 
-The autoscaler decides to add new instances (scale-up) when the number of concurrent requests defined (default is `80`) is reached.
+The autoscaler decides to add new instances (scale up) when the number of concurrent requests defined (default is `80`) is reached.
 
-The same autoscaler decides to remove instances (scale-down) down to `1` when no more requests are received during 30 seconds.
+The same autoscaler decides to remove instances (scale down) down to `1` when no more requests are received for 30 seconds.
 
 Scaling down to zero (if min-scale is set to `0`) happens after 15 minutes of inactivity.
 
 <Message type="note">
-Redeploying your resource does not generate downtime. Instances are gradually replaced with new ones.
+Redeploying your resource does not entail downtime. Instances are gradually replaced with new ones.
 
 Old instances remain running to handle traffic, while new instances are brought up and verified before fully replacing the old ones. This method helps maintain application availability and service continuity throughout the update process.
 </Message>

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

@@ -38,14 +38,14 @@ When the maximum scale is reached, new requests are queued for processing. When
 
 ### Autoscaler behavior
 
-The autoscaler decides to add new instances (scale-up) for each concurrent request. For example, 5 concurrent requests will generate 5 Serverless Functions instances. This parameter can be customized on Serverless Containers but not on Serverless Functions.
+The autoscaler decides to add new instances (scale up) for each concurrent request. For example, 5 concurrent requests will generate 5 Serverless Functions instances. This parameter can be customized on Serverless Containers but not on Serverless Functions.
 
-The same autoscaler decides to remove instances (scale-down) down to `1` when no more requests are received during 30 seconds.
+The same autoscaler decides to remove instances (scale down) down to `1` when no more requests are received for 30 seconds.
 
 Scaling down to zero (if min-scale is set to `0`) happens after 15 minutes of inactivity.
 
 <Message type="note">
-Redeploying your resource does not generate downtime. Instances are gradually replaced with new ones.
+Redeploying your resource does not entail downtime. Instances are gradually replaced with new ones.
 
 Old instances remain running to handle traffic, while new instances are brought up and verified before fully replacing the old ones. This method helps maintain application availability and service continuity throughout the update process.
 </Message>