Update nodes.md (#36522)

* Update nodes.md

In the previous doc, the doc  is "用户可以手动将具有 `NoExecute` 或 `NoSchedule` 效果的
`node kubernetes.io/out-of-service` ", please note that it is `node kubernetes.io/out-of-service`, there is a space between "node" and "kubernetes.io/out-of-service",
after read the related doc, I think that this should be "node.kubernetes.io/out-of-service", this is defined node label in k8s. Please see https://kubernetes.io/docs/reference/labels-annotations-taints/#node-kubernetes-io-out-of-service

* Update nodes.md

Fix line 878 per comment

Author: aim-for-better

content/zh-cn/docs/concepts/architecture/nodes.md

@@ -875,9 +875,8 @@ these pods will be stuck in terminating status on the shutdown node forever.
 如果原来的已关闭节点没有被恢复，那些在已关闭节点上的 Pod 将永远滞留在终止状态。
 
 <!--
-To mitigate the above situation, a  user can manually add the taint `node 
-kubernetes.io/out-of-service` with either `NoExecute` or `NoSchedule` effect to 
-a Node marking it out-of-service. 
+To mitigate the above situation, a  user can manually add the taint `node.kubernetes.io/out-of-service` with either `NoExecute` 
+or `NoSchedule` effect to a Node marking it out-of-service. 
 If the `NodeOutOfServiceVolumeDetach`  [feature gate](/docs/reference/
 command-line-tools-reference/feature-gates/) is enabled on
 `kube-controller-manager`, and a Node is marked out-of-service with this taint, the 
@@ -887,7 +886,7 @@ immediately. This allows the Pods on the out-of-service node to recover quickly
 different node. 
 -->
 为了缓解上述情况，用户可以手动将具有 `NoExecute` 或 `NoSchedule` 效果的
-`node kubernetes.io/out-of-service` 污点添加到节点上，标记其无法提供服务。
+`node.kubernetes.io/out-of-service` 污点添加到节点上，标记其无法提供服务。
 如果在 `kube-controller-manager` 上启用了 `NodeOutOfServiceVolumeDetach`
 [特性门控](/zh-cn/docs/reference/command-line-tools-reference/feature-gates/)，
 并且节点被通过污点标记为无法提供服务，如果节点 Pod 上没有设置对应的容忍度，