Skip to content

tiup: fix typos, flag names, Markdown, and wrong links in TiUP reference docs - #24486

Merged
ti-chi-bot[bot] merged 5 commits into
pingcap:masterfrom
yahonda:tiup-fix-typos-flags-and-links
Oct 27, 2026
Merged

ti-chi-bot[bot] merged 5 commits into
pingcap:masterfrom
yahonda:tiup-fix-typos-flags-and-links

Conversation

@yahonda

@yahonda yahonda commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

What is changed, added, or deleted? (Required)

Fix typos, flag names, Markdown, and wrong links in the TiUP reference docs. These errors were found while reviewing the English docs for issues that affect the Japanese translation. Each fix is shown below; the same wrong text was also searched for in the rest of the docs.

File Before After
tiup-component-management.md The --all and --verbose list items have no space after -, so the list does not render Add the space
tiup-component-management.md "use the tiup install command to query the component list" (Install components section) "…to install components"
tiup-dm-topology-reference.md log_dir: "the data directory" "the log directory"
tiup-dm-topology-reference.md worker_servers: "the master node of the DM component" "the worker node"
tiup-command-mirror-publish.md tiup list -all tiup list --all
tiup-component-cluster-audit-cleanup.md "tiup clustercommand" "tiup cluster command"
tiup-component-cluster-check.md -enable-cpu, -enable-mem, -enable-disk, -cluster --enable-cpu, --enable-mem, --enable-disk, --cluster (as in the headings)
tiup-component-cluster-check.md The code fence lines in a blockquote have no space after > Add the space
tiup-component-cluster-clean.md "at lease one" "at least one"
tiup-component-cluster-display.md "all nodes are checked by default", "are checked" (copied from the check page) "displayed"
tiup-component-cluster-import.md . /ansible.cfg, -dir ./ansible.cfg, --dir
tiup-component-cluster-meta-backup.md (summary) "Use tiup dm list to check the cluster name" tiup cluster list
tiup-component-cluster-reload.md, tiup-component-cluster-upgrade.md -transfer-timeout --transfer-timeout
tiup-component-cluster-scale-out.md cluster list links to tiup-component-dm-list.md; the topology file links to tiup-dm-topology-reference.md tiup-component-cluster-list.md; tiup-cluster-topology-reference.md
tiup-component-dm-restart.md cluster list links to tiup-component-cluster-list.md tiup-component-dm-list.md (as in the other tiup dm pages)
tiup-component-dm-patch.md, tiup-component-dm-restart.md "[tiup dm display](…)" (the link is inside a code span and does not render) "tiup dm display"
tiup-component-dm-prune.md "scale in the cluster(/tiup/tiup-component-dm-scale-in.md)" "scale in the cluster"
tiup-component-dm-edit-config.md "topology file. of the specified cluster" "topology file of the specified cluster"
tiup-command-mirror-modify.md (summary) <component>[version] <component>[:version] (as in the syntax)
tiup-cluster-topology-reference.md ng_port: Continuous Profiling (the Manual Profiling page) Continuous Profiling

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)?

  • Related code change PR links (if applicable):
  • 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

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Corrected TiUP mirror and cluster command syntax, option names, defaults, and examples.
    • Clarified cluster display behavior and guidance for importing, scaling, upgrading, reloading, and editing configurations.
    • Fixed command references and Markdown links across cluster and DM documentation.
    • Clarified component installation behavior, version syntax, and list options.
    • Corrected topology descriptions for log directories, DM-worker deployment, and Continuous Profiling.

…nce docs

- Fix single-dash flags that should be double-dash: --all, --enable-cpu,
  --enable-mem, --enable-disk, --cluster, --dir, and --transfer-timeout.
- Fix list markers and code fences in blockquotes that did not render.
- Fix wrong descriptions: tiup install installs components, log_dir is
  the log directory, worker_servers deploys worker nodes, and display
  displays nodes.
- Fix wrong links and link formatting: cluster list, the cluster topology
  file, tiup dm display, and the scale-in link.
