cfg: fix wrong pd-ctl cmd

[glkappe]

First-time contributors' checklist

• I've signed Contributor License Agreement that's required for repo owners to accept my contribution.

What is changed, added or deleted? (Required)

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 (in Chinese).

• master (the latest development version)
• 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):

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

[glkappe]

wrong：

correct：

[dveeden]

I think it would be better to use TiUP as it can manage versions, updates, etc. instead of directly calling a binary. But please make sure whatever you do matches the rest of the document

$ tiup ctl:v8.3.0 pd cluster
Starting component ctl: /home/dvaneeden/.tiup/components/ctl/v8.3.0/ctl pd cluster
{
  "id": 7423704173585173569,
  "max_peer_count": 3
}

Did the command change or was it always wrong?

[glkappe]

I think it would be better to use TiUP as it can manage versions, updates, etc. instead of directly calling a binary. But please make sure whatever you do matches the rest of the document

$ tiup ctl:v8.3.0 pd cluster
Starting component ctl: /home/dvaneeden/.tiup/components/ctl/v8.3.0/ctl pd cluster
{
  "id": 7423704173585173569,
  "max_peer_count": 3
}

Did the command change or was it always wrong?

1. Just modified the wrong command
2. All the commands in this document are called binary files. This may be a good opportunity to modify them. . .
3. Maybe I can start a new PR to make changes instead of this one, what do you think? @dveeden

[dveeden]

@glkappe yes perfect!

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-10-10 08:06:29.774569759 +0000 UTC m=+1119745.194782767: ☑️ agreed by hfxsd.

[hfxsd]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hfxsd

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hfxsd]

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]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

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