docs: fix grammar errors in English README#149
Open
Avicennasis wants to merge 1 commit into
Open
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
1 participant
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.
Five small grammar fixes in the English README; no semantic changes:
significantly improvements→significant improvements(adjective modifies noun)Significant better performances→Significantly better performance(adverb modifies adjective; "performance" is uncountable here)More general→More generally(adverb modifying the clause)role-play scenario→role-play scenarios(matches plural "scenarios" earlier in the same sentence)Claude Code、Cline、Roo Code(consistent with the rest of the English README)in both vLLM and SGLang method→methods(plural needed with "both")[link]. for the detailed template.→[link] for the detailed template.(stray period breaking the sentence)