- Fix typos: "at lease", ". /ansible.cfg", a missing space, a stray
  period, tiup dm list in a cluster page summary, and <component>[:version].

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ti-chi-bot

ti-chi-bot Bot commented Oct 19, 2026

Copy link
Copy Markdown

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 ti-chi-bot Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 19, 2026
@coderabbitai

coderabbitai Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: pingcap/docs
  • Branch: master
  • File: .coderabbit.yaml
  • Commit: 3ba897a
  • Layers: Repository YAML
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: d28b201a-49ea-4b4d-82ad-b23ceee842b5
Commits

Reviewing files that changed from the base of the PR and between be0179a and 32509b1.

Files selected for processing: 1
  • tiup/tiup-component-dm-restart.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.

Walkthrough

The change corrects command syntax, option references, Markdown links, and descriptions across TiUP command, cluster, and DM documentation.

Changes: TiUP and DM documentation

Layer / File(s) Summary
General TiUP command references
tiup/tiup-command-mirror-*.md, tiup/tiup-component-management.md
Corrected mirror command syntax and the hidden-component listing command. Updated component-list formatting and the tiup install description.
Cluster command references
tiup/tiup-component-cluster-*.md, tiup/tiup-cluster-topology-reference.md
Corrected option syntax, command references, and descriptions. Updated links to cluster documentation.
DM command and topology references
tiup/tiup-component-dm-*.md, tiup/tiup-dm-topology-reference.md
Corrected DM command links and topology-file wording. Updated the log_dir and worker_servers descriptions.

Priority: Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Suggested reviewers: qiancai

Merge Risk: Minimal · previous review 32509

The documentation corrections present no identified merge-blocking risk.

Architecture risk: Low · up to d5895

The change affects 1 system.

Changed systems: tiup

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — tiup (service) was modified; 17 changed files map to changed impact.

Before / after behavior

  • observed — Modified behavior in tiup/tiup-command-mirror-modify.md: Corrected the documented command syntax from <component>[version] to <component>[:version].
  • observed — Modified behavior in tiup/tiup-command-mirror-publish.md: Updated the documented command for listing hidden components from tiup list -all to tiup list --all.
  • observed — Modified behavior in tiup/tiup-component-cluster-audit-cleanup.md: Corrected the command description’s spacing from clustercommand to cluster command.
  • observed — Modified behavior in tiup/tiup-component-cluster-check.md: Updated the CPU, memory, and related option documentation to use the double-hyphen forms --enable-cpu and --enable-mem instead of single-hyphen forms.
Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly summarizes the main changes: typo, flag name, Markdown, and link corrections in TiUP reference documentation.
Description check Passed The description includes the required change summary, affected versions, related-link section, AI involvement, and change-category checklist. The first-time contributor checklist is omitted, which is …
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within survi…
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 includes the required change summary, affected versions, related-link section, AI involvement, and change-category checklist. The first-time contributor checklist is omitted, which is allowed when the author is not a first-time contributor.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

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

@ti-chi-bot ti-chi-bot Bot added missing-translation-status This PR does not have translation status info. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 19, 2026
@yahonda
yahonda marked this pull request as ready for review October 20, 2026 00:07
@ti-chi-bot ti-chi-bot Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 20, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🔇 Additional comments: 12
tiup/tiup-command-mirror-publish.md: 1

69-69: LGTM!

tiup/tiup-component-management.md: 1

33-34: LGTM!

tiup/tiup-component-cluster-audit-cleanup.md: 1

8-8: LGTM!

tiup/tiup-component-cluster-check.md: 1

111-111: LGTM!

Also applies to: 119-119, 131-131, 165-167, 235-235

tiup/tiup-component-cluster-clean.md: 1

29-29: LGTM!

tiup/tiup-component-cluster-display.md: 1

30-30: LGTM!

Also applies to: 34-34

tiup/tiup-component-cluster-import.md: 1

41-41: LGTM!

Also applies to: 53-53

