boluor opened a new pull request, #3743:
URL: https://github.com/apache/doris-website/pull/3743

   ## 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).
   
   | File | Issue | Fix |
   | --- | --- | --- |
   | `versioned_docs/version-3.x/admin-manual/cluster-management/upgrade.md` | 
placeholder `clusterId=<a_new_clusterIP, ...>` typo (the value assigned to 
`clusterId=` 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 example used literal `"azure.account_name" = "ak"` / `"azure.account_key" 
= "sk"` (looks like a stray copy-paste from the S3 ak/sk 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 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 files | `SHOW SNAPSHOT` result-table border 
`+-----------------+` (17 dashes) is narrower than the 20-char data column → 
table renders broken | widen the rule line to `+--------------------+` and trim 
the over-padded header cells. Same form already used in current/4.x EN and zh. |
   
   ## Test plan
   
   - [x] Verified against the current/4.x EN+zh versions of the same pages 
(which already carry the correct form).
   - [x] Dead-link check passes.
   - [ ] CI build.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to