[DOCS] Correct spelling errors in 'large_query_results' part #6900
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
pan3793
approved these changes
Jan 23, 2025
pan3793
pushed a commit
that referenced
this pull request
Jan 23, 2025
…' part ### Why are the changes needed? Correct spelling make the documentation better. ### How was this patch tested? No need. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #6900 from shuyouZZ/new-branch. Closes #6900 27220ab [dongshuyou] [DOCS] Correct spelling errors in 'large_query_results' part Authored-by: dongshuyou <dongshuyou@idea.edu.cn> Signed-off-by: Cheng Pan <chengpan@apache.org> (cherry picked from commit fee4899) Signed-off-by: Cheng Pan <chengpan@apache.org>
Member
|
thanks, merged to master/1.10 |
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.
Why are the changes needed?
Correct spelling make the documentation better.
How was this patch tested?
No need.
Was this patch authored or co-authored using generative AI tooling?
No.