Propagate changes to elastic-cloud-server-api-ref from PreProd environment

[otcbot]

This is an automatically created Pull Request for changes to elastic-cloud-server-api-ref to promote changes down the pipeline to Production environment.

The original change can be found under https://gitea.eco.tsi-dev.otc-service.com/docs/elastic-cloud-server/pulls/328.

There were patch conflicts, please review original patch file.

[otcbot]

I tried my best, but could not apply the patch as is, therefore I will report you what I could not apply.

BTW, if in the diff you see removed line equal to the added line it may be caused by invisible trailing spaces. This is safe to ignore.

In most cases content of the patch remainder need to be carefully analyzed and necessary changes applied manually.

Following is the patch remainder:

diff a/umn/source/change_history.rst b/umn/source/change_history.rst	(rejected hunks)
@@ -8,6 +8,10 @@ Change History
 +-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 | Released On                       | Description                                                                                                                                                                                                                                                                                                                                                                             |
 +===================================+=========================================================================================================================================================================================================================================================================================================================================================================================+
+| 2025-11-30                        | Modified the following content:                                                                                                                                                                                                                                                                                                                                                         |
+|                                   |                                                                                                                                                                                                                                                                                                                                                                                         |
+|                                   | Added P5e ECSs in :ref:`GPU-accelerated ECSs <en-us_topic_0097289624>`.                                                                                                                                                                                                                                                                                                                 |
++-----------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
 | 2025-09-10                        | Added the following content:                                                                                                                                                                                                                                                                                                                                                            |
 |                                   |                                                                                                                                                                                                                                                                                                                                                                                         |
 |                                   | :ref:`Configuring TPM for an ECS <en-us_topic_0000002424701056>`                                                                                                                                                                                                                                                                                                                        |
diff a/umn/source/faqs/file_upload_data_transfer/how_can_i_use_winscp_to_transfer_files_from_a_local_windows_computer_to_a_linux_ecs.rst b/umn/source/faqs/file_upload_data_transfer/how_can_i_use_winscp_to_transfer_files_from_a_local_windows_computer_to_a_linux_ecs.rst	(rejected hunks)
@@ -18,7 +18,7 @@ Prerequisites
 -  The target ECS is running.
 -  An EIP has been bound to the ECS. For details, see :ref:`Binding an EIP <en-us_topic_0174917535>`.
 
--  Access to port 22 is allowed in the inbound direction of the security group which the ECS belongs to. For details, see :ref:`Configuring Security Group Rules <en-us_topic_0030878383>`.
+-  Access to port 22 is allowed in the inbound direction of the security group that the ECS belongs to. For details, see :ref:`Configuring Security Group Rules <en-us_topic_0030878383>`.
 
 Solution
 --------
diff a/umn/source/faqs/file_upload_data_transfer/how_can_i_transfer_files_from_a_local_windows_computer_to_a_windows_ecs.rst b/umn/source/faqs/file_upload_data_transfer/how_can_i_transfer_files_from_a_local_windows_computer_to_a_windows_ecs.rst	(rejected hunks)
@@ -16,7 +16,7 @@ Prerequisites
 -  The target ECS is running.
 -  An EIP has been bound to the ECS. For details, see :ref:`Binding an EIP <en-us_topic_0174917535>`.
 
--  Access to port 3389 is allowed in the inbound direction of the security group which the ECS belongs to. For details, see :ref:`Configuring Security Group Rules <en-us_topic_0030878383>`.
+-  Access to port 3389 is allowed in the inbound direction of the security group that the ECS belongs to. For details, see :ref:`Configuring Security Group Rules <en-us_topic_0030878383>`.
 
 Solution
 --------
diff a/umn/source/security/methods_for_improving_ecs_security.rst b/umn/source/security/methods_for_improving_ecs_security.rst	(rejected hunks)
@@ -103,7 +103,7 @@ Set CBR when purchasing an ECS. The system will associate the ECS with a cloud b
 -  Create new
 
    #. Enter the name of the cloud backup vault. The name consists of 1 to 64 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. For example, **vault-f61e**. The default naming rule is **vault\_**\ *xxxx*.
-   #. Enter the vault capacity, which is required for backing up the ECS. The vault capacity cannot be smaller than that of the ECS to be backed up. The value range is from the total capacity of the ECS to 10,485,760 in the unit of GiB.
+   #. Enter the vault capacity, which is required for backing up the ECS. The vault capacity cannot be smaller than that of the ECS to be backed up. The value range is from the ECS's total capacity to 10,485,760, in GiB.
    #. Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one.
 
 -  Use existing
diff a/umn/source/security/security_groups/changing_a_security_group.rst b/umn/source/security/security_groups/changing_a_security_group.rst	(rejected hunks)
@@ -19,7 +19,7 @@ Constraints
 Procedure
 ---------
 
-#. Log in to the console and access the ECS list page.
+#. Log in to the management console and access the ECS list page.
 
 #. Click |image1| in the upper left corner and select a region and project.
 
