[AMORO-3616][Improvement] Correct the spelling errors in doc of Managing Optimizers page#3618
Merged
xxubai merged 1 commit intoapache:masterfrom Jun 13, 2025
Merged
Conversation
github-actions
bot
added
the
type:docs
klion26
approved these changes
Jun 13, 2025
Member
klion26
left a comment
klion26
left a comment
There was a problem hiding this comment.
@Akeron-Zhu LGTM, thanks for the contribution.
Jzjsnow
pushed a commit
to Jzjsnow/amoro
that referenced
this pull request
Aug 20, 2025
…ing Optimizers page (apache#3618) Fix spelling error in doc of Managing Optimizers page Co-authored-by: ZKK <akeron@qq.com> (cherry picked from commit 7197ec6)
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
3 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?
Close #3616
Brief change log
Fix the spelling errors in doc of Managing Optimizers page.
How was this patch tested?
Add some test cases that check the changes thoroughly including negative and positive cases if possible
Add screenshots for manual tests if appropriate
Run test locally before making a pull request
Documentation