i18n(ja): unify OLTP katakana compound spacing to no-separator form

[yahonda]

What is changed, added or deleted? (Required)

オンライン トランザクション処理 (half-width space) and オンライン・トランザクション処理 (middle-dot) were both used inconsistently for the OLTP term across the corpus, instead of the no-separator compound form オンライントランザクション処理 already used elsewhere (10+ occurrences) and matching the standing katakana-compound-spacing convention (no separator between katakana words in a compound).

Neither the half-width space nor the middle-dot has any counterpart in the EN source, which simply uses normal English word spacing ("Online Transaction Processing") — both are JA-only artifacts with no basis in the source text.

Files changed (17):

• benchmark/benchmark-sysbench-v4-vs-v3.md, benchmark/v4.0-performance-benchmarking-with-tpcc.md
• quick-start-with-htap.md, develop/dev-guide-create-table.md, explore-htap.md (2 occ), glossary.md
• tidb-cloud/tidb-cloud-faq.md
• tidb-cloud/v6.5-performance-benchmarking-with-sysbench.md, v6.5-...-tpcc.md, v7.1-...-sysbench.md, v7.1-...-tpcc.md, v7.5-...-sysbench.md, v7.5-...-tpcc.md, v8.1-...-sysbench.md, v8.1-...-tpcc.md, v8.5-...-sysbench.md, v8.5-...-tpcc.md

4 other occurrences of this same pattern (develop/dev-guide-connection-parameters.md, develop/java-app-best-practices.md, tidb-cloud/releases/release-notes-2025.md, tidb-cloud/serverless-high-availability.md) are already fixed in the still-open PR #23668 and are not duplicated here.

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 terminology for online transaction processing (OLTP) across benchmark reports, guides, FAQs, and glossary content.
  • Corrected spacing and punctuation to improve consistency and readability.
  • No functional or technical behavior changes.

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

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Team

Run ID: 9fce0920-e367-4c09-9d3f-0373eb857eca

📥 Commits

Reviewing files that changed from the base of the PR and between adfeb1f and 383b63e.

📒 Files selected for processing (17)

• benchmark/benchmark-sysbench-v4-vs-v3.md
• benchmark/v4.0-performance-benchmarking-with-tpcc.md
• develop/dev-guide-create-table.md
• explore-htap.md
• glossary.md
• quick-start-with-htap.md
• tidb-cloud/tidb-cloud-faq.md
• tidb-cloud/v6.5-performance-benchmarking-with-sysbench.md
• tidb-cloud/v6.5-performance-benchmarking-with-tpcc.md
• tidb-cloud/v7.1-performance-benchmarking-with-sysbench.md
• tidb-cloud/v7.1-performance-benchmarking-with-tpcc.md
• tidb-cloud/v7.5-performance-benchmarking-with-sysbench.md
• tidb-cloud/v7.5-performance-benchmarking-with-tpcc.md
• tidb-cloud/v8.1-performance-benchmarking-with-sysbench.md
• tidb-cloud/v8.1-performance-benchmarking-with-tpcc.md
• tidb-cloud/v8.5-performance-benchmarking-with-sysbench.md
• tidb-cloud/v8.5-performance-benchmarking-with-tpcc.md

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

---

📝 Walkthrough

Walkthrough

This documentation-only update standardizes Japanese OLTP terminology across HTAP references, the glossary, the FAQ, and benchmark reports by removing spaces and middle dots.

Changes

OLTP terminology normalization

Layer / File(s)	Summary
Reference terminology updates develop/dev-guide-create-table.md, explore-htap.md, glossary.md, quick-start-with-htap.md, tidb-cloud/tidb-cloud-faq.md	Japanese OLTP and HTAP descriptions use the normalized wording without spaces or middle dots.
Benchmark terminology updates benchmark/*.md, tidb-cloud/*performance-benchmarking*.md	Japanese Sysbench and TPC-C benchmark reports use the normalized OLTP wording.

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

Merge Risk: ⚪ Minimal · up to 383b6

This PR standardizes Japanese OLTP terminology without changing product behavior or runtime configuration, so no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: qiancai

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the Japanese internationalization change and the standardization of OLTP katakana compound spacing. It is concise and directly related to the main changes.
Description check	✅ Passed	The description explains the change, affected files, rationale, target documentation version, and AI involvement. The related-link fields are empty, but they are non-critical and the description is ot…
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.

Full details: Description check

Explanation

The description explains the change, affected files, rationale, target documentation version, and AI involvement. The related-link fields are empty, but they are non-critical and the description is otherwise complete.

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. (17 skipped: 17 unsupported.)

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-09-02 03:47:55.802426668 +0000 UTC m=+1251110.973520781: ☑️ agreed by qiancai.