diff a/umn/source/eips/overview.rst b/umn/source/eips/overview.rst	(rejected hunks)
@@ -10,7 +10,7 @@ EIP
 
 The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways, or load balancers.
 
-Each EIP can be used by only one cloud resource at a time. An EIP must be in the same region as the resource it is bound to. Cross-region EIP bounding is not supported.
+Each EIP can be used by only one cloud resource at a time. EIPs must be in the same region as the bound resources. EIPs cannot be used across regions.
 
 
 .. figure:: /_static/images/en-us_image_0178890066.png
diff a/umn/source/eips/enabling_internet_connectivity_for_an_ecs_without_an_eip_bound.rst b/umn/source/eips/enabling_internet_connectivity_for_an_ecs_without_an_eip_bound.rst	(rejected hunks)
@@ -38,7 +38,7 @@ The following uses CentOS 7.9 as an example. The operations apply to CentOS 7.9
 
 #. Under **Computing**, click **Elastic Cloud Server**.
 
-#. In the search box above the upper right corner of the ECS list, enter the proxy ECS name for search.
+#. In the search box above the ECS list, enter the proxy ECS name for search.
 
 #. Click the name of the proxy ECS. The ECS details page is displayed.
 
diff a/umn/source/service_overview/network.rst b/umn/source/service_overview/network.rst	(rejected hunks)
@@ -53,7 +53,7 @@ EIP
 
 The Elastic IP (EIP) service enables your cloud resources to communicate with the Internet using static public IP addresses and scalable bandwidths. EIPs can be bound to or unbound from ECSs, BMSs, virtual IP addresses, NAT gateways, or load balancers.
 
-Each EIP can be used by only one cloud resource at a time. An EIP must be in the same region as the resource it is bound to. Cross-region EIP bounding is not supported.
+Each EIP can be used by only one cloud resource at a time. EIPs must be in the same region as the bound resources. EIPs cannot be used across regions.
 
 
 .. figure:: /_static/images/en-us_image_0178890066.png
diff a/umn/source/service_overview/ecs_types_and_specifications/ecs_specifications/ultra-high_i_o_ecss.rst b/umn/source/service_overview/ecs_types_and_specifications/ecs_specifications/ultra-high_i_o_ecss.rst	(rejected hunks)
@@ -280,7 +280,7 @@ Notes
    -  Both EVS disks and local disks can be used as data disks of an ultra-high I/O ECS.
    -  An ultra-high I/O ECS can have a maximum of 60 attached disks (including VBD, SCSI, and local disks). For details about constraints, see :ref:`Can I Attach Multiple Disks to an ECS? <en-us_topic_0018073215>`
 
--  Modify the **fstab** file to set automatic disk mounting at ECS start. For details, see :ref:`Configuring Automatic Mounting at System Start <en-us_topic_0085634798__en-us_topic_0000001809029272_en-us_topic_0000001808490156_section15839912195453>`.
+-  Modify the **fstab** file to set automatic disk mounting at ECS start. For details, see :ref:`Initializing EVS Data Disks <en-us_topic_0030831989>`.
 
 -  The local disk data of an ultra-high I/O ECS may be lost if an exception occurs, such as physical server breakdown or local disk damage. If your application did not use the data reliability architecture, it is a good practice to use EVS disks to build your ECS.
 
diff a/umn/source/service_overview/ecs_types_and_specifications/ecs_specifications/gpu-accelerated_ecss.rst b/umn/source/service_overview/ecs_types_and_specifications/ecs_specifications/gpu-accelerated_ecss.rst	(rejected hunks)
@@ -353,19 +409,19 @@ P5s ECSs use high-performance NVIDIA Tesla H100 PCIe to provide outstanding real
 
 **Specifications**
 
-.. table:: **Table 5** P5s ECS specifications
+.. table:: **Table 6** P5s ECS specifications
 
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
-   | Flavor          | vCPUs | Memory (GiB) | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS (10,000) | Max. NIC Queues | Max. NICs | GPUs           | GPU Memory (GiB) | Virtualization |
-   +=================+=======+==============+=========================================+===========================+=================+===========+================+==================+================+
-   | p5s.5xlarge.12  | 20    | 240          | 16/4.5                                  | 280                       | 8               | 4         | 1 \* H100 PCIe | 80               | KVM            |
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
-   | p5s.10xlarge.12 | 40    | 480          | 24/9                                    | 550                       | 16              | 8         | 2 \* H100 PCIe | 160              | KVM            |
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
-   | p5s.20xlarge.12 | 80    | 960          | 32/18                                   | 750                       | 32              | 8         | 4 \* H100 PCIe | 320              | KVM            |
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
-   | p5s.40xlarge.12 | 160   | 1920         | 40/36                                   | 850                       | 32              | 8         | 8 \* H100 PCIe | 640              | KVM            |
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
+   | Flavor          | vCPUs | Memory (GiB) | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS (10,000) | Max. NIC Queues | Max. NICs | GPUs          | GPU Memory (GiB) | Virtualization |
+   +=================+=======+==============+=========================================+===========================+=================+===========+===============+==================+================+
+   | p5s.5xlarge.12  | 20    | 240          | 16/4.5                                  | 280                       | 8               | 4         | 1 x H100 PCIe | 80               | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
+   | p5s.10xlarge.12 | 40    | 480          | 24/9                                    | 550                       | 16              | 8         | 2 x H100 PCIe | 160              | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
+   | p5s.20xlarge.12 | 80    | 960          | 32/18                                   | 750                       | 32              | 8         | 4 x H100 PCIe | 320              | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
+   | p5s.40xlarge.12 | 160   | 1,920        | 40/36                                   | 850                       | 32              | 8         | 8 x H100 PCIe | 640              | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
 
 **P5s ECS Features**
 
