i18n(ja): restore UI labels in 11 files skipped from the 2-word batch

[yahonda]

What is changed, added or deleted? (Required)

These 11 files were skipped by the 2-word UI-labels batch (#23535) because their EN/JA bold-span counts didn't match, making the mechanical positional-pairing script unsafe. Reviewed each 1:1 against EN by hand, applying the same verify-via-dbaas-ui-or-third-party-knowledge method established in the earlier batches.

Beyond simple label restoration, this surfaced several genuine content defects predating this session's work:

• tidb-cloud-encrypt-cmek-aws.md / tidb-cloud-encrypt-cmek-azure.md: an entire console step (locate project + click the project-settings icon) was missing from the JA translation, collapsing EN's 9-step (AWS) and 11/7-step (Azure) sequences by one step each. Reconstructed in full against EN.
• Several files had stale "use the combo box to switch cluster/project" navigation instructions describing an older console flow, while EN has since been updated to the current "My TiDB page > Project view tab > project-settings icon" flow. Rewritten to match EN's current instructions.
• tidb-cloud-glossary.md: a hallucinated MT substitution (a fabricated My TiDB link replacing EN's actual "List all accessible projects" API endpoint reference), a false-friend mistranslation (終点 → エンドポイント for "endpoint"), and 2 particle-trapped-in-bold defects.
• connected-care-overview.md: corrupted HTML <strong> tags baked into a heading anchor slug, inconsistent "Connected:" prefix translation across sibling bullets, and a dropped particle.
• Various straddling-bracket defects, split-mid-word defects, and garbled/reordered value lists across the private-link and Kafka setup guides.

configure-ip-access-list.md needed no changes — its bold-count mismatch is a single JA-only emphasis span with no EN counterpart, not a defect.

Deliberately left as-is (flagged for future follow-up, out of this task's scope): a content-accuracy issue in connected-care-overview.md (退職日 mistranslation), a term-consistency issue in tidb-cloud-glossary.md (地域/リージョン, リサイクルボックス/ごみ箱), recurring stale combo-box navigation text in set-up-vpc-peering-connections.md and use-tidb-cloud-with-ai-tools.md, and a missing EN paragraph + 4-step list in troubleshoot-import-access-denied-error.md (about obtaining the TiDB Cloud Account ID/External ID) that JA replaces with a stale literal-example-ID version instead of EN's current placeholder convention.

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

• master (the latest development version)
• v8.5 (TiDB 8.5 versions)
• v8.4 (TiDB 8.4 versions)
• v8.3 (TiDB 8.3 versions)
• v8.2 (TiDB 8.2 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)
• v5.4 (TiDB 5.4 versions)
• v5.3 (TiDB 5.3 versions)

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

• This PR is translated from:
• Other reference link(s): i18n(ja): restore 2-word TiDB Cloud UI labels to English #23535

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

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

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: 7cd43eba-717a-44ad-9dec-cb1d841c750d

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]

[LGTM Timeline notifier]

Timeline:

• 2026-08-17 10:00:34.024242622 +0000 UTC m=+3645420.060337677: ☑️ agreed by qiancai.