clarify that scheduler will use CSINode object for volume limits as w…

…ell as driver availability

keps/sig-storage/20190408-volume-scheduling-limits.md

@@ -111,7 +111,10 @@ object and return early as applicable.
 
 ## Proposal
 
-* Track volume limits for CSI driver in `CSINode` objects instead of `Node`. Limit in `CSINode` is used instead of limit coming from `Node` object whenever available for same in-tree volume type. This mean scheduler will always try to translate in-tree driver name to CSI driver name whenever `CSINode` object has same in-tree volume type (even if migration is off).
+Track volume limits for CSI driver in `CSINode` object instead of `Node` and update scheduler to use `CSINode` object to determining volume limits and availability of CSI driver.
+
+Limit in `CSINode` is used instead of limit coming from `Node` object whenever available for same in-tree volume type. This mean scheduler will always try to translate in-tree driver name to CSI driver name whenever `CSINode` object has same in-tree volume type (even if migration is off).
+
   * To get rid of prefix + SHA for `ResourceName` of CSI volumes.
   * So in-tree volume plugin can share limits with CSI driver that uses the same storage backend.