@@ -374,9 +430,9 @@ P5s ECSs use high-performance NVIDIA Tesla H100 PCIe to provide outstanding real
 -  Each GPU provides 80 GiB of GPU memory and 3,026 TFLOPS INT8 compute.
 -  The GPU memory bandwidth can reach up to 2,000 GB/s.
 
-**Supported Common Software**
+**Supported Software**
 
-P5s ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P5s ECSs. The following commonly used software is supported:
+P5s ECSs are used in computing acceleration scenarios, such as deep learning training, inference, scientific computing, molecular modeling, and seismic analysis. If the software is required to support GPU CUDA, use P5s ECSs. P5s ECSs support the following commonly used software:
 
 -  Common deep learning frameworks, such as TensorFlow, Spark, PyTorch, MXNet, and Caffe
 -  CUDA GPU rendering supported by RedShift for Autodesk 3ds Max and V-Ray for 3ds Max
@@ -402,7 +458,7 @@ P3 ECSs use NVIDIA A100 GPUs and provide flexibility and ultra-high-performance
 
 **Specifications**
 
-.. table:: **Table 6** P3 ECS specifications
+.. table:: **Table 7** P3 ECS specifications
 
    +---------------+-------+--------+-----------------------------------------+------------------+-----------------+-----------+-----------------------+------------+----------------+
    | Flavor        | vCPUs | Memory | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS | Max. NIC Queues | Max. NICs | GPUs                  | GPU Memory | Virtualization |
@@ -464,10 +520,10 @@ P3 ECSs are used in computing acceleration scenarios, such as deep learning trai
 
    .. note::
 
-      Resources will be released after a P3 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop it.
+      Resources will be released after a P3 ECS is stopped. If resources are insufficient at the next start, the start may fail. If you want to use such an ECS for a long period of time, do not stop the ECS.
 
 -  If a P3 ECS is created using a private image, make sure that the Tesla driver was installed during the private image creation. If not, install the driver for computing acceleration after the ECS is created. For details, see :ref:`Manually Installing a Tesla Driver on a GPU-accelerated ECS <en-us_topic_0149470468>`.
--  GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous computing power. Their specifications can only be changed to other specifications of the same instance type.
+-  GPU-accelerated ECSs differ greatly in general-purpose and heterogeneous compute. Their specifications can only be changed to other specifications of the same instance type.
 -  GPU-accelerated ECSs do not support live migration.
 
 .. _en-us_topic_0097289624__section1454714546567:
@@ -481,7 +537,7 @@ P2s ECSs use NVIDIA Tesla V100 GPUs to provide flexibility, high-performance com
 
 **Specifications**
 
-.. table:: **Table 7** P2s ECS specifications
+.. table:: **Table 8** P2s ECS specifications
 
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------------+----------------+----------------------------------------------------------+
    | Flavor         | vCPUs | Memory | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS (10,000) | Max. NIC Queues | Max. NICs | GPUs     | GPU Connection | GPU Memory (GiB) | Virtualization | Hardware                                                 |
@@ -560,14 +616,14 @@ P2v ECSs use NVIDIA Tesla V100 GPUs and deliver high flexibility, high-performan
 
 **Specifications**
 
-.. table:: **Table 8** P2v ECS specifications
+.. table:: **Table 9** P2v ECS specifications
 
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------+----------------+-------------------------------------------+
    | Flavor         | vCPUs | Memory | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS (10,000) | Max. NIC Queues | Max. NICs | GPUs     | GPU Connection | GPU Memory | Virtualization | Hardware                                  |
    |                |       |        |                                         |                           |                 |           |          |                |            |                |                                           |
    |                |       | (GiB)  |                                         |                           |                 |           |          |                | (GiB)      |                |                                           |
    +================+=======+========+=========================================+===========================+=================+===========+==========+================+============+================+===========================================+
