diff --git a/cluster-autoscaler/README.md b/cluster-autoscaler/README.md
index 2152c6f4d1..93d847c03f 100644
--- a/cluster-autoscaler/README.md
+++ b/cluster-autoscaler/README.md
@@ -67,6 +67,9 @@ somewhere else.
 * There are no kube-system pods on the node (except these that run on all nodes by default like 
 manifest-run pods or pods created by daemonsets).
 
+* There are no pods with local storage. Applications with local storage would lose their 
+data if a node is deleted, even if they are replicated.
+
 If a node is not needed for more than 10 min (configurable) then it can be deleted. Cluster Autoscaler
 deletes one node at a time to reduce the risk of creating new unschedulable pods. The next node 
 can be deleted when it is also not needed for more than 10 min. It may happen just after
@@ -83,7 +86,7 @@ But if another node C, in case of deletion, can move its pods to node Y then it
 may still do it, because noone touched Y. So C can be deleted immediatelly after A. And B not. 
 
 Cluster Autoscaler does all of this acounting based on the simulations and memorized new pod location.
-They may not always be precise (pods can land elswehere) but it seemed to be a good heuristic so far.
+They may not always be precise (pods can land elswehere) but it seems to be a good heuristic so far.
 
 
 # When scaling is executed