i18n(ja): restore dropped particles after code spans in two SQL/TiCDC docs

[yahonda]

What is changed, added or deleted? (Required)

• sql-statements/sql-statement-start-transaction.md: the START TRANSACTION MySQL-compatibility bullet was missing the は particle after every `START TRANSACTION` code span (3 places), producing a run-on, ungrammatical sentence. Restored particles to match the English source's three clauses (TiDB behavior / MySQL behavior / the WITH CONSISTENT SNAPSHOT equivalence). Fixed the same missing-は defect in the adjacent START TRANSACTION READ ONLY bullet.
• ticdc/ticdc-faq.md:
  • "詳細はMySQLの互換性ご覧ください" was missing the を particle before the verb. Restored to "...をご覧ください", and also applied MySQLの互換性 -> MySQLとの互換性 on this line (matching i18n(ja): unify MySQL-compatibility term translation #23437's term unification, to reduce cross-PR churn).
  • Reordered "TiDBのデフォルト値explicit_defaults_for_timestampがMySQLと異なる" (awkward: reads as "TiDB's default value explicit_defaults_for_timestamp") to "TiDBのexplicit_defaults_for_timestampのデフォルト値がMySQLと異なる", matching the English's modifier order: "the default value of explicit_defaults_for_timestamp in TiDB".

Known benign conflict: this PR and #23437 both touch the same physical line in ticdc-faq.md (line-level, not content-level — my version already includes their term change plus additional independent fixes). Standard git line-collision, trivial to resolve on rebase whichever merges second.

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

• v8.5 (LTS)
• v8.1 (LTS)
• v7.5 (LTS)
• v7.1 (LTS)
• v6.5 (LTS)
• v6.1 (LTS)

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Add redirect rules
• Change the framework or the code logic of the repository

[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

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: e00001d0-7e7f-499b-9c05-cc010a4485ca

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 lance6716 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-08-06 05:31:24.388625376 +0000 UTC m=+2678870.424720432: ☑️ agreed by qiancai.