test-nicole'sagen-commit

[nicole-yc]

First-time contributors' checklist

• I've signed the Contributor License Agreement, which is required for the repository owners to accept my contribution.

What is changed, added or deleted? (Required)

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)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)
• v6.1 (TiDB 6.1 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]

Hi @nicole-yc. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign csuzhangxc for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Code Review

This pull request cleans up and generalizes region-specific information across the 2022, 2023, and 2024 release notes for TiDB Cloud, removing specific references to regions like Mumbai, Osaka, and N. Virginia. The review feedback focuses on improving clarity, conciseness, and style guide compliance, specifically by recommending active voice, simplifying phrasing to 'Available in', and clarifying 'dual-region backup'.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

To make the sentence more concise and natural, you can simplify "Provide services in" to "Available in". This aligns with the style guide's principle of avoiding unnecessary words.

Suggested change

	- Provide services in the following 5 regions:
	- Available in the following 5 regions:

References

1. Avoid unnecessary words and repetition. ^(link)

[gemini-code-assist]

The phrases "is stored" and "is created" are in the passive voice. According to the style guide, we should avoid passive voice and write in the second person ("you") and present tense. Rewriting this to active voice makes the instruction more direct and clear.

Suggested change

	By default, backup data is stored in the same region where the cluster is created. For TiDB clusters hosted on GCP with PITR enabled, you can choose to store backup data in a supported region. Restoring data from an alternative region provides a higher level of data safety and can tolerate region failures.
	By default, TiDB Cloud stores backup data in the same region where you create the cluster. For TiDB clusters hosted on GCP with PITR enabled, you can choose to store backup data in a supported region. Restoring data from an alternative region provides a higher level of data safety and can tolerate region failures.

References

1. Avoid passive voice overuse (e.g., "The cluster is started by TiUP" -> "TiUP starts the cluster"). ^(link)

[gemini-code-assist]

The phrase "the dual-region" is slightly unclear and grammatically incomplete in this context. Specifying "dual-region backup" improves clarity and consistency with the feature name mentioned in the heading.

Suggested change

	TiDB Cloud Dedicated clusters hosted on Google Cloud work seamlessly with Google Cloud Storage. Similar to the [Dual-regions](https://cloud.google.com/storage/docs/locations#location-dr) feature of Google Cloud Storage, the pair of regions that you use for the dual-region in TiDB Cloud Dedicated must be within the same multi-region.
	TiDB Cloud Dedicated clusters hosted on Google Cloud work seamlessly with Google Cloud Storage. Similar to the [Dual-regions](https://cloud.google.com/storage/docs/locations#location-dr) feature of Google Cloud Storage, the pair of regions that you use for dual-region backup in TiDB Cloud Dedicated must be within the same multi-region.

References

1. Clarity, simplicity, completeness, and readability. ^(link)