-   | p2v.2xlarge.8  | 8     | 64     | 10/4                                    | 50                        | 4               | 4         | 1 x V100 | N/A            | 1 x 16 GiB | KVM            | CPU: Intel® Xeon® Skylake-SP Gold 6151 v5 |
+   | p2v.2xlarge.8  | 8     | 64     | 10/4                                    | 50                        | 4               | 4         | 1 x V100 | ``-``          | 1 x 16 GiB | KVM            | CPU: Intel® Xeon® Skylake-SP Gold 6151 v5 |
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------+----------------+-------------------------------------------+
    | p2v.4xlarge.8  | 16    | 128    | 15/8                                    | 100                       | 8               | 8         | 2 x V100 | NVLink         | 2 x 16 GiB | KVM            |                                           |
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------+----------------+-------------------------------------------+
@@ -640,7 +696,7 @@ Pi5e ECSs use NVIDIA Ada Lovelace L4 Tensor Core GPUs that are dedicated for rea
 
 **Specifications**
 
-.. table:: **Table 9** Pi5e ECS specifications
+.. table:: **Table 10** Pi5e ECS specifications
 
    +-----------------+-------+--------+-----------------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+
    | Flavor          | vCPUs | Memory | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS | Max. NIC Queues | Max. NICs | GPUs   | GPU Memory | Local Disks | Virtualization |
@@ -686,22 +742,22 @@ Pi2 ECSs use NVIDIA Tesla T4 GPUs dedicated for real-time AI inference. These EC
 
 **Specifications**
 
-.. table:: **Table 10** Pi2 ECS specifications
+.. table:: **Table 11** Pi2 ECS specifications
 
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
    | Flavor         | vCPUs | Memory | Max./Assured Network Bandwidth | Max. Network PPS | Max. NIC Queues | Max. NICs | GPUs   | GPU Memory | Local Disks | Virtualization | Hardware                                                                         |
    |                |       |        |                                |                  |                 |           |        |            |             |                |                                                                                  |
    |                |       | (GiB)  | (Gbit/s)                       | (10,000)         |                 |           |        | (GiB)      |             |                |                                                                                  |
    +================+=======+========+================================+==================+=================+===========+========+============+=============+================+==================================================================================+
-   | pi2.2xlarge.4  | 8     | 32     | 10/4                           | 50               | 4               | 4         | 1 x T4 | 1 x 16 GiB | N/A         | KVM            | CPU: Intel® Xeon® Skylake 6151 3.0 GHz or Intel® Xeon® Cascade Lake 6278 2.6 GHz |
+   | pi2.2xlarge.4  | 8     | 32     | 10/4                           | 50               | 4               | 4         | 1 x T4 | 1 x 16 GiB | ``-``       | KVM            | CPU: Intel® Xeon® Skylake 6151 3.0 GHz or Intel® Xeon® Cascade Lake 6278 2.6 GHz |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
-   | pi2.3xlarge.4  | 12    | 48     | 12/6                           | 80               | 6               | 6         | 1 x T4 | 1 x 16 GiB | N/A         | KVM            |                                                                                  |
+   | pi2.3xlarge.4  | 12    | 48     | 12/6                           | 80               | 6               | 6         | 1 x T4 | 1 x 16 GiB | ``-``       | KVM            |                                                                                  |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
-   | pi2.4xlarge.4  | 16    | 64     | 15/8                           | 100              | 8               | 8         | 2 x T4 | 2 x 16 GiB | N/A         | KVM            |                                                                                  |
+   | pi2.4xlarge.4  | 16    | 64     | 15/8                           | 100              | 8               | 8         | 2 x T4 | 2 x 16 GiB | ``-``       | KVM            |                                                                                  |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
-   | pi2.8xlarge.4  | 32    | 128    | 25/15                          | 200              | 16              | 8         | 4 x T4 | 4 x 16 GiB | N/A         | KVM            |                                                                                  |
+   | pi2.8xlarge.4  | 32    | 128    | 25/15                          | 200              | 16              | 8         | 4 x T4 | 4 x 16 GiB | ``-``       | KVM            |                                                                                  |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
-   | pi2.16xlarge.4 | 64    | 256    | 30/30                          | 400              | 32              | 8         | 8 x T4 | 8 x 16 GiB | N/A         | KVM            |                                                                                  |
+   | pi2.16xlarge.4 | 64    | 256    | 30/30                          | 400              | 32              | 8         | 8 x T4 | 8 x 16 GiB | ``-``       | KVM            |                                                                                  |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
 
 **Pi2 ECS Features**
diff a/umn/source/service_overview/ecs_types_and_specifications/ecs_specifications/a_summary_list_of_ecs_specifications.rst b/umn/source/service_overview/ecs_types_and_specifications/ecs_specifications/a_summary_list_of_ecs_specifications.rst	(rejected hunks)
@@ -670,21 +670,33 @@ For more details, see :ref:`GPU-accelerated ECSs <en-us_topic_0097289624>`.
    | g6.20xlarge.7 | 80    | 560    | 30/30                          | 400              | 32              | 16        | 2 x T4 | 32         | KVM            |
    +---------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+----------------+
 
