chore: Minor typographical fixes#1183
Merged
rishabh3112 merged 2 commits intowebpack:nextfrom Jan 23, 2020
Merged
Conversation
|
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
rishabh3112
requested changes
Jan 22, 2020
Member
rishabh3112
left a comment
rishabh3112
left a comment
There was a problem hiding this comment.
Thanks for PR!
There is a similar typographical mistake in commands.js file.
Please correct it too 😅
|
@jamesgeorge007 Thanks for your update. I labeled the Pull Request so reviewers will review it again. @rishabh3112 Please review the new changes. |
webpack-bot
added
PR: review-outdated
and removed
PR: reviewed-changes-requested
labels
ematipico
approved these changes
Jan 23, 2020
jamesgeorge007
changed the title
rishabh3112
approved these changes
Jan 23, 2020
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
5 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.
What kind of change does this PR introduce?
Did you add tests for your changes?
N/A
If relevant, did you update the documentation?
Nope
Summary
Follow up of #1141
Does this PR introduce a breaking change?
Nope
Other information
N/A