Fix network-topology guide range rendering and wording across EN/ZH current + versioned docs

docs/UserGuide/user_guide_how_to_use_network_topology_aware_scheduling.md

@@ -265,7 +265,7 @@ Based on the following network topology, this chapter will demonstrate how workl
    network-topology-job-t0-6   1/1     Running   0          5s    192.168.0.16   node6
    network-topology-job-t0-7   1/1     Running   0          5s    192.168.0.17   node7
    ```
-   In this example, the entire Job is scheduled to HyperNode2 (Node0~Node7). The first partition (Pod0~Pod3) is scheduled to HyperNode0 (Node0~Node3), the second partitions (Pod4~Pod7) is scheduled to HyperNode1 (Node4~Node7), and each partition satisfies its own network topology constraints.
+   In this example, the entire Job is scheduled within HyperNode2 (nodes Node0–Node7). The first partition, Pods Pod0–Pod3, is scheduled within HyperNode0 (nodes Node0–Node3). The second partition, Pods Pod4–Pod7, is scheduled within HyperNode1 (nodes Node4–Node7). Each partition satisfies its own network topology constraints.
 
 #### 3.3.3 Deploying Using Volcano Job Without Network Topology Constraints
 

i18n/zh-Hans/docusaurus-plugin-content-docs/current/UserGuide/user_guide_how_to_use_network_topology_aware_scheduling.md

@@ -264,7 +264,7 @@ data:
    network-topology-job-t0-6   1/1     Running   0          5s    192.168.0.16   node6
    network-topology-job-t0-7   1/1     Running   0          5s    192.168.0.17   node7
    ```
-   本例中，整个 Job 被调度到 HyperNode2（Node0~Node7）。第一个分区（Pod0~Pod3）调度到 HyperNode0（Node0~Node3），第二个分区（Pod4~Pod7）调度到 HyperNode1（Node4~Node7），各分区均满足各自的网络拓扑约束。
+   在此示例中，整个 Job 被调度到 HyperNode2（节点 Node0–Node7）内。第一个分区（Pod0–Pod3）被调度到 HyperNode0（节点 Node0–Node3）内；第二个分区（Pod4–Pod7）被调度到 HyperNode1（节点 Node4–Node7）内。每个分区都满足其各自的网络拓扑约束。
 
 #### 3.3.3 部署未配置网络拓扑约束的 Volcano Job
 

i18n/zh-Hans/docusaurus-plugin-content-docs/version-v1.13.0/UserGuide/user_guide_how_to_use_network_topology_aware_scheduling.md

@@ -264,7 +264,7 @@ data:
    network-topology-job-t0-6   1/1     Running   0          5s    192.168.0.16   node6
    network-topology-job-t0-7   1/1     Running   0          5s    192.168.0.17   node7
    ```
-   本例中，整个 Job 被调度到 HyperNode2（Node0~Node7）。第一个分区（Pod0~Pod3）调度到 HyperNode0（Node0~Node3），第二个分区（Pod4~Pod7）调度到 HyperNode1（Node4~Node7），各分区均满足各自的网络拓扑约束。
+   在此示例中，整个 Job 被调度到 HyperNode2（节点 Node0–Node7）内。第一个分区（Pod0–Pod3）被调度到 HyperNode0（节点 Node0–Node3）内；第二个分区（Pod4–Pod7）被调度到 HyperNode1（节点 Node4–Node7）内。每个分区都满足其各自的网络拓扑约束。
 
 #### 3.3.3 部署未配置网络拓扑约束的 Volcano Job
 

i18n/zh-Hans/docusaurus-plugin-content-docs/version-v1.14.0/UserGuide/user_guide_how_to_use_network_topology_aware_scheduling.md

@@ -264,7 +264,7 @@ data:
    network-topology-job-t0-6   1/1     Running   0          5s    192.168.0.16   node6
    network-topology-job-t0-7   1/1     Running   0          5s    192.168.0.17   node7
    ```
-   本例中，整个 Job 被调度到 HyperNode2（Node0~Node7）。第一个分区（Pod0~Pod3）调度到 HyperNode0（Node0~Node3），第二个分区（Pod4~Pod7）调度到 HyperNode1（Node4~Node7），各分区均满足各自的网络拓扑约束。
+   在此示例中，整个 Job 被调度到 HyperNode2（节点 Node0–Node7）内。第一个分区（Pod0–Pod3）被调度到 HyperNode0（节点 Node0–Node3）内；第二个分区（Pod4–Pod7）被调度到 HyperNode1（节点 Node4–Node7）内。每个分区都满足其各自的网络拓扑约束。
 
 #### 3.3.3 部署未配置网络拓扑约束的 Volcano Job
 

