i18n(ja): keep SQL transaction isolation level names in English

[yahonda]

What is changed, added or deleted? (Required)

Repeatable Read and Read Committed (and their literal SQL keyword forms REPEATABLE READ / READ COMMITTED) are SQL-92 standard isolation-level names, not descriptive phrases that should be translated. This corpus rendered Repeatable Read inconsistently with 3 competing literal-kanji/katakana translations while English already dominated elsewhere.

This PR unifies the remaining non-English Repeatable Read occurrences to the literal English term, mirroring each site's own exact EN casing rather than picking one fixed form:

• 繰り返し読み取り → Repeatable Read (title case, matching most prose mentions)
• 反復可能読み取り → Repeatable Read
• リピータブルリード → Repeatable Read
• one occurrence → repeatable read (lowercase, matching the SQL-92 four-level bullet list in develop/dev-guide-transaction-overview.md, where EN itself uses lowercase)

Also converts the 2 sibling entries in that same four-level bullet list (コミットされていない読み取り → read uncommitted, シリアル化可能 → serializable) that were left translated while the other two entries in the identical list were being fixed, producing an inconsistent list — the trailing full stop after serializable mirrors EN's own list, which ends the last item with a period.

Also unifies the section headings ("Repeatable Read isolation level" / "Read Committed isolation level") to match the mixed English-term + 分離レベル pattern already used consistently in every body occurrence of these terms in the same file, rather than mirroring EN's fully-English heading text — and removes 2 stray extra spaces before 分離レベル for the same consistency.

6 files, ~20 sites.

Also fixes, found along the way:

• 3 directly-adjacent Read Committed occurrences that were the same defect on the same line/heading/file as a Repeatable Read fix: transaction-isolation-levels.md's ## Read Committed isolation level heading (before being unified per above), which the rest of that file already used consistently in body text; one shared table cell in tidb-performance-tuning-config.md; and a literal コミット済みを読む link text in pessimistic-transaction.md that should read Read Committed like its sibling Repeatable Read link two lines above.
• 3 stray text fragments left before links in transaction-isolation-levels.md with no counterpart in EN, the same defect class fixed corpus-wide in i18n(ja): fix stray text fragments and scrambled link lists #23640/i18n(ja): fix particle/punctuation trapped inside bold spans #23641: two "SI" fragments and a "1番目の" (lit. "the first") fragment before an unrelated paper citation link.
• 2 particle/punctuation-trapped-in-bold defects in transaction-isolation-levels.md, part of the same corpus-wide sweep as i18n(ja): fix particle/punctuation trapped inside bold spans #23641.
• Reworded 宣伝 ("advertise" in the exaggerated/promotional sense) to 表示されます (neutral "is displayed as") in the 3 sites describing TiDB's REPEATABLE-READ compatibility label — 宣伝 reads as if TiDB were making a marketing claim, not a neutral technical report of its isolation-level name. Also fixed the one remaining 宣伝 in the corpus, in tikv-configuration-file.md's advertise-addr description, to match the established アドバタイズ katakana term already used consistently for that networking sense of "advertise" across DM/PD/Kafka config docs.

Other Read Committed occurrences elsewhere in the corpus (system-variables.md, several release notes) are the same defect class but out of scope for this PR — left for a follow-up sweep. スナップショット分離 ("Snapshot Isolation") was also checked and found already consistent (17 occurrences, dominant, well-formed) — not part of this PR.

Independently re-reviewed the full diff and did a structural 1:1 comparison of transaction-isolation-levels.md against the EN source (line count, heading position, and anchors all match exactly) before marking ready for review.

Verified markdownlint-cli2 clean on all touched files.

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

• i18n-ja-release-8.5 (TiDB Japanese documentation for TiDB 8.5 versions)

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

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

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

Summary by CodeRabbit

• Documentation
  • Standardized Japanese transaction documentation to use the official English names for SQL isolation levels.
  • Clarified wording describing how snapshot isolation and REPEATABLE-READ are displayed.
  • Updated related configuration and system variable references for consistent terminology.
  • Improved the Japanese wording for the advertise-addr configuration description.

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

Warning

Review limit reached

Next included review available in 9 minutes.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1ceef130-195e-4f64-8eb2-de9efa306f3f

📥 Commits

Reviewing files that changed from the base of the PR and between 08b3bd6 and 201f912.

📒 Files selected for processing (3)

• system-variables.md
• tidb-cloud/transaction-concepts.md
• transaction-isolation-levels.md

📝 Walkthrough

Walkthrough

The PR standardizes English transaction isolation-level terminology and updates related Japanese wording in seven documentation files. It changes headings, link text, and descriptions without modifying functionality or public entities.

Changes

Transaction terminology documentation

Layer / File(s)	Summary
Standardize transaction terminology develop/dev-guide-transaction-overview.md, pessimistic-transaction.md, transaction-isolation-levels.md, system-variables.md, tidb-cloud/transaction-concepts.md, tidb-performance-tuning-config.md, tikv-configuration-file.md	Isolation-level names and comparison links now use English terms such as Repeatable Read and Read Committed. Related Japanese wording now uses “表示されます” and “アドバタイズする”.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: 🔵 Low · up to 08b3b

The PR only changes Japanese documentation, but two minor wording issues remain that could confuse readers about snapshot isolation and the displayed isolation-level value. The change is low risk and mergeable with explicit owner follow-up to correct those sentences.

Suggested reviewers: qiancai

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the primary change: keeping SQL transaction isolation-level names in English for Japanese internationalization.
Description check	✅ Passed	The description covers the changes, affected version, AI involvement, and applicable checklist items. It is sufficiently complete for review, although the stated file count differs from the change sum…

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (7 skipped: 7 unsupported.)

Full details: Description check

Explanation

The description covers the changes, affected version, AI involvement, and applicable checklist items. It is sufficiently complete for review, although the stated file count differs from the change summary.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-repeatable-read-term-english

---

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 jackysp 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

[coderabbitai]

Actionable comments posted: 2

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 6b6bf1a0-b63a-4ef7-ad1f-6591e163f5d3

📥 Commits

Reviewing files that changed from the base of the PR and between a349332 and 08b3bd6.

📒 Files selected for processing (7)

• develop/dev-guide-transaction-overview.md
• pessimistic-transaction.md
• system-variables.md
• tidb-cloud/transaction-concepts.md
• tidb-performance-tuning-config.md
• tikv-configuration-file.md
• transaction-isolation-levels.md

Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-08-28 08:21:38.736465979 +0000 UTC m=+835533.907560114: ☑️ agreed by qiancai.