docs: fix topic message custom fee limit method

Signed-off-by: Ziliang-H <2270669192@qq.com>

Author: Ziliang-H

native/consensus/submit-message.mdx

@@ -16,15 +16,15 @@ The **max chunk size** refers to the maximum size (in bytes) of each individual
 
 ## **Custom Fee Payment**
 
-If a topic has custom fees enabled, users submitting messages must pay the required fee in **HBAR or HTS fungible tokens**. If `setCustomFees` is not specified in the transaction, the user would need to pay any fee associated with that topic ID. The transaction will only fail if the user does not have sufficient assets to cover the fee.
+If a topic has custom fees enabled, users submitting messages must pay the required fee in **HBAR or HTS fungible tokens**. If `setCustomFeeLimits` is not specified in the transaction, the user would need to pay any fee associated with that topic ID. The transaction will only fail if the user does not have sufficient assets to cover the fee.
 
-**Recommendation:** To avoid unexpected fees, it is strongly recommended to use `setCustomFees` when submitting a message. This ensures that only the intended fee structure is applied, providing a safeguard against unintended charges.
+**Recommendation:** To avoid unexpected fees, it is strongly recommended to use `setCustomFeeLimits` or `addCustomFeeLimit` when submitting a message. This ensures that only the intended fee structure is applied, providing a safeguard against unintended charges.
 
 ```java
 TopicMessageSubmitTransaction()
    .setTopicId(<TOPIC_ID>)
    .setMessage(<MESSAGE>)
-   .setCustomFees(<MAX_CUSTOM_FEES>) // Ensure this covers the required amount
+   .setCustomFeeLimits(<CUSTOM_FEE_LIMITS>) // Ensure this covers the required amount
    .execute(client);
 ```
 
@@ -38,7 +38,7 @@ TopicMessageSubmitTransaction()
 - Each transaction incurs a standard Hedera network fee based on network resource usage.
 - If a custom fee is set for a topic, users submitting messages must pay this fee in HBAR or HTS tokens.
 - The Fee Schedule Key allows authorized users to update fee structures. If set, it must sign transactions modifying fees.
-- If the topic has custom fees, the sender must have sufficient balance to cover the fees unless they are exempt via the Fee Exempt Key List. It is recommended to use `setCustomFees` on the `TopicMessageSubmitTransaction` to ensure the expected fee structure is applied and avoid unexpected transaction failures due to insufficient funds.
+- If the topic has custom fees, the sender must have sufficient balance to cover the fees unless they are exempt via the Fee Exempt Key List. It is recommended to use `setCustomFeeLimits` or `addCustomFeeLimit` on the `TopicMessageSubmitTransaction` to ensure the expected fee structure is applied and avoid unexpected transaction failures due to insufficient funds.
 - If you submit a message to a topic with a custom fee, the cost changes from the baseline $0.0001 USD to roughly $0.05 USD per `TopicMessageSubmitTransaction`.
 - Use the [query fees table](/learn/networks/mainnet/fees#consensus-service) for the base transaction fee and the [Hedera Fee Estimator](https://hedera.com/fees) to estimate standard network fees.
 
@@ -133,7 +133,7 @@ TopicMessageSubmitTransaction()
 TopicMessageSubmitTransaction transaction = new TopicMessageSubmitTransaction()
     .setTopicId(newTopicId)
     .setMessage("hello, HCS! ")
-    .setMaxCustomFees(maxCustomFees); // Set max custom fees if applicable
+    .setCustomFeeLimits(customFeeLimits); // Set custom fee limits if applicable
 
 //Sign with the client operator key and submit transaction to a Hedera network, get transaction ID
 TransactionResponse txResponse = transaction.execute(client);
@@ -155,7 +155,7 @@ System.out.println("The transaction consensus status is " +transactionStatus);
 const transaction = await new TopicMessageSubmitTransaction()
   .setTopicId(newTopicId)
   .setMessage("Hello, HCS!")
-  .setMaxCustomFees(maxCustomFees); // Set max custom fees if applicable
+  .setCustomFeeLimits(customFeeLimits); // Set custom fee limits if applicable
 
 // Execute transaction
 const txResponse = await transaction.execute(client);