KEP-3008: clarify goals

keps/sig-node/3008-cri-class-based-resources/README.md

@@ -230,10 +230,11 @@ List the specific goals of the KEP. What is it trying to achieve? How will we
 know that this has succeeded?
 -->
 
-- Introduce RDT support comparable to the OCI runtime-spec to CRI protocol.
-- Make it possible to specify the RDT class of containers on CRI level.
-- Make it possible to specify the blockio class of containers on CRI level.
-- Make the extensions flexible, enabling easy addition of other class-based
+- Make it possible to request class resources
+  - Support RDT class assignment of containers. This is already supported by
+    the containerd and CRI-O runtime and part of the OCI runtime-spec
+  - Support blockio class assignment of containers.
+- Make the extensions flexible, enabling simple addition of other class-based
   resource types in the future.
 
 ### Non-Goals
@@ -304,13 +305,13 @@ Go in to as much detail as necessary here.
 This might be a good place to talk about core concepts and how they relate.
 -->
 
-This is only the first in getting class-based resources supported in
+This is only the first step in getting class-based resources supported in
 Kubernetes. Important pieces like resource status, resource disovery and
 permission control are [non-goals](#non-goals) not solved here. However, these
-aspects are briefly discussed in [future work](#future-work). However, the risk
-in this sort of piecemeal approach is finding devil in the details, resulting
-in inconsistent and/or crippled and/or cumbersome end result. However, there is
-a lot of experience in extending the API and understanding which sort of
+aspects are briefly discussed in [future work](#future-work). The risk in this
+sort of piecemeal approach is finding devil in the details, resulting in
+inconsistent and/or crippled and/or cumbersome end result. However, there is a
+lot of experience in extending the API and understanding which sort of
 solutions are functional and practical.
 
 ### Risks and Mitigations