Fix typos and improve clarity in release notes#845
Open
sky-coderay wants to merge 3 commits intoTrueFiEng:masterfrom
Open
Fix typos and improve clarity in release notes#845sky-coderay wants to merge 3 commits intoTrueFiEng:masterfrom
sky-coderay wants to merge 3 commits intoTrueFiEng:masterfrom
Conversation
|
Author
|
@velvet-shark @alcuadrado @marekkirejczyk Hi! Just a reminder about my PR . If everything looks good, it would be great if you could merge it. Thanks! 😊 |
Contributor
|
FYI, I don't have any rights to this repo anymore. CC @JustynaBroniszewska |
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
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.
Files:
docs/release-notes/2.0.0.md
docs/release-notes/2.0.8.md
docs/release-notes/2.1.0.md
Corrected words:
reease → release
complied → compiled
localy → locally
extenstions → extensions
officialy → officially
Form → From
compiliation → compilation
Why this is important:
Professionalism: Correcting spelling and grammatical errors helps maintain a high level of documentation, which is especially important in open-source projects.
Accuracy: Using correct terms, such as "compiled" instead of "complied", helps avoid confusion and misunderstandings among developers.
Readability: Proper spelling and grammar make documentation more understandable and accessible to users.