fix langtool issues
@@ -21,9 +21,9 @@ you may want to follow the hot-fix release process instead of the usual release
It's mostly similar to the usual release flow, but you need to change the target branch of release pull request.
1. Create a fix and merge it into master.
-2. Create a release branch (`release-v{major}.{minor}`) based on the latest semver release `v{major}.{minor}.{patch}` if there are no exisisting release branch.
- - You need a write permission to reviewdog repository to push the release branch.
-3. Create **an another release request branch** (any name is fine) and update [CHANGELOG.md](../CHANGELOG.md).
+2. Create a release branch (`release-v{major}.{minor}`) based on the latest semver release `v{major}.{minor}.{patch}` if there is no exisisting release branch.
+ - You need write permission to reviewdog repository to push the release branch.
+3. Create **another release request branch** (any name is fine) and update [CHANGELOG.md](../CHANGELOG.md).
4. Create a pull request from the release request branch to **the release branch** (`release-v{major}.{minor}`) instead of master.
5. Attach `bump:patch` label.
6. [The release workflow](./workflows/release.yml) automatically tag a