i18n/zh-Hans/docusaurus-plugin-content-docs/version-v1.15.0/UserGuide/user_guide_how_to_use_network_topology_aware_scheduling.md

@@ -264,7 +264,7 @@ data:
    network-topology-job-t0-6   1/1     Running   0          5s    192.168.0.16   node6
    network-topology-job-t0-7   1/1     Running   0          5s    192.168.0.17   node7
    ```
-   本例中，整个 Job 被调度到 HyperNode2（Node0~Node7）。第一个分区（Pod0~Pod3）调度到 HyperNode0（Node0~Node3），第二个分区（Pod4~Pod7）调度到 HyperNode1（Node4~Node7），各分区均满足各自的网络拓扑约束。
+   在此示例中，整个 Job 被调度到 HyperNode2（节点 Node0–Node7）内。第一个分区（Pod0–Pod3）被调度到 HyperNode0（节点 Node0–Node3）内；第二个分区（Pod4–Pod7）被调度到 HyperNode1（节点 Node4–Node7）内。每个分区都满足其各自的网络拓扑约束。
 
 #### 3.3.3 部署未配置网络拓扑约束的 Volcano Job
 

versioned_docs/version-v1.13.0/UserGuide/user_guide_how_to_use_network_topology_aware_scheduling.md

@@ -265,7 +265,7 @@ Based on the following network topology, this chapter will demonstrate how workl
    network-topology-job-t0-6   1/1     Running   0          5s    192.168.0.16   node6
    network-topology-job-t0-7   1/1     Running   0          5s    192.168.0.17   node7
    ```
-   In this example, the entire Job is scheduled to HyperNode2 (Node0~Node7). The first partition (Pod0~Pod3) is scheduled to HyperNode0 (Node0~Node3), the second partitions (Pod4~Pod7) is scheduled to HyperNode1 (Node4~Node7), and each partition satisfies its own network topology constraints.
+   In this example, the entire Job is scheduled within HyperNode2 (nodes Node0–Node7). The first partition, Pods Pod0–Pod3, is scheduled within HyperNode0 (nodes Node0–Node3). The second partition, Pods Pod4–Pod7, is scheduled within HyperNode1 (nodes Node4–Node7). Each partition satisfies its own network topology constraints.
 
 #### 3.3.3 Deploying Using Volcano Job Without Network Topology Constraints
 

versioned_docs/version-v1.14.0/UserGuide/user_guide_how_to_use_network_topology_aware_scheduling.md

@@ -265,7 +265,7 @@ Based on the following network topology, this chapter will demonstrate how workl
    network-topology-job-t0-6   1/1     Running   0          5s    192.168.0.16   node6
    network-topology-job-t0-7   1/1     Running   0          5s    192.168.0.17   node7
    ```
-   In this example, the entire Job is scheduled to HyperNode2 (Node0~Node7). The first partition (Pod0~Pod3) is scheduled to HyperNode0 (Node0~Node3), the second partitions (Pod4~Pod7) is scheduled to HyperNode1 (Node4~Node7), and each partition satisfies its own network topology constraints.
+   In this example, the entire Job is scheduled within HyperNode2 (nodes Node0–Node7). The first partition, Pods Pod0–Pod3, is scheduled within HyperNode0 (nodes Node0–Node3). The second partition, Pods Pod4–Pod7, is scheduled within HyperNode1 (nodes Node4–Node7). Each partition satisfies its own network topology constraints.
 
 #### 3.3.3 Deploying Using Volcano Job Without Network Topology Constraints
 

versioned_docs/version-v1.15.0/UserGuide/user_guide_how_to_use_network_topology_aware_scheduling.md

@@ -265,7 +265,7 @@ Based on the following network topology, this chapter will demonstrate how workl
    network-topology-job-t0-6   1/1     Running   0          5s    192.168.0.16   node6
    network-topology-job-t0-7   1/1     Running   0          5s    192.168.0.17   node7
    ```
-   In this example, the entire Job is scheduled to HyperNode2 (Node0~Node7). The first partition (Pod0~Pod3) is scheduled to HyperNode0 (Node0~Node3), the second partitions (Pod4~Pod7) is scheduled to HyperNode1 (Node4~Node7), and each partition satisfies its own network topology constraints.
+   In this example, the entire Job is scheduled within HyperNode2 (nodes Node0–Node7). The first partition, Pods Pod0–Pod3, is scheduled within HyperNode0 (nodes Node0–Node3). The second partition, Pods Pod4–Pod7, is scheduled within HyperNode1 (nodes Node4–Node7). Each partition satisfies its own network topology constraints.
 
 #### 3.3.3 Deploying Using Volcano Job Without Network Topology Constraints