[docs] improve English translation and technical terms for MySQL #3928
+1
−1
Conversation
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.
What's changed?
Refined the English translation in the MySQL monitoring template (
app-mysql.yml).Corrected Technical Terms: Changed "things" to "Transactions" (事务) to match standard database terminology.
Improved Clarity: Updated the
helpdocumentation and metric descriptions (e.g., "Queries Per Second", "Transaction Commits") to be more professional and grammatically correct.Consistency:Ensured
en-USfields align with the technical intent of thezh-CNsource.This contribution is part of the community translation task #1759.
Checklist
[x] I have read the Contributing Guide
[x] I have written the necessary doc or comment. (Since you updated the documentation itself).
[ ] I have added the necessary unit tests... (You can leave this blank, as documentation/translation usually doesn't need new tests).