-.. table:: **Table 23** P5s ECS specifications
-
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
-   | Flavor          | vCPUs | Memory (GiB) | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS (10,000) | Max. NIC Queues | Max. NICs | GPUs           | GPU Memory (GiB) | Virtualization |
-   +=================+=======+==============+=========================================+===========================+=================+===========+================+==================+================+
-   | p5s.5xlarge.12  | 20    | 240          | 16/4.5                                  | 280                       | 8               | 4         | 1 \* H100 PCIe | 80               | KVM            |
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
-   | p5s.10xlarge.12 | 40    | 480          | 24/9                                    | 550                       | 16              | 8         | 2 \* H100 PCIe | 160              | KVM            |
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
-   | p5s.20xlarge.12 | 80    | 960          | 32/18                                   | 750                       | 32              | 8         | 4 \* H100 PCIe | 320              | KVM            |
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
-   | p5s.40xlarge.12 | 160   | 1920         | 40/36                                   | 850                       | 32              | 8         | 8 \* H100 PCIe | 640              | KVM            |
-   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+----------------+------------------+----------------+
-
-.. table:: **Table 24** P3 ECS specifications
+.. table:: **Table 23** P5e ECS specifications
+
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+--------------+------------------+----------------+
+   | Flavor          | vCPUs | Memory (GiB) | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS (10,000) | Max. NIC Queues | Max. NICs | GPUs         | GPU Memory (GiB) | Virtualization |
+   +=================+=======+==============+=========================================+===========================+=================+===========+==============+==================+================+
+   | p5e.10xlarge.12 | 40    | 480          | 24/9                                    | 550                       | 16              | 8         | 2 x H100 NVL | 188              | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+--------------+------------------+----------------+
+   | p5e.20xlarge.12 | 80    | 960          | 32/18                                   | 750                       | 32              | 8         | 4 x H100 NVL | 376              | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+--------------+------------------+----------------+
+   | p5e.40xlarge.12 | 160   | 1920         | 40/36                                   | 850                       | 32              | 8         | 8 x H100 NVL | 752              | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+--------------+------------------+----------------+
+
+.. table:: **Table 24** P5s ECS specifications
+
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
+   | Flavor          | vCPUs | Memory (GiB) | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS (10,000) | Max. NIC Queues | Max. NICs | GPUs          | GPU Memory (GiB) | Virtualization |
+   +=================+=======+==============+=========================================+===========================+=================+===========+===============+==================+================+
+   | p5s.5xlarge.12  | 20    | 240          | 16/4.5                                  | 280                       | 8               | 4         | 1 x H100 PCIe | 80               | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
+   | p5s.10xlarge.12 | 40    | 480          | 24/9                                    | 550                       | 16              | 8         | 2 x H100 PCIe | 160              | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
+   | p5s.20xlarge.12 | 80    | 960          | 32/18                                   | 750                       | 32              | 8         | 4 x H100 PCIe | 320              | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
+   | p5s.40xlarge.12 | 160   | 1,920        | 40/36                                   | 850                       | 32              | 8         | 8 x H100 PCIe | 640              | KVM            |
+   +-----------------+-------+--------------+-----------------------------------------+---------------------------+-----------------+-----------+---------------+------------------+----------------+
+
+.. table:: **Table 25** P3 ECS specifications
 
    +---------------+-------+--------+-----------------------------------------+------------------+-----------------+-----------+-----------------------+------------+----------------+
    | Flavor        | vCPUs | Memory | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS | Max. NIC Queues | Max. NICs | GPUs                  | GPU Memory | Virtualization |
@@ -700,7 +712,7 @@ For more details, see :ref:`GPU-accelerated ECSs <en-us_topic_0097289624>`.
    | p3.16xlarge.8 | 64    | 512    | 36/30                                   | 700              | 32              | 8         | 8 x NVIDIA A100 80 GB | 640        | KVM            |
    +---------------+-------+--------+-----------------------------------------+------------------+-----------------+-----------+-----------------------+------------+----------------+
 
-.. table:: **Table 25** P2s ECS specifications
+.. table:: **Table 26** P2s ECS specifications
 
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------------+----------------+----------------------------------------------------------+
    | Flavor         | vCPUs | Memory | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS (10,000) | Max. NIC Queues | Max. NICs | GPUs     | GPU Connection | GPU Memory (GiB) | Virtualization | Hardware                                                 |
@@ -716,14 +728,14 @@ For more details, see :ref:`GPU-accelerated ECSs <en-us_topic_0097289624>`.
    | p2s.16xlarge.8 | 64    | 512    | 30/30                                   | 400                       | 32              | 8         | 8 x V100 | PCIe Gen3      | 8 x 32 GiB       | KVM            |                                                          |
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------------+----------------+----------------------------------------------------------+
 
