Documentation typo fixes #4500
Merged
Documentation typo fixes #4500
Conversation
This file contains 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
In the last paragraph of the CLI Service docs page the second instance of the word 'need' should be changed to 'needs'.
owanhunte
changed the title
sodatea
approved these changes
Sep 2, 2019
|
Hey @owanhunte, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚 |
sodatea
pushed a commit
that referenced
this pull request
Sep 24, 2019
* Minor typo fix for CLI Service docs page In the last paragraph of the CLI Service docs page the second instance of the word 'need' should be changed to 'needs'. * Typo fix to 'HTML and Static Assets' docs page (cherry picked from commit b20e27a)
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.
The 'CLI Service' and 'HTML and Static Assets' docs pages have some minor typos.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Other information: