[zh] sync scheduling-eviction node-pressure-eviction file

content/zh/docs/concepts/scheduling-eviction/node-pressure-eviction.md

@@ -365,7 +365,7 @@ kubelet 在驱逐最终用户 Pod 之前会先尝试回收节点级资源。
 If the node has a dedicated `imagefs` filesystem for container runtimes to use,
 the kubelet does the following:
 
-  * If the `nodefs` filesystem meets the eviction threshlds, the kubelet garbage collects
+  * If the `nodefs` filesystem meets the eviction thresholds, the kubelet garbage collects
     dead pods and containers. 
   * If the `imagefs` filesystem meets the eviction thresholds, the kubelet
     deletes all unused images.
@@ -403,7 +403,7 @@ signal below the threshold, the kubelet begins to evict end-user pods.
 The kubelet uses the following parameters to determine pod eviction order:
 
 1. Whether the pod's resource usage exceeds requests
-1. [Pod Priority](/docs/concepts/configuration/pod-priority-preemption/)
+1. [Pod Priority](/docs/concepts/scheduling-eviction/pod-priority-preemption/)
 1. The pod's resource usage relative to requests
 -->
 ### kubelet 驱逐时 Pod 的选择
@@ -414,7 +414,7 @@ The kubelet uses the following parameters to determine pod eviction order:
 kubelet 使用以下参数来确定 Pod 驱逐顺序：
 
 1. Pod 的资源使用是否超过其请求
-1. [Pod 优先级](/zh/docs/concepts/configuration/pod-priority-preemption/)
+1. [Pod 优先级](/zh/docs/concepts/scheduling-eviction/pod-priority-preemption/)
 1. Pod 相对于请求的资源使用情况
 
 <!--