-.. table:: **Table 26** P2v ECS specifications
+.. table:: **Table 27** P2v ECS specifications
 
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------+----------------+-------------------------------------------+
    | Flavor         | vCPUs | Memory | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS (10,000) | Max. NIC Queues | Max. NICs | GPUs     | GPU Connection | GPU Memory | Virtualization | Hardware                                  |
    |                |       |        |                                         |                           |                 |           |          |                |            |                |                                           |
    |                |       | (GiB)  |                                         |                           |                 |           |          |                | (GiB)      |                |                                           |
    +================+=======+========+=========================================+===========================+=================+===========+==========+================+============+================+===========================================+
-   | p2v.2xlarge.8  | 8     | 64     | 10/4                                    | 50                        | 4               | 4         | 1 x V100 | N/A            | 1 x 16 GiB | KVM            | CPU: Intel® Xeon® Skylake-SP Gold 6151 v5 |
+   | p2v.2xlarge.8  | 8     | 64     | 10/4                                    | 50                        | 4               | 4         | 1 x V100 | ``-``          | 1 x 16 GiB | KVM            | CPU: Intel® Xeon® Skylake-SP Gold 6151 v5 |
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------+----------------+-------------------------------------------+
    | p2v.4xlarge.8  | 16    | 128    | 15/8                                    | 100                       | 8               | 8         | 2 x V100 | NVLink         | 2 x 16 GiB | KVM            |                                           |
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------+----------------+-------------------------------------------+
@@ -732,7 +744,7 @@ For more details, see :ref:`GPU-accelerated ECSs <en-us_topic_0097289624>`.
    | p2v.16xlarge.8 | 64    | 512    | 30/30                                   | 400                       | 32              | 8         | 8 x V100 | NVLink         | 8 x 16 GiB | KVM            |                                           |
    +----------------+-------+--------+-----------------------------------------+---------------------------+-----------------+-----------+----------+----------------+------------+----------------+-------------------------------------------+
 
-.. table:: **Table 27** Pi5e ECS specifications
+.. table:: **Table 28** Pi5e ECS specifications
 
    +-----------------+-------+--------+-----------------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+
    | Flavor          | vCPUs | Memory | Max./Assured Network Bandwidth (Gbit/s) | Max. Network PPS | Max. NIC Queues | Max. NICs | GPUs   | GPU Memory | Local Disks | Virtualization |
@@ -752,20 +764,20 @@ For more details, see :ref:`GPU-accelerated ECSs <en-us_topic_0097289624>`.
    | pi5e.24xlarge.4 | 96    | 384    | 40/36                                   | 850              | 32              | 8         | 6 x L4 | 144        | ``-``       | KVM            |
    +-----------------+-------+--------+-----------------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+
 
-.. table:: **Table 28** Pi2 ECS specifications
+.. table:: **Table 29** Pi2 ECS specifications
 
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
    | Flavor         | vCPUs | Memory | Max./Assured Network Bandwidth | Max. Network PPS | Max. NIC Queues | Max. NICs | GPUs   | GPU Memory | Local Disks | Virtualization | Hardware                                                                         |
    |                |       |        |                                |                  |                 |           |        |            |             |                |                                                                                  |
    |                |       | (GiB)  | (Gbit/s)                       | (10,000)         |                 |           |        | (GiB)      |             |                |                                                                                  |
    +================+=======+========+================================+==================+=================+===========+========+============+=============+================+==================================================================================+
-   | pi2.2xlarge.4  | 8     | 32     | 10/4                           | 50               | 4               | 4         | 1 x T4 | 1 x 16 GiB | N/A         | KVM            | CPU: Intel® Xeon® Skylake 6151 3.0 GHz or Intel® Xeon® Cascade Lake 6278 2.6 GHz |
+   | pi2.2xlarge.4  | 8     | 32     | 10/4                           | 50               | 4               | 4         | 1 x T4 | 1 x 16 GiB | ``-``       | KVM            | CPU: Intel® Xeon® Skylake 6151 3.0 GHz or Intel® Xeon® Cascade Lake 6278 2.6 GHz |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
-   | pi2.3xlarge.4  | 12    | 48     | 12/6                           | 80               | 6               | 6         | 1 x T4 | 1 x 16 GiB | N/A         | KVM            |                                                                                  |
+   | pi2.3xlarge.4  | 12    | 48     | 12/6                           | 80               | 6               | 6         | 1 x T4 | 1 x 16 GiB | ``-``       | KVM            |                                                                                  |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
-   | pi2.4xlarge.4  | 16    | 64     | 15/8                           | 100              | 8               | 8         | 2 x T4 | 2 x 16 GiB | N/A         | KVM            |                                                                                  |
+   | pi2.4xlarge.4  | 16    | 64     | 15/8                           | 100              | 8               | 8         | 2 x T4 | 2 x 16 GiB | ``-``       | KVM            |                                                                                  |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
-   | pi2.8xlarge.4  | 32    | 128    | 25/15                          | 200              | 16              | 8         | 4 x T4 | 4 x 16 GiB | N/A         | KVM            |                                                                                  |
+   | pi2.8xlarge.4  | 32    | 128    | 25/15                          | 200              | 16              | 8         | 4 x T4 | 4 x 16 GiB | ``-``       | KVM            |                                                                                  |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
-   | pi2.16xlarge.4 | 64    | 256    | 30/30                          | 400              | 32              | 8         | 8 x T4 | 8 x 16 GiB | N/A         | KVM            |                                                                                  |
+   | pi2.16xlarge.4 | 64    | 256    | 30/30                          | 400              | 32              | 8         | 8 x T4 | 8 x 16 GiB | ``-``       | KVM            |                                                                                  |
    +----------------+-------+--------+--------------------------------+------------------+-----------------+-----------+--------+------------+-------------+----------------+----------------------------------------------------------------------------------+
