Address reveiw comments

Co-authored-by: kishen-v <[email protected]>

Author: Karthik-K-N

keps/sig-node/3953-node-resource-hot-plug/README.md

@@ -269,9 +269,9 @@ With increase in cluster resources the following components will be updated:
 3. Update in Node capacity.
 
 4. Scheduler:
-    * Scheduler will automatically schedule any pending pods.
-    * This is done as an expected behavior and does not require any changes in the existing design of the scheduler, as the scheduler `watches` the
-      available capacity of the node and creates pods accordingly.
+    * Scheduler keeps trying to schedule any pending pods.
+    * The scheduler `watches` the updates to available capacity of the node and schedule pods accordingly. 
+   The scheduler is already doing this today, and this KEP does not require any changes in the scheduler implementation.
 
 
 ### Handling hotplug events
@@ -333,6 +333,9 @@ To ensure the Cluster Autoscaler acknowledges resource hotplug, the following ap
 2. Identify Nodes Affected by Hotplug:
    * By flagging a Node as being impacted by hotplug, the Cluster Autoscaler could revert to a less reliable but more conservative "scale from 0 nodes" logic.
 
+Given that this KEP and autoscaler are inter-related, the above approaches were discussed in the community with relevant stakeholders, and have decided approaching this problem through the former route. 
+The same will be targeted around the beta graduation of this KEP
+
 ### Handling HotUnplug Events
 
 Though this KEP focuses only on resource hotplug, It will enable the kubelet to capture the current available capacity of the node (Regardless of whether it was a hotplug or hotunplug of resources.)