Fix: Correct typos, grammar, and missing translations #2318
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
This commit addresses a range of wording and syntax issues across your codebase:
- Corrected typos and grammatical errors in the client-side English locale file (gb.json).
- Addressed typos, inconsistencies, and grammatical issues in the server-side English locale file (en.json).
- Fixed a typo and removed an extraneous key in the server-side Turkish locale file (tr.json).
- Resolved issues in MJML email templates:
- Replaced a 'TBD' placeholder link.
- Generalized hardcoded monitor examples.
- Clarified wording in the password reset email.
- Standardized service naming to 'Checkmate Service'.
- Corrected numerous typos, grammatical errors, and formatting inconsistencies in Markdown documentation files (README.md, CONTRIBUTING.md, PULLREQUESTS.md, and various files in .github/).
- Added missing translations to client-side Russian (ru.json) and Turkish (tr.json) locale files. Common UI terms were translated, and more complex phrases were prefixed with [LANG_NEEDS_TRANSLATION] for future review.
- Added missing translations to the server-side Turkish (tr.json) locale file, following the same approach of translating common terms and prefixing complex ones.
These changes improve the overall quality and clarity of user-facing text and internal documentation. The [LANG_NEEDS_TRANSLATION] prefixes highlight areas where further review by native speakers or those with deep contextual knowledge would be beneficial.
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
There are a few issues here that can be skipped, but I am not sure how to omit them. This is generated by Google's Jules (jules.google.com) |
ajhollid
approved these changes
May 26, 2025
There was a problem hiding this comment.
Changes look OK to me, although @gorkem-bwl you may want to check headings, they have been changed from eg "User guide" to "User Guide"
Yep - I am ok with those, and happy to see it merged. I'll fix them later on. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit addresses a range of wording and syntax issues across the codebase:
These changes improve the overall quality and clarity of user-facing text and internal documentation. The [LANG_NEEDS_TRANSLATION] prefixes highlight areas where further review by native speakers or those with deep contextual knowledge would be beneficial.