FAQ formatting changes #1842
Merged
FAQ formatting changes #1842
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
- remove usage of ‎ - don't skip headers (##### instead of ###)
ekzyis
force-pushed
the
faq-formatting
branch
from
492a287 to
e3df527
Compare
Merged
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.
Intermediate PR for formatting changes included in #1800:
That helps with viewing the FAQ in the local build since links will now keep you on the same page instead of redirecting you to a prod link.
‎and don't skip headers (#####instead of###)It makes the FAQ page formatting feel inconsistent with the rest of the site