made error documentation headings more standard #367
Merged
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
* `How To Fix` is a good heading, but less common and could be written better * Changed `How To Fix` with `Troubleshooting` which is very standard and well worded
|
Merging to
|
InnocentBug
approved these changes
Sep 27, 2023
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.
Description
made error documentation headings more standard.
How To Fixis a good heading, but less common and could be written betterChanges
How To FixwithTroubleshootingwhich is very standard within technical documentations and and well wordedScreenshots
Before
documentation headings before change
After
documentation headings after change
Known Issues
Notes
Checklist
CONTRIBUTORS.md) in the pull request source branch.