update UI text according to UI

Author: qiancai

tidb-cloud/changefeed-sink-to-apache-kafka.md

@@ -125,7 +125,7 @@ The steps vary depending on the connectivity method you select.
 <div label="Private Link (AWS)">
 
 1. In **Connectivity Method**, select **Private Link**.
-2. In **Sink Private Endpoint**, select the private endpoint that you created in the [Network](#network) section. Make sure the AZs of the private endpoint match the AZs of the Kafka deployment.
+2. In **Private Endpoint**, select the private endpoint that you created in the [Network](#network) section. Make sure the AZs of the private endpoint match the AZs of the Kafka deployment.
 3. Fill in the **Bootstrap Ports** that you obtained from the [Network](#network) section. It is recommended that you set at least one port for one AZ. You can use commas `,` to separate multiple ports.
 4. Select an **Authentication** option according to your Kafka authentication configuration.
 
@@ -143,7 +143,7 @@ The steps vary depending on the connectivity method you select.
 <div label="Private Service Connect (Google Cloud)">
 
 1. In **Connectivity Method**, select **Private Service Connect**.    
-2. In **Sink Private Endpoint**, select the private endpoint that you created in the [Network](#network) section.
+2. In **Private Endpoint**, select the private endpoint that you created in the [Network](#network) section.
 3. Fill in the **Bootstrap Ports** that you obtained from the [Network](#network) section. It is recommended that you provide more than one port. You can use commas `,` to separate multiple ports. 
 4. Select an **Authentication** option according to your Kafka authentication configuration.
 
@@ -161,7 +161,7 @@ The steps vary depending on the connectivity method you select.
 <div label="Private Link (Azure)">
 
 1. In **Connectivity Method**, select **Private Link**.
-2. In **Sink Private Endpoint**, select the private endpoint that you created in the [Network](#network) section.
+2. In **Private Endpoint**, select the private endpoint that you created in the [Network](#network) section.
 3. Fill in the **Bootstrap Ports** that you obtained in the [Network](#network) section. It is recommended that you set at least one port for one AZ. You can use commas `,` to separate multiple ports.
 4. Select an **Authentication** option according to your Kafka authentication configuration.
 

tidb-cloud/changefeed-sink-to-mysql.md

@@ -113,7 +113,7 @@ After completing the prerequisites, you can sink your data to MySQL.
 3. In **Connectivity Method**, choose the method to connect to your MySQL service.
 
     - If you choose **VPC Peering** or **Public IP**, fill in your MySQL endpoint.
-    - If you choose **Private Endpoint**, select the private endpoint that you created in the [Network](#network) section, and fill in the MySQL port for your MySQL service.
+    - If you choose **Private Link**, select the private endpoint that you created in the [Network](#network) section, and then fill in the MySQL port for your MySQL service.
 
 4. In **Authentication**, fill in the MySQL user name and password of your MySQL service.
 

tidb-cloud/set-up-sink-private-endpoint.md

@@ -66,45 +66,45 @@ The configuration steps vary depending on the cloud provider where your cluster
 <SimpleTab>
 <div label="AWS">
 
-1. On the **Create Sink Private Endpoint** page, enter a name for the private endpoint.
-2. Follow the tip to authorize the [AWS Principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html#principal-accounts) of TiDB Cloud to create an endpoint.
+1. In the **Create Private Endpoint for Changefeed** dialog, enter a name for the private endpoint.
+2. Follow the reminder to authorize the [AWS Principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_principal.html#principal-accounts) of TiDB Cloud to create an endpoint.
 3. Enter the **Endpoint Service Name** that that you collected in the [Network](#network) section.
-4. Select the **Number of Availability Zones**. Ensure that the number of AZs and the AZ IDs match your Kafka deployment.
+4. Select the **Number of AZs**. Ensure that the number of AZs and the AZ IDs match your Kafka deployment.
 5. If this private endpoint is created for Apache Kafka, enable the **Advertised Listener for Kafka** option.
-6. Configure the advertised listener for Kafka using either **TiDB Managed Domain** or **Custom Domain**.
+6. Configure the advertised listener for Kafka using either **TiDB Managed** domain or **Custom** domain.
 
-    - To use **TiDB Managed Domain** for advertised listeners, enter a unique string in the **Domain Pattern** field, and then click **Generate**. TiDB will generate broker addresses with subdomains for each availability zone.
-    - To use your own **Custom Domain** for advertised listeners, enter the root domain, click **Check**, and then specify the broker subdomains for each availability zone.
+    - To use **TiDB Managed** domain for advertised listeners, enter a unique string in the **Domain Pattern** field, and then click **Generate**. TiDB will generate broker addresses with subdomains for each availability zone.
+    - To use your own **Custom** domain for advertised listeners, switch the domain type to **Custom**, enter the root domain in the **Custom Domain** field, click **Check**, and then specify the broker subdomains for each availability zone.
 
 7. Click **Create** to validate the configurations and create the private endpoint.
 
 </div>
 
 <div label="Google Cloud">
 
-1. On the **Create Sink Private Endpoint** page, enter a name for the private endpoint.
-2. Follow the tip to authorize the [Google Cloud project](https://cloud.google.com/resource-manager/docs/creating-managing-projects) of TiDB Cloud to pre-approve endpoint creation, or manually approve the endpoint connection request when you receive it.
+1. In the **Create Private Endpoint for Changefeed** dialog, enter a name for the private endpoint.
+2. Follow the reminder to authorize the [Google Cloud project](https://cloud.google.com/resource-manager/docs/creating-managing-projects) of TiDB Cloud to pre-approve endpoint creation, or manually approve the endpoint connection request when you receive it.
 3. Enter the **Service Attachment** that that you collected in the [Network](#network) section.
 4. If this private endpoint is created for Apache Kafka, enable the **Advertised Listener for Kafka** option.
-5. Configure the advertised listener for Kafka using either **TiDB Managed Domain** or **Custom Domain**.
+5. Configure the advertised listener for Kafka using either **TiDB Managed** domain or **Custom** domain.
 
-    - To use **TiDB Managed Domain** for advertised listeners, enter a unique string in the **Domain Pattern** field, and then click **Generate**. TiDB will generate broker addresses with subdomains for each availability zone.
-    - To use your own **Custom Domain** for advertised listeners, enter the root domain, click **Check**, and then specify the broker subdomains for each availability zone.
+    - To use **TiDB Managed** domain for advertised listeners, enter a unique string in the **Domain Pattern** field, and then click **Generate**. TiDB will generate broker addresses with subdomains for each availability zone.
+    - To use your own **Custom** domain for advertised listeners, switch the domain type to **Custom**, enter the root domain in the **Custom Domain** field, click **Check**, and then specify the broker subdomains for each availability zone.
 
 6. Click **Create** to validate the configurations and create the private endpoint.
 
 </div>
 
 <div label="Azure">
 
-1. On the **Create Sink Private Endpoint** page, enter a name for the private endpoint.
-2. Follow the tip to authorize the Azure subscription of TiDB Cloud or allow anyone with your alias to access your Private Link service before creating the changefeed. For more information about Private Link service visibility, see [Control service exposure](https://learn.microsoft.com/en-us/azure/private-link/private-link-service-overview#control-service-exposure) in Azure documentation.
+1. In the **Create Private Endpoint for Changefeed** dialog, enter a name for the private endpoint.
+2. Follow the reminder to authorize the Azure subscription of TiDB Cloud or allow anyone with your alias to access your Private Link service before creating the changefeed. For more information about Private Link service visibility, see [Control service exposure](https://learn.microsoft.com/en-us/azure/private-link/private-link-service-overview#control-service-exposure) in Azure documentation.
 3. Enter the **Alias of Private Link Service** that you collected in the [Network](#network) section.
 4. If this private endpoint is created for Apache Kafka, enable the **Advertised Listener for Kafka** option.
-5. Configure the advertised listener for Kafka using either **TiDB Managed Domain** or **Custom Domain**.
+5. Configure the advertised listener for Kafka using either **TiDB Managed** domain or **Custom** domain.
 
-    - To use **TiDB Managed Domain** for advertised listeners, enter a unique string in the **Domain Pattern** field, and then click **Generate**. TiDB will generate broker addresses with subdomains for each availability zone.
-    - To use your own **Custom Domain** for advertised listeners, enter the root domain, click **Check**, and then specify the broker subdomains for each availability zone.
+    - To use **TiDB Managed** domain for advertised listeners, enter a unique string in the **Domain Pattern** field, and then click **Generate**. TiDB will generate broker addresses with subdomains for each availability zone.
+    - To use your own **Custom** domain for advertised listeners, switch the domain type to **Custom**, enter the root domain in the **Custom Domain** field, click **Check**, and then specify the broker subdomains for each availability zone.
 
 6. Click **Create** to validate the configurations and create the private endpoint.