tidbcloud: update changefeed replication

[zier-one]

First-time contributors' checklist

• I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added or deleted? (Required)

refine the docs of the changefeed replication in tidb cloud

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v6.1 (TiDB 6.1 versions)
• v6.0 (TiDB 6.0 versions)
• v5.4 (TiDB 5.4 versions)
• v5.3 (TiDB 5.3 versions)
• v5.2 (TiDB 5.2 versions)
• v5.1 (TiDB 5.1 versions)
• v5.0 (TiDB 5.0 versions)
• v4.0 (TiDB 4.0 versions)

What is the related PR or file link(s)?

• This PR is translated from:
• Other reference link(s):

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[qiancai]

Suggested change

	* The network latency between the primary and secondary clusters affects the performance or stability of **TiDB Cloud Replication**. with the following limitations:
	* Depending on the network latency between the primary and secondary clusters, the performance and stability of **TiDB Cloud Replication** are affected as follows:

[qiancai]

Suggested change

	* When the network latency between 120 millisecond and 180 millisecond, the performance of **TiDB Cloud Replication** may be affected.
	* When the network latency is between 120 milliseconds and 180 milliseconds, the performance of **TiDB Cloud Replication** might be affected.

[qiancai]

Suggested change

	* The network latency less than 120 millisecond is recommended.
	* To achieve the best performance and stability of **TiDB Cloud Replication**, the network latency within 120 milliseconds is recommended.

[qiancai]

Suggested change

	* When the network latenct is greater than 180 millisecond, **TiDB Cloud Replication** will not work.
	* When the network latency exceeds 180 milliseconds, **TiDB Cloud Replication** cannot provide service normally.

[qiancai]

Suggested change

	- [Secondary Replication](changefeed-replication.md)
	- [Secondary Replication](/tidb-cloud/changefeed-replication.md)

[qiancai]

@leoppro I've completed the review and made some comments. PTAL. Thanks.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

leoppro seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}