docs: rename "Usage Scenarios" to "How-to guides" #5799
Merged
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
Co-Authored-By: Hage Yaapa <captain@hacksparrow.com> Signed-off-by: Miroslav Bajtoš <mbajtoss@gmail.com>
bajtos
added
developer-experience
hacksparrow
approved these changes
Jun 22, 2020
achrinza
approved these changes
Jun 22, 2020
3 tasks
dhmlau
approved these changes
Jun 22, 2020
raymondfeng
approved these changes
Jun 22, 2020
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.
To further align our sidebar with the four-quadrant documentation system (see #5549 and #5718), I am proposing to rename "Usage Scenarios" to "How-to guides".
This pull request is extracted from #5768.
Checklist
👉 Read and sign the CLA (Contributor License Agreement) 👈
npm testpasses on your machinepackages/cliwere updatedexamples/*were updated👉 Check out how to submit a PR 👈