diff a/umn/source/backup_using_cbr/backing_up_an_ecs.rst b/umn/source/backup_using_cbr/backing_up_an_ecs.rst	(rejected hunks)
@@ -28,22 +28,22 @@ ECS Backup Procedure
 
 #. In the ECS list, locate the target ECS and choose **More** > **Manage Image/Backup** > **Create Server Backup**.
 
-   -  If the ECS has been associated with a vault, configure the backup information as prompted.
+   -  If the ECS has been associated with a vault, configure the backup information as instructed.
 
       -  **Server List**: The ECS to be backed up is selected by default.
       -  **Name**: Customize your backup name.
       -  **Description**: Supplementary information about the backup.
       -  **Full Backup**: If this option is selected, the system will perform full backup for the ECS to be associated. The storage capacity used by the backup increases accordingly.
 
-   -  If the ECS is not associated with a vault, buy a vault first and then configure the backup information as prompted.
+   -  If the ECS is not associated with a vault, buy a vault first and then configure the backup information as instructed.
 
       For details, see `Creating a Server Backup Vault <https://docs.otc.t-systems.com/cloud-backup-recovery/umn/getting_started/step_1_create_a_vault/creating_a_server_backup_vault.html>`__.
 
 #. Click **OK**. The system automatically creates a backup for the ECS.
 
-   On the **Backups** tab page, if the status of the backup is **Available**, the backup task is successful.
+   On the **Backups** tab, if the status of the backup is **Available**, the backup task is successful.
 
-   The ECS can be restarted if the backup progress of an ECS exceeds 10%. However, to ensure data integrity, restart it after the backup is complete.
+   The ECS can be restarted if the backup progress of an ECS exceeds 10%. However, to ensure data integrity, restart the ECS only after the backup is complete.
 
    After the backup is complete, you can restore server data or create images on the **Backups** tab page. For details, see `Restoring from a Cloud Server Backup <https://docs.otc.t-systems.com/en-us/usermanual/cbr/cbr_03_0032.html>`__ and `Creating an Image from a Cloud Server Backup <https://docs.otc.t-systems.com/en-us/usermanual/cbr/cbr_03_0016.html>`__.
 
diff a/umn/source/resources_and_tags/tag_management/adding_tags.rst b/umn/source/resources_and_tags/tag_management/adding_tags.rst	(rejected hunks)
@@ -51,7 +51,7 @@ Adding Tags on the ECS Details Page
 
 #. Click |image2| in the upper left corner and select a region and project.
 
-#. Under\ **Computing**, click **Elastic Cloud Server**. The **Elastic Cloud Server** page is displayed.
+#. Under **Computing**, click **Elastic Cloud Server**. The **Elastic Cloud Server** page is displayed.
 
 #. In the ECS list, click the name of the target ECS.
 
diff a/umn/source/resources_and_tags/tag_management/searching_for_resources_by_tag.rst b/umn/source/resources_and_tags/tag_management/searching_for_resources_by_tag.rst	(rejected hunks)
@@ -41,10 +41,10 @@ Filtering Resources on the TMS Console
 
 #. Under **Management & Deployment**, click **Tag Management Service**.
 
-#. On the **Resource Tags** page, set the search criteria, including **Region**, **Resource Type**, and **Resource Tag**.
+#. On the displayed page, set the search criteria, including **Region**, **Resource Type**, and **Resource Tag**.
 
 #. Click **Search**.
 
-   All the resources that meet the search criteria will be displayed in the **Search Result** area.
+   All the resources that meet the search criteria will be displayed in the **Search Results** area.
 
 .. |image1| image:: /_static/images/en-us_image_0000002188678994.png
diff a/umn/source/elastic_network_interfaces/dynamically_assigning_ipv6_addresses.rst b/umn/source/elastic_network_interfaces/dynamically_assigning_ipv6_addresses.rst	(rejected hunks)
@@ -108,7 +108,7 @@ Windows Server 2012
 
          **Figure 1** Querying the IPv6 address
 
