@@ -44,7 +44,7 @@ Before v8.3.0, TiDB only supports generating valid execution plans for the `WITH
 
 <CustomContent platform="tidb-cloud">
 
-Before v8.3.0, TiDB only supports generating valid execution plans for the `WITH ROLLUP` syntax in [TiFlash MPP mode](/tiflash/use-tiflash-mpp-mode.md). Therefore, your TiDB cluster needs to contain TiFlash nodes, and the target table must be configured with the correct TiFlash replica. For more information, see [Change node number](/tidb-cloud/scale-tidb-cluster.md#change-node-number).
+Before v8.3.0, TiDB only supports generating valid execution plans for the `WITH ROLLUP` syntax in [TiFlash MPP mode](/tiflash/use-tiflash-mpp-mode.md). Therefore, your TiDB cluster needs to contain TiFlash nodes, and the target table must be configured with the correct TiFlash replica. For more information, see [Change node count](/tidb-cloud/scale-tidb-cluster.md#change-node-count).
 
 </CustomContent>
 
 
@@ -18,7 +18,7 @@ To understand the key metrics displayed on the Overview dashboard, check the fol
 
 | Service | Panel Name | Description | Normal Range |
 | ---- | ---------------- | ---------------------------------- | -------------- |
-| Services Port Status | Services Up | The online nodes number of each service. |
+| Services Port Status | Services Up | The number of online nodes of each service. |
 | PD | PD role | The role of the current PD. |
 | PD | Storage capacity |  The total storage capacity of the TiDB cluster. |
 | PD | Current storage size | The occupied storage capacity of the TiDB cluster, including the space occupied by TiKV replicas. |
 
@@ -309,7 +309,7 @@ To restore your TiDB Cloud Dedicated cluster data from a backup to a new cluster
 
     - Set the cluster name.
     - Update the port number of the cluster.
-    - Increase node number, vCPU and RAM, and storage for the cluster.
+    - Increase the number of nodes, vCPU and RAM, and storage for the cluster.
 
 7. Click **Restore**.
 
@@ -337,7 +337,7 @@ To restore a deleted TiDB Cloud Dedicated cluster from the Recycle Bin, take the
 5. On the **Restore** page, specify a name for the new cluster, and then make the following changes if necessary:
 
     - Update the port number of the cluster.
-    - Increase the node number, vCPU and RAM, and storage for the cluster.
+    - Increase the number of nodes, vCPU and RAM, and storage for the cluster.
 
 6. In the **Summary** section, check the restore information, and then click **Restore**.
 
 
@@ -68,18 +68,18 @@ TiDB Cloud provides different alert rules for each [TiDB Cloud plan](/tidb-cloud
 
 | Condition | Recommended Action |
 |:--- |:--- |
-| Total TiDB node memory utilization across cluster exceeded 70% for 10 minutes | Consider increasing the node number or node size for TiDB to reduce the memory usage percentage of the current workload.|
-| Total TiKV node memory utilization across cluster exceeded 70% for 10 minutes | Consider increasing the node number or node size for TiKV to reduce the memory usage percentage of the current workload. |
-| Total TiFlash node memory utilization across cluster exceeded 70% for 10 minutes | Consider increasing the node number or node size for TiFlash to reduce the memory usage percentage of the current workload. |
-| Total TiDB node CPU utilization exceeded 80% for 10 minutes | Consider increasing the node number or node size for TiDB to reduce the CPU usage percentage of the current workload.|
-| Total TiKV node CPU utilization exceeded 80% for 10 minutes | Consider increasing the node number or node size for TiKV to reduce the CPU usage percentage of the current workload. |
-| Total TiFlash node CPU utilization exceeded 80% for 10 minutes | Consider increasing the node number or node size for TiFlash to reduce the CPU usage percentage of the current workload. |
-| TiKV storage utilization exceeds 80% | Consider increasing the node number or node storage size for TiKV to increase your storage capacity. When the storage usage of TiKV exceeds 80%, latency spikes might occur, and higher usage might cause requests to fail. |
-| TiFlash storage utilization exceeds 80% | Consider increasing the node number or node storage size for TiFlash to increase your storage capacity. When the storage usage of all TiFlash nodes reaches 80%, any DDL statement that adds a TiFlash replica hangs indefinitely. |
-| Max memory utilization across TiDB nodes exceeded 70% for 10 minutes | Consider checking if there is any [hotspot](/tidb-cloud/tidb-cloud-sql-tuning-overview.md#hotspot-issues) in the cluster or increasing the node number or node size for TiDB to reduce the memory usage percentage of the current workload. |
-| Max memory utilization across TiKV nodes exceeded 70% for 10 minutes | Consider checking if there is any [hotspot](/tidb-cloud/tidb-cloud-sql-tuning-overview.md#hotspot-issues) in the cluster or increasing the node number or node size for TiKV to reduce the memory usage percentage of the current workload. |
-| Max CPU utilization across TiDB nodes exceeded 80% for 10 minutes | Consider checking if there is any [hotspot](/tidb-cloud/tidb-cloud-sql-tuning-overview.md#hotspot-issues) in the cluster or increasing the node number or node size for TiDB to reduce the CPU usage percentage of the current workload. |
-| Max CPU utilization across TiKV nodes exceeded 80% for 10 minutes | Consider checking if there is any [hotspot](/tidb-cloud/tidb-cloud-sql-tuning-overview.md#hotspot-issues) in the cluster or increasing the node number or node size for TiKV to reduce the CPU usage percentage of the current workload. |
+| Total TiDB node memory utilization across cluster exceeded 70% for 10 minutes | Consider increasing the node count or node size for TiDB to reduce the memory usage percentage of the current workload.|
+| Total TiKV node memory utilization across cluster exceeded 70% for 10 minutes | Consider increasing the node count or node size for TiKV to reduce the memory usage percentage of the current workload. |
+| Total TiFlash node memory utilization across cluster exceeded 70% for 10 minutes | Consider increasing the node count or node size for TiFlash to reduce the memory usage percentage of the current workload. |
+| Total TiDB node CPU utilization exceeded 80% for 10 minutes | Consider increasing the node count or node size for TiDB to reduce the CPU usage percentage of the current workload.|
+| Total TiKV node CPU utilization exceeded 80% for 10 minutes | Consider increasing the node count or node size for TiKV to reduce the CPU usage percentage of the current workload. |
+| Total TiFlash node CPU utilization exceeded 80% for 10 minutes | Consider increasing the node count or node size for TiFlash to reduce the CPU usage percentage of the current workload. |
+| TiKV storage utilization exceeds 80% | Consider increasing the node count or node storage size for TiKV to increase your storage capacity. When the storage usage of TiKV exceeds 80%, latency spikes might occur, and higher usage might cause requests to fail. |
+| TiFlash storage utilization exceeds 80% | Consider increasing the node count or node storage size for TiFlash to increase your storage capacity. When the storage usage of all TiFlash nodes reaches 80%, any DDL statement that adds a TiFlash replica hangs indefinitely. |
+| Max memory utilization across TiDB nodes exceeded 70% for 10 minutes | Consider checking if there is any [hotspot](/tidb-cloud/tidb-cloud-sql-tuning-overview.md#hotspot-issues) in the cluster or increasing the node count or node size for TiDB to reduce the memory usage percentage of the current workload. |
+| Max memory utilization across TiKV nodes exceeded 70% for 10 minutes | Consider checking if there is any [hotspot](/tidb-cloud/tidb-cloud-sql-tuning-overview.md#hotspot-issues) in the cluster or increasing the node count or node size for TiKV to reduce the memory usage percentage of the current workload. |
+| Max CPU utilization across TiDB nodes exceeded 80% for 10 minutes | Consider checking if there is any [hotspot](/tidb-cloud/tidb-cloud-sql-tuning-overview.md#hotspot-issues) in the cluster or increasing the node count or node size for TiDB to reduce the CPU usage percentage of the current workload. |
+| Max CPU utilization across TiKV nodes exceeded 80% for 10 minutes | Consider checking if there is any [hotspot](/tidb-cloud/tidb-cloud-sql-tuning-overview.md#hotspot-issues) in the cluster or increasing the node count or node size for TiKV to reduce the CPU usage percentage of the current workload. |
 
 ### Data migration alerts
 
 
@@ -19,7 +19,7 @@ This notification describes the details that you need to know about the maintena
 
 ## Impact
 
-During the maintenance window, [change vCPU and RAM](https://docs.pingcap.com/tidbcloud/scale-tidb-cluster#change-vcpu-and-ram) is disabled and you can not change vCPU and RAM for your Dedicated Clusters. However, you can still change the node number or storage in the Modify Cluster page. Your TiDB cluster will maintain its regular operations for data read and write, ensuring no adverse effects on your online business.
+During the maintenance window, [change vCPU and RAM](https://docs.pingcap.com/tidbcloud/scale-tidb-cluster#change-vcpu-and-ram) is disabled and you can not change vCPU and RAM for your Dedicated Clusters. However, you can still change the node count or storage in the Modify Cluster page. Your TiDB cluster will maintain its regular operations for data read and write, ensuring no adverse effects on your online business.
 
 ### Affected features of TiDB Cloud console UI
 
 
@@ -898,7 +898,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c
 
 - Support decreasing the number of TiKV and TiFlash nodes to scale in a TiDB [Dedicated Tier](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) cluster.
 
-    You can decrease the node number [via the TiDB Cloud console](/tidb-cloud/scale-tidb-cluster.md#change-node-number) or [via the TiDB Cloud API (beta)](https://docs.pingcap.com/tidbcloud/api/v1beta#tag/Cluster/operation/UpdateCluster).
+    You can decrease the number of nodes [via the TiDB Cloud console](/tidb-cloud/scale-tidb-cluster.md#change-node-count) or [via the TiDB Cloud API (beta)](https://docs.pingcap.com/tidbcloud/api/v1beta#tag/Cluster/operation/UpdateCluster).
 
 **Console changes**
 
 
@@ -26,18 +26,18 @@ A combination of both vertical and horizontal scaling is also supported in TiDB
 
 ## TiDB scalability
 
-TiDB is for computing only and does not store data. You can configure the node number, vCPU, and RAM for TiDB.
+TiDB is for computing only and does not store data. You can configure the node count, vCPU, and RAM for TiDB.
 
 In general, TiDB performance increases linearly with the number of TiDB nodes.
 
 ## TiKV scalability
 
-TiKV is responsible for storing row-based data. You can configure the node number, vCPU and RAM, and storage for TiKV. The number of TiKV nodes should be at least 1 set (3 nodes in 3 different availability zones) and increase by 3 nodes.
+TiKV is responsible for storing row-based data. You can configure the node count, vCPU and RAM, and storage for TiKV. The number of TiKV nodes should be at least 1 set (3 nodes in 3 different availability zones) and increase by 3 nodes.
 
 TiDB Cloud deploys TiKV nodes evenly to 3 availability zones in the region you select to achieve durability and high availability. In a typical 3-replica setup, your data is distributed evenly among the TiKV nodes across all availability zones and is persisted to the disk of each TiKV node. Although TiKV is mainly used for data storage, the performance of the TiKV node also varies depending on different workloads.
 
 ## TiFlash scalability
 
-TiFlash is responsible for storing columnar data. TiFlash synchronizes data from TiKV in real time and supports real-time analytics workloads right out of the box. You can configure the node number, vCPU and RAM, and storage for TiFlash.
+TiFlash is responsible for storing columnar data. TiFlash synchronizes data from TiKV in real time and supports real-time analytics workloads right out of the box. You can configure the node count, vCPU and RAM, and storage for TiFlash.
 
 TiDB Cloud deploys TiFlash nodes evenly to different availability zones in a region. It is recommended that you configure at least two TiFlash nodes in each TiDB Cloud Dedicated cluster and create at least two replicas of the data for high availability in your production environment.
@@ -12,7 +12,7 @@ summary: Learn how to scale your TiDB Cloud cluster.
 
 You can scale a TiDB cluster in the following dimensions:
 
-- Node number of TiDB, TiKV, and TiFlash
+- Node count of TiDB, TiKV, and TiFlash
 - vCPU and RAM of TiDB, TiKV, and TiFlash
 - Storage of TiKV and TiFlash
 
@@ -22,17 +22,17 @@ For information about how to determine the size of your TiDB cluster, see [Deter
 >
 > If the vCPU and RAM size of TiDB or TiKV is set as **4 vCPU, 16 GiB**, note the following restrictions. To bypass these restrictions, you can [increase the vCPU and RAM](#change-vcpu-and-ram) first.
 >
-> - The node number of TiDB can only be set to 1 or 2, and the node number of TiKV is fixed to 3.
+> - The node count of TiDB can only be set to 1 or 2, and the node count of TiKV is fixed to 3.
 > - 4 vCPU TiDB can only be used with 4 vCPU TiKV, and 4 vCPU TiKV can only be used with 4 vCPU TiDB.
 > - TiFlash is unavailable.
 
-## Change node number
+## Change node count
 
 You can increase or decrease the number of TiDB, TiKV, or TiFlash nodes.
 
 > **Warning:**
 >
-> Decreasing TiKV or TiFlash node number can be risky, which might lead to insufficient storage space, excessive CPU usage, or excessive memory usage on remaining nodes.
+> Decreasing TiKV or TiFlash node count can be risky, which might lead to insufficient storage space, excessive CPU usage, or excessive memory usage on remaining nodes.
 
 To change the number of TiDB, TiKV, or TiFlash nodes, take the following steps:
 
 
@@ -265,7 +265,7 @@ In the results:
 
 - `cloud_provider` is the cloud provider on which a TiDB cluster can be hosted.
 - `region` is the region of `cloud_provider`.
-- `node_quantity_range` shows the minimum node number and the step to scale a node.
+- `node_quantity_range` shows the minimum node count and the step to scale a node.
 - `node_size` is the size of a node.
 - `storage_size_gib_range` shows the minimum and maximum storage size you can set for a node.
 
 
@@ -26,7 +26,7 @@ The following table shows the maximum QPS and network bandwidth of each TiProxy
 | Small | 30K         | 93 MiB/s                  |
 | Large | 120K        | 312 MiB/s                 |
 
-The available TiProxy sizes are `Small` and `Large`. The available TiProxy node numbers are 2, 3, 6, 9, 12, 15, 18, 21, and 24. The default two small-sized TiProxy nodes can provide 60K QPS and 186 MiB/s network bandwidth. It is recommended that you reserve 20% of the QPS capacity to prevent high latency.
+The available TiProxy sizes are `Small` and `Large`. The available TiProxy node counts are 2, 3, 6, 9, 12, 15, 18, 21, and 24. The default two small-sized TiProxy nodes can provide 60K QPS and 186 MiB/s network bandwidth. It is recommended that you reserve 20% of the QPS capacity to prevent high latency.
 
 For example, if your cluster's maximum QPS is 100K and the maximum network bandwidth is 100 MiB/s, the size and number of TiProxy nodes mainly depend on the QPS. In this case, you can select 6 small-sized TiProxy nodes.