tiup/tiup-component-cluster-meta-backup.md: 1

3-3: LGTM!

tiup/tiup-component-cluster-reload.md: 1

28-28: LGTM!

tiup/tiup-component-cluster-scale-out.md: 1

18-20: LGTM!

tiup/tiup-component-cluster-upgrade.md: 1

33-33: LGTM!

tiup/tiup-component-management.md-54-54: 1

54-54: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

⚠️ Unverified finding
Verification ran but could not confirm this finding. It is shown for review, not as a verified issue.

Use direct wording for the install command.

The changed sentence contains This usage of this command is as follows, which is ungrammatical. Replace the changed line with:

You can use the `tiup install` command to install components as follows:

ℹ️ Review info
⚙️ Run configuration
  • Configuration used: Repository: pingcap/docs/.coderabbit.yaml
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 32df9fd6-2e41-4612-986c-8551886dad95
📥 Commits

Reviewing files that changed from the base of the PR and between 3ba897a and d5895da.

📒 Files selected for processing: 17
  • tiup/tiup-command-mirror-modify.md
  • tiup/tiup-command-mirror-publish.md
  • tiup/tiup-component-cluster-audit-cleanup.md
  • tiup/tiup-component-cluster-check.md
  • tiup/tiup-component-cluster-clean.md
  • tiup/tiup-component-cluster-display.md
  • tiup/tiup-component-cluster-import.md
  • tiup/tiup-component-cluster-meta-backup.md
  • tiup/tiup-component-cluster-reload.md
  • tiup/tiup-component-cluster-scale-out.md
  • tiup/tiup-component-cluster-upgrade.md
  • tiup/tiup-component-dm-edit-config.md
  • tiup/tiup-component-dm-patch.md
  • tiup/tiup-component-dm-prune.md
  • tiup/tiup-component-dm-restart.md
  • tiup/tiup-component-management.md
  • tiup/tiup-dm-topology-reference.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

Comment thread tiup/tiup-command-mirror-modify.md
Comment thread tiup/tiup-component-management.md Outdated
yahonda and others added 2 commits October 20, 2026 09:16
Use `<component>[:version]`, as the rest of the page does
(`tiup [flags] <component>[:version]`, `tiup uninstall [component][:version]`).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@qiancai qiancai added the translation/doing This PR's assignee is translating this PR. label Oct 27, 2026
@ti-chi-bot ti-chi-bot Bot removed the missing-translation-status This PR does not have translation status info. label Oct 27, 2026
@ti-chi-bot ti-chi-bot Bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Oct 27, 2026
@ti-chi-bot

ti-chi-bot Bot commented Oct 27, 2026

Copy link
Copy Markdown

[LGTM Timeline notifier]

Timeline:

  • 2026-10-27 13:56:56.953568718 +0000 UTC m=+469754.445280977: ☑️ agreed by qiancai.

@qiancai qiancai added area/tiup Indicates that the Issue or PR belongs to the area of the TiUP tool. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. labels Oct 27, 2026
@qiancai qiancai self-assigned this Oct 27, 2026
@qiancai

qiancai commented Oct 27, 2026

Copy link
Copy Markdown
Collaborator

/approve

@qiancai qiancai added the lgtm label Oct 27, 2026
@ti-chi-bot

ti-chi-bot Bot commented Oct 27, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

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 ti-chi-bot Bot added the approved label Oct 27, 2026
@qiancai qiancai added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 27, 2026
Comment thread tiup/tiup-component-dm-restart.md Outdated
@qiancai qiancai removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 27, 2026
@ti-chi-bot
ti-chi-bot Bot merged commit 75d9a76 into pingcap:master Oct 27, 2026
12 checks passed
@ti-chi-bot

Copy link
Copy Markdown
Member

In response to a cherrypick label: new pull request created to branch release-8.5: #24563.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved area/tiup Indicates that the Issue or PR belongs to the area of the TiUP tool. lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. translation/doing This PR's assignee is translating this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants