Apply suggestions from code review

Co-authored-by: Grace Cai <qqzczy@126.com>

Author: hfxsd

tidb-cloud/set-up-private-endpoint-connections-on-azure.md

@@ -77,10 +77,10 @@ If you have multiple clusters, you need to repeat these steps for each cluster t
     >
     > For each TiDB Cloud Dedicated cluster, the corresponding endpoint service is automatically created 3 to 4 minutes after the cluster creation.
 
-2. Create the private endpoint by using either Azure Portal or Azure CLI.
+2. Create the private endpoint by using either the Azure portal or Azure CLI.
 
 <SimpleTab>
-<div label="Use Azure Portal">
+<div label="Use Azure portal">
 
 1. Log in to the [Azure portal](https://portal.azure.com/).
 2. Search for **Private endpoints**, and then select **Private endpoints** in the result.
@@ -108,7 +108,7 @@ If you have multiple clusters, you need to repeat these steps for each cluster t
     az account set --subscription ${your_subscription_id}
     ```
 
-2. Create the private endpoint by using the TiDB Cloud resource ID copied in Step 2:
+2. Create the private endpoint by using the TiDB Cloud resource ID that you copied from the **Create Azure Private Endpoint Connection** dialog:
 
     ```bash
     az network private-endpoint create \

tidb-cloud/set-up-private-endpoint-connections-on-google-cloud.md

@@ -144,7 +144,7 @@ Before you begin to create an endpoint:
 
 ### Step 3. Accept endpoint access
 
-After creating the endpoint in Google Cloud successfully, go back to the TiDB Cloud console and then click **Accept Endpoint Access**.
+After creating the endpoint in Google Cloud successfully, go back to the TiDB Cloud console, and then click **Accept Endpoint Access**.
 
 If you see an error `not received connection request from endpoint`, make sure that you have successfully created the endpoint in your Google Cloud project and that its configuration matches the generated command.