solty feedback

keps/sig-cli/3515-kubectl-explain-openapiv3/README.md

@@ -338,7 +338,7 @@ specified by the user's path.
 
 1. User types `kubectl explain pods`
 2. kubectl resolves 'pods' to GVR core v1 pods using cluster discovery information
-3. kubectl attempts to fetches `/openapi/v3` which indexes where to find specs for each GV
+3. kubectl attempts to fetch `/openapi/v3`, which indexes where to find specs for each GV
 4. If failure and fallback to v2 is allowed, falls back to Step #3 of the "Current High-level Approach".
 5. Otherwise, kubectl fetches OpenAPIV3 path for GV: `/openapi/v3/<group>/<version>`
 6. kubectl parses the result as map[string]any
@@ -953,6 +953,8 @@ be very unstable, this sort of feature should be delayed until the internal
 templates have proven the API surface to be used. To do otherwise would risk
 breaking user's templates.
 
+## Future Work
+
 ### Other template outputs
 
 We considered an `md` and `html` template for this KEP, possibly with the following