[fix](doc) backport 3 cross-version consistency fixes to 2.1/3.x#3743
Merged
Conversation
Three small fixes flagged by the cross-version consistency audit — current/4.x already had the correction; 2.1/3.x and one EN/3.x file missed the back-port. - upgrade.md (EN 3.x): placeholder `clusterId=<a_new_clusterIP, ...>` should be `clusterID` (the value being assigned to `clusterId=`). All other 7 instances (EN current/4.x/2.1 and all 4 zh) already use `clusterID`. - backup-restore/backup.md (EN 3.x): the Azure example used literal credential strings `"azure.account_name" = "ak"` / `"azure.account_key" = "sk"` (stray copy-paste from the S3 ak/sk credentials block). Replace with the documented placeholder form `<account_name>` / `<account_key>`, matching the `<account_name>.blob.core.windows.net` placeholder on the line above and the zh 3.x and all current/4.x EN+zh versions of the same example. - backup-restore/restore.md (EN+zh 2.1/3.x): the `SHOW SNAPSHOT` result-table border `+-----------------+` (17 dashes) is narrower than the 20-char data column, so the table renders broken. Widen to `+--------------------+` and trim the over-padded header cells to match — same form already used in current/4.x EN and zh. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three small consistency fixes where the correction already landed in current/4.x but never reached 2.1/3.x (or one EN/3.x file).
versioned_docs/version-3.x/admin-manual/cluster-management/upgrade.mdclusterId=<a_new_clusterIP, ...>typo (the value assigned toclusterId=should be an ID, not an IP)clusterIP→clusterID. Matches the other 7 instances (EN current/4.x/2.1 + all 4 zh).versioned_docs/version-3.x/admin-manual/data-admin/backup-restore/backup.md"azure.account_name" = "ak"/"azure.account_key" = "sk"(looks like a stray copy-paste from the S3 ak/sk block)"<account_name>"/"<account_key>", matching the<account_name>.blob.core.windows.netplaceholder on the line above and the zh 3.x and all current/4.x EN+zh copies of the same example.versioned_docs/version-{2.1,3.x}/admin-manual/data-admin/backup-restore/restore.md+ the same zh-CN 2.1/3.x filesSHOW SNAPSHOTresult-table border+-----------------+(17 dashes) is narrower than the 20-char data column → table renders broken+--------------------+and trim the over-padded header cells. Same form already used in current/4.x EN and zh.Test plan