docs: enhance grammar and consistency in README #2113
Merged
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
|
@Gayathri-K-Binoy Thanks for the PR! Next time don't use AI to generate the description as we're more likely to ignore/close them when they are. For simple PRs like this one a couple words are totally fine. |
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 PR refines the grammar in a key feature bullet point by changing “scans and enhance” to “scan and enhance.”
Though subtle, this correction improves parallel structure and reflects a more polished, professional tone in the documentation. Clear and precise language in the feature list is especially important, as it's one of the first sections new users and contributors read when evaluating the project.
Consistent grammar reinforces the project’s attention to detail and commitment to quality.