apply comments

Author: ikidnapmyself

docs/hypernode-platform/autoscaling/how-does-autoscaling-work.md

@@ -9,17 +9,21 @@ myst:
 
 ## Purpose
 
-Autoscaling ensures dynamic server resource adjustments based on CPU usage metrics, efficiently managing workload demands without manual intervention.
+Autoscaling ensures dynamic server resource adjustments based on CPU usage metrics, efficiently managing workload demands without manual intervention. Once triggered, boosted state lasts for a 24-hour period.
+
+## Supported providers:
+
+Autoscaling is available for Combell Openstack and AWS cloud hosting providers.
 
 ## Configuration Parameters
 
-In the control panel, users can define autoscaling conditions to tailor actions to their workload demands:
+In the control panel or with CLI tool, users can define autoscaling conditions based on CPU load thresholds and minimum duration to tailor actions to their workload demands:
 - **CPU Load Threshold:** Specifies the CPU load percentage that triggers autoscaling using a range slider.
 - **Minimum Duration:** Determines the minimum duration, in minutes, for the CPU load to exceed the threshold to activate autoscaling.
 
 ## Autoscaling Triggering Process
 - **Continuous Monitoring:** The autoscaling agent continually monitors your application's CPU load.
-- **Activation Conditions:** Autoscaling is triggered if the CPU load surpasses the defined threshold and duration criteria set by the user.
+- **Activation Conditions:** Autoscaling is triggered if the CPU load surpasses the defined threshold and duration criteria set by the user or default values that were set when the feature was enabled.
 
 ## Autoscaling Workflow
 - **Initial Cooldown period:** A 5-minute cooldown period after enabling autoscaling prevents rapid scaling due to sudden spikes.
@@ -33,12 +37,15 @@ If the server remains overloaded post-autoscaling, the next autoscaling trigger
   - **A fallback duration of 15 minutes**: Ensures a minimum interval for reassessment when the user-defined duration is less than 15 minutes.
 
 This approach selects the longer duration between user-defined settings or the fallback duration before initiating the next autoscaling event. It ensures adequate time for evaluating resource changes on CPU performance.
+
 To halt continued autoscaling behavior, simply turn off the autoscaling feature in your control panel. This prevents subsequent autoscaling triggers after the initial action.
 
+**Important to know:**
+- For the next 24 hours, plan adjustments are restricted. If necessary, please contact support for assistance.
+- If there are still insufficient resources and the conditions are met, the system will initiate another autoscaling process with a cooldown period of 5 minutes.
+- It will scale up to the largest plan available within the same provider.
+- Downscaling takes place within 24 hours from the initial autoscaling event.
+
 ## Enabling Autoscaling
 
 For detailed steps on enabling Autoscaling, please refer to our documentation: [How to enable Autoscaling?](how-to-enable-autoscaling.md)
-
-## Supported providers:
-
-Autoscaling is available for Combell Openstack and AWS cloud hosting providers.