review fix

Author: chrischdi

docs/proposals/20250513-propogate-taints.md

@@ -295,8 +295,9 @@ Proper validation on the new field has to:
   * With the exception of `node.kubernetes.io/out-of-service`, this taints are managed by the node controller or the kubelet.
 * block taints with the key prefix `node.cloudprovider.kubernetes.io/`
   * This taints are either managed by the kubelet or by a cloud-controller-manager's node-lifecycle-controller
-* block the taints `node-role.kubernetes.io/control-plane` and `node-role.kubernetes.io/master` (deprecated) for control-plane Machines (identified by existence of the label `cluster.x-k8s.io/control-plane`) and for MachineDeployments and MachineSets.
+* block the taints `node-role.kubernetes.io/control-plane` for worker nodes (identified by existence of the label `cluster.x-k8s.io/control-plane`) and for MachineDeployments and MachineSets.
   * This taints are dedicated to be set on control-plane machines, not for workers.
+* block the taint `node-role.kubernetes.io/master` which is deprecated since 1.24
 
 If in the future we are introducing new taints that users should not be able to set, ratcheting may be used.