updates from feedback

content/en/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm.md

@@ -336,10 +336,6 @@ The nodes are where your workloads (containers and Pods, etc) run. To add new no
   kubeadm join --token <token> <control-plane-host>:<control-plane-port> --discovery-token-ca-cert-hash sha256:<hash>
   ```
 
-{{< note >}}
-On Windows you should specify the `--cri-socket` parameter in the `kubeadm join` command. The default path is "npipe:////./pipe/containerd-containerd" for containerd.
-{{< /note >}}
-
 If you do not have the token, you can get it by running the following command on the control-plane node:
 
 ```bash

content/en/docs/tasks/administer-cluster/kubeadm/upgrading-windows-nodes.md

@@ -62,7 +62,7 @@ upgrade the control plane nodes before upgrading your Windows nodes.
     kubeadm upgrade node
     ```
 
-### Upgrade kubelet and kubeproxy
+### Upgrade kubelet and kube-proxy
 
 1.  From the Windows node, upgrade and restart the kubelet:
 
@@ -81,7 +81,7 @@ upgrade the control plane nodes before upgrading your Windows nodes.
     ```
 
 {{< note >}}
-If you are running kube-proxy in a HostProcess Container instead of a Windows Service, you can upgrade kube-proxy by applying a newer version of your kube-proxy manifests.
+If you are running kube-proxy in a HostProcess container within a Pod, and not as a Windows Service, you can upgrade kube-proxy by applying a newer version of your kube-proxy manifests.
 {{< /note >}}
 
 ### Uncordon the node