add more details to the proposed changes

Author: iamzili

vertical-pod-autoscaler/enhancements/7571-support-pod-level-resources/README.md

@@ -426,7 +426,7 @@ In summary Pods with Pod-level resources should not be validated against Contain
 
 #### Pod LimitRange object
 
-For the admission controller, the most relevant recommendation type is the Target, since the controller calculates requests and limits. For the updater, other pod-level recommendation types (Target, LowerBound, and UpperBound) are used to decide which Pods should be evicted.
+For the admission controller, the most relevant recommendation type is the Target, since the controller calculates requests and limits. For the updater, the other Pod-level recommendation types - LowerBound and UpperBound - are used to determine which Pods should be evicted.
 
 This AEP proposes applying the same logic for Pod-level recommendations as defined in the [capProportionallyToPodLimitRange](https://github.com/kubernetes/autoscaler/blob/722902dce0d3fba2a1eb9904a4d91e448496a7f8/vertical-pod-autoscaler/pkg/utils/vpa/capping.go#L514) method. In other words, the Pod-level Target, UpperBound, and LowerBound should be increased or decreased proportionally to comply with Pod LimitRange constraints.