Correction of what Kubelet did/could do in versions <1.24.

Co-authored-by: Mike Brown <[email protected]>

Author: tomkivlin

content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md

@@ -29,7 +29,7 @@ CNI specification (plugins can be compatible with multiple spec versions).
 A Container Runtime, in the networking context, is a daemon on a node configured to provide CRI Services for kubelet. In particular the Container Runtime must be configured to load the CNI plugins required to implement the Kubernetes network model.
 
 {{< note >}}
-Prior to Kubernetes 1.24, the CNI plugin was managed by the Kubelet using the `cni-bin-dir` and `network-plugin` command line parameters.
+Prior to Kubernetes 1.24, the CNI plugins could also be managed by the Kubelet using the `cni-bin-dir` and `network-plugin` command line parameters.
 These were both removed in Kubernetes 1.24, with management of the CNI no longer in scope of the Kubelet.
 
 See [Troubleshooting CNI plugin-related errors](/docs/tasks/administer-cluster/migrating-from-dockershim/troubleshooting-cni-plugin-related-errors/)