-   -  If only a link-local IPv6 address is displayed, IPv6 is enabled but dynamic IPv6 assignment is not enabled. Go to step :ref:`2 <en-us_topic_0140963099__en-us_topic_0129883696_li2024825592115>`.
+   -  If only a link-local IPv6 address is displayed, IPv6 is enabled but dynamic IPv6 assignment is not enabled. Go to :ref:`2 <en-us_topic_0140963099__en-us_topic_0129883696_li2024825592115>`.
 
 
       .. figure:: /_static/images/en-us_image_0000001723492302.png
@@ -116,7 +116,7 @@ Windows Server 2012
 
          **Figure 2** Link-local IPv6 address
 
-   -  If neither an IPv6 address nor link-local IPv6 address is displayed, IPv6 is disabled. Go to step :ref:`3 <en-us_topic_0140963099__en-us_topic_0129883696_li35521349132511>`.
+   -  If neither an IPv6 address nor link-local IPv6 address is displayed, IPv6 is disabled. Go to :ref:`3 <en-us_topic_0140963099__en-us_topic_0129883696_li35521349132511>`.
 
 
       .. figure:: /_static/images/en-us_image_0000001771211453.png
@@ -178,7 +178,7 @@ Windows Server 2012
 
       **Set-NetIPv6Protocol -RandomizeIdentifiers disabled**
 
-   c. Perform step :ref:`1 <en-us_topic_0140963099__en-us_topic_0129883696_li64771254152011>` to check whether dynamic IPv6 address assignment is enabled.
+   c. Perform :ref:`1 <en-us_topic_0140963099__en-us_topic_0129883696_li64771254152011>` to check whether dynamic IPv6 address assignment is enabled.
 
 .. _en-us_topic_0140963099__en-us_topic_0129883696_section106971627556:
 
@@ -482,9 +482,9 @@ Linux (Manually Enabling Dynamic Assignment of IPv6 Addresses)
 
             If no IPv6 address is assigned after the NICs are brought down and up, you can run this command to restart the network.
 
-      d. Perform step :ref:`1 <en-us_topic_0140963099__en-us_topic_0129883696_li967053013012>` to check whether dynamic IPv6 address assignment is enabled.
+      d. Perform :ref:`1 <en-us_topic_0140963099__en-us_topic_0129883696_li967053013012>` to check whether dynamic IPv6 address assignment is enabled.
 
-   -  CentOS, EulerOS, or Fedora
+   -  CentOS, EulerOS, Fedora, or openEuler
 
       a. Open the configuration file **/etc/sysconfig/network-scripts/ifcfg-eth0** of the primary NIC.
 
@@ -562,7 +562,7 @@ Linux (Manually Enabling Dynamic Assignment of IPv6 Addresses)
 
             **systemctl restart NetworkManager**
 
-      f. Perform step :ref:`1 <en-us_topic_0140963099__en-us_topic_0129883696_li967053013012>` to check whether dynamic IPv6 address assignment is enabled.
+      f. Perform :ref:`1 <en-us_topic_0140963099__en-us_topic_0129883696_li967053013012>` to check whether dynamic IPv6 address assignment is enabled.
 
    -  SUSE, openSUSE, or CoreOS
 
diff a/umn/source/getting_started/creating_an_ecs/step_3_configure_advanced_settings.rst b/umn/source/getting_started/creating_an_ecs/step_3_configure_advanced_settings.rst	(rejected hunks)
@@ -46,7 +46,7 @@ Advanced Settings
    -  Create new
 
       a. Enter the name of the cloud backup vault. The name consists of 1 to 64 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. For example, **vault-f61e**. The default naming rule is **vault\_**\ *xxxx*.
-      b. Enter the vault capacity, which is required for backing up the ECS. The vault capacity cannot be smaller than that of the ECS to be backed up. The value range is from the total capacity of the ECS to 10,485,760 in the unit of GiB.
+      b. Enter the vault capacity, which is required for backing up the ECS. The vault capacity cannot be smaller than that of the ECS to be backed up. The value range is from the ECS's total capacity to 10,485,760, in GiB.
       c. Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one.
 
    -  Use existing
diff a/umn/source/cloud_eye_monitoring/viewing_ecs_metrics.rst b/umn/source/cloud_eye_monitoring/viewing_ecs_metrics.rst	(rejected hunks)
@@ -40,13 +40,13 @@ Procedure
 
 #. Under **Computing**, click **Elastic Cloud Server**.
 
-#. In the search box above the upper right corner of the ECS list, enter the ECS name, IP address, or ID to search for the target ECS.
+#. In the search box above the ECS list, enter the ECS name, IP address, or ID to search for the target ECS.
 
 #. Click the name of the target ECS. The ECS details page is displayed.
 
 #. Click the **Monitoring** tab to view the monitoring data.
 
-#. In the ECS monitoring area, select a duration to view the monitoring data.
+#. In the ECS monitoring area, select a time range to view the monitoring data.
 
    You can view the monitoring data of the ECS in the last 1 hour, last 3 hours, last 12 hours, last 1 day, or last 7 days. You can also select a custom time range to view the historical monitoring data of the last six months.