Addressed more comments

Author: mortent

keps/sig-scheduling/4815-dra-partitionable-devices/README.md

@@ -352,8 +352,9 @@ on the device that mirrors the node selector fields on the `ResourceSlice`.
    device can be allocated if the necessary counters (i.e. resources) is not
    available. Each counter is identified by its name and the name of its set.
    Nesting counters inside sets was chosen because it enables referencing a mixin
-   (link to other KEP here) with a list of counters in different counter sets and it
-   makes it possible to align groups of counters with the underlying physical devices.
+   ([KEP-5234](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/5234-dra-resourceslice-mixins))
+   with a list of counters in different counter sets and it makes it possible
+   to align groups of counters with the underlying physical devices.
 
 1. Introduce a new field, `ConsumesCounters` under `Device`. It specifies
    the amount the device will draw for the counters in the referenced `CounterSet`.

keps/sig-scheduling/5234-dra-resourceslice-mixins/README.md

@@ -595,6 +595,12 @@ During version skew where the apiserver supports the feature and the scheduler
 doesn't, the devices that is using the mixins feature will be dropped and
 not visible to the scheduler (ref [Implementation](#implementation)).
 
+The exception here is in 1.34 (the first version where this feature is in alpha).
+If the APIServer is at 1.34 and the scheduler is at 1.33, the APIServer will send
+the new fields, but the scheduler will not know what to do about them. It will end
+up ignoring them, which can lead to incorrect scheduling decisions. Note that this
+scenario only applies to the initial 1.34 release and will not apply for 1.35+.
+
 ## Production Readiness Review Questionnaire
 
 <!--