@@ -362,7 +362,7 @@ type DeviceMixin struct {
362
362
// must be listed without the driver name as domain prefix in
363
363
// their name. All others must be listed with their domain prefix.
364
364
//
365
- // The maximum number of attributes and capacities across all devices
365
+ // The maximum number of attributes and capacities across all devices
366
366
// and device mixins in a ResourceSlice is 4096. When flattened, the
367
367
// total number of attributes and capacities for each device can not
368
368
// exceed 32.
@@ -377,7 +377,7 @@ type DeviceMixin struct {
377
377
// must be listed without the driver name as domain prefix in
378
378
// their name. All others must be listed with their domain prefix.
379
379
//
380
- // The maximum number of attributes and capacities across all devices
380
+ // The maximum number of attributes and capacities across all devices
381
381
// and device mixins in a ResourceSlice is 4096. When flattened, the
382
382
// total number of attributes and capacities for each device can not
383
383
// exceed 32.
@@ -417,7 +417,7 @@ type CounterSetMixin struct {
417
417
// Counters defines the set of counters for this mixin.
418
418
// The name of each counter must be unique in that set and must be a DNS label.
419
419
//
420
- // The maximum number of counters across all counter sets and counter set
420
+ // The maximum number of counters across all counter sets and counter set
421
421
// mixins in a ResourceSlice is 256.
422
422
//
423
423
// +required
662
662
663
663
###### Can the feature be disabled once it has been enabled (i.e. can we roll back the enablement)?
664
664
665
- Yes. Applications that we already running will continue to run and the allocated
665
+ Yes. Applications that were already running will continue to run and the allocated
666
666
devices will remain so.
667
667
668
668
###### What happens if we reenable the feature if it was previously rolled back?
0 commit comments