diff --git a/tidb-cloud/serverless-export.md b/tidb-cloud/serverless-export.md
index b9e9098b4a710..a0e6271936176 100644
--- a/tidb-cloud/serverless-export.md
+++ b/tidb-cloud/serverless-export.md
@@ -31,8 +31,9 @@ You can export data to:
 
 Exporting data to local file has the following limitations:
 
+- You can only download the exported data with the [TiDB Cloud CLI](/tidb-cloud/cli-reference.md), download on the console is not supported.
 - Exported data is saved in the stashing area and will expire after two days. You need to download the exported data in time.
-- If the storage space of stashing area is full, you will not be able to export data to local file.
+- If the storage space of stashing area is full, you will not be able to export data to the local file.
 
 ### Amazon S3
 
@@ -56,7 +57,7 @@ See [Configure TiDB Cloud Serverless external storage access](/tidb-cloud/server
 
 > **Note:**
 >
-> Only supported in TiDB Cloud CLI now.
+> You can only export to Google Cloud Storage with TiDB Cloud CLI now.
 
 ### Azure Blob Storage
 
@@ -69,7 +70,7 @@ See [Configure TiDB Cloud Serverless external storage access](/tidb-cloud/server
 
 > **Note:**
 >
-> Only supported in TiDB Cloud CLI now.
+> You can only export to Azure Blob Storage with TiDB Cloud CLI now.
 
 ## Export options
 
diff --git a/tidb-cloud/serverless-external-storage.md b/tidb-cloud/serverless-external-storage.md
index 098fa6a8320cd..b402eefcdb571 100644
--- a/tidb-cloud/serverless-external-storage.md
+++ b/tidb-cloud/serverless-external-storage.md
@@ -54,11 +54,11 @@ Take the following steps to configure a service account key:
 
    ![img.png](../media/tidb-cloud/serverless-external-storage/gcs-service-account.png)
 
-2. Click the service account and then click the `ADD KEY` button in the `KEYS` page to create a service account key. 
+2. Click the service account and then click the **ADD KEY** button in the `KEYS` page to create a service account key. 
 
     ![img.png](../media/tidb-cloud/serverless-external-storage/gcs-service-account-key.png)
 
-3. Choose the default `JSON` key type and click the `CREATE` button to download the service account key.
+3. Choose the default `JSON` key type and click the **CREATE** button to download the service account key.
 
 4. Open the downloaded JSON file and encode the content with base64. For example, you can use the following command to encode the content in the macOS terminal:
 
@@ -73,17 +73,17 @@ To allow TiDB Cloud Serverless to access your Azure Blob container, you need to
 Take the following steps to configure a service SAS token:
 
 1. Click your storage account where the container belong to in the [Azure storage account](https://portal.azure.com/#browse/Microsoft.Storage%2FStorageAccounts) page.
-2. In your `storage account` page, click the `Security+network` and then click the `Shared access signature`.
+2. In your `storage account` page, click the **Security+network** and then click the **Shared access signature**.
 
     ![img.png](../media/tidb-cloud/serverless-external-storage/azure-sas.png)
 
 3. In the `Shared access signature` page, create a service SAS token with needed permission. For more information, see [Create a service SAS token](https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview).
    1. Choose the `Blob` service under the `Allowed services` section.
    2. Choose the `Container` and `Object` under the `Allowed Resource types` section.
-   3. Choose the permission under the `Allowed permissions` section as you needed. For example: TiDB Cloud Serverless exports needs `Write` permission.
+   3. Choose the permission under the `Allowed permissions` section as you needed. For example: TiDB Cloud Serverless exports needs `Read` and `Write` permission.
    4. Adjust the `Start and expiry date/time` as you needed.
-   5. You can keep other settings as default and click the `Generate SAS and connection string` button.
+   5. You can keep other settings as default.
 
    ![img.png](../media/tidb-cloud/serverless-external-storage/azure-create-sas.png)
 
-4. The SAS token will be generated, and you can use it to configure the Azure Blob access.
+4. Click the **Generate SAS and connection string** button to generate the SAS token.