Fix typos for .md files at root directory

[n0vad3v]

What is changed, added or deleted? (Required)

Tons of typo fix for .md files at root directory of this repo.

Some backgrounds on how theses typos are fixed, I've wrote a (Chinese) blog about this: https://nova.moe/fast-typo-fix/ (English version: https://nova.moe/fast-typo-fix-en/) 😇

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)
• v8.1 (TiDB 8.1 versions)
• v8.0 (TiDB 8.0 versions)
• v7.6 (TiDB 7.6 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)
• v5.2 (TiDB 5.2 versions)
• v5.1 (TiDB 5.1 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

[CLAassistant]

All committers have signed the CLA.

[ti-chi-bot]

Welcome @n0vad3v!

It looks like this is your first PR to pingcap/docs 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/docs. 😃

[ti-chi-bot]

Hi @n0vad3v. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[n0vad3v]

@ti-chi-bot

It looks like this is your first PR to pingcap/docs 🎉.

Nope, I've PR merged before: #2058, don't you remember? oh, that was the time you're not here.😏

[qiancai]

Hi @n0vad3v, thanks very much for your contribution. It seems that most typos in this PR have been fixed in https://github.com/pingcap/docs/pull/17381/files already (actually it was inspired by your brilliant blog https://nova.moe/fast-typo-fix/ 👍). Now, I've merged the latest upstream to this PR and there is one typo left in this PR.

[n0vad3v]

@qiancai Wow, nice😇.

[ti-chi-bot]

@nolouch: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[qiancai]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-05-09 06:51:36.432243444 +0000 UTC m=+1117650.189379002: ☑️ agreed by qiancai.

[qiancai]

/approve

[ti-chi-bot]

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

[ti-chi-bot]

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

[ti-chi-bot]

In response to a cherrypick label: cannot checkout release-8.1: error checking out release-8.1: exit status 1. output: error: pathspec 'release-8.1' did not match any file(s) known to git

[ti-chi-bot]

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