i18n(ja): fix scrambled global-index note in 3 sql-statement docs

[yahonda]

What is changed, added or deleted? (Required)

Found while reviewing PR #23509 (a daily translation-sync PR): the note about setting a PRIMARY KEY/UNIQUE INDEX/UNIQUE KEY as a global index with the GLOBAL index option had its word order completely scrambled in 3 sibling files, swapping which term modifies which and mangling "partitioned tables" into a garbled duplicate ("パーティション化[パーティション化されたテーブル]").

• sql-statements/sql-statement-add-index.md
• sql-statements/sql-statement-create-index.md
• sql-statements/sql-statement-create-table.md

Restored each to match the English source's actual meaning: "Setting a PRIMARY KEY (or UNIQUE INDEX/UNIQUE KEY) as a global index using the GLOBAL index option is a TiDB extension for partitioned tables and is not compatible with MySQL."

Note: PR #23509 (still open) happens to touch one of these exact lines (sql-statement-add-index.md) — its change is limited to accidentally converting the line's trailing 。 to a half-width ., unrelated to the actual scrambling this PR fixes. Whichever of the two PRs merges first, the other will need a trivial rebase on this one line.

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)

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

• This PR is translated from:
• Other reference link(s): i18n-ja-release-8.5: translate doc changes from pingcap/docs release-8.5 on 2026-08-13 #23509

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f99f2bff-bc9a-4203-841d-b9978dcd059c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[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 kissmydb 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

[yahonda]

Superseded — this fix has been committed directly onto #23509's branch instead, per the reviewer's request to keep all #23509 review findings on that PR itself.