Fix stale advice on changing the Container Runtime on a Node (#42739)

* Stale advice on changing the Container Runtime on a Node from Docker Engine to containerd

* Update content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd.md

Co-authored-by: Tim Bannister <[email protected]>

* Update migrate-dockershim-dockerd.md

---------

Co-authored-by: Tim Bannister <[email protected]>

Author: pegasas

content/en/docs/tasks/administer-cluster/migrating-from-dockershim/migrate-dockershim-dockerd.md

@@ -76,6 +76,8 @@ instructions for that tool.
 1.  Open `/var/lib/kubelet/kubeadm-flags.env` on each affected node.
 1.  Modify the `--container-runtime-endpoint` flag to
     `unix:///var/run/cri-dockerd.sock`.
+1.  Modify the `--container-runtime` flag to `remote`
+    (unavailable in Kubernetes v1.27 and later).
 
 The kubeadm tool stores the node's socket as an annotation on the `Node` object
 in the control plane. To modify this socket for each affected node:  
@@ -118,4 +120,4 @@ kubectl uncordon <NODE_NAME>
 ## {{% heading "whatsnext" %}}
 
 *   Read the [dockershim removal FAQ](/dockershim/).
-*   [Learn how to migrate from Docker Engine with dockershim to containerd](/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/).
+*   [Learn how to migrate from Docker Engine with dockershim to containerd](/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/).