Updated node roles in docs

Author: Aaina26

content/en/docs/concepts/architecture/nodes.md

@@ -140,6 +140,8 @@ When you want to create Node objects manually, set the kubelet flag `--register-
 You can modify Node objects regardless of the setting of `--register-node`.
 For example, you can set labels on an existing Node or mark it unschedulable.
 
+You can set optional node role for nodes by adding `node-role.kubernetes.io/<role>=` label to the node where characters of `<role>` are limited by the [syntax](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set) rules of labels.
+
 You can use labels on Nodes in conjunction with node selectors on Pods to control
 scheduling. For example, you can constrain a Pod to only be eligible to run on
 a subset of the available nodes.

content/en/docs/reference/labels-annotations-taints/_index.md

@@ -2739,7 +2739,7 @@ ignores that node while calculating Topology Aware Hints.
 
 Type: Taint
 
-Example: `node-role.kubernetes.io/control-plane:NoSchedule`
+Example: `node-role.kubernetes.io/*:NoSchedule`
 
 Used on: Node
 
@@ -2751,7 +2751,7 @@ be scheduled onto them. You can manually remove this taint with the following
 command on a specific node.
 
 ```shell
-kubectl taint nodes <node-name> node-role.kubernetes.io/control-plane:NoSchedule-
+kubectl taint nodes <node-name> node-role.kubernetes.io/*:NoSchedule-
 ```
 
 ### node-role.kubernetes.io/master (deprecated) {#node-role-kubernetes-io-master-taint}
@@ -2760,7 +2760,7 @@ Type: Taint
 
 Used on: Node
 
-Example: `node-role.kubernetes.io/master:NoSchedule`
+Example: `node-role.kubernetes.io/*:NoSchedule`
 
 Taint that kubeadm previously applied on control plane nodes to allow only critical
 workloads to schedule on them. Replaced by the