fix double backticks in forbidden_header_name guide #9953
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
Preview URLsFlawsNone! 🎉 External URLsURL: No new external URLs |
ddbeck
approved these changes
Oct 20, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
The forbidden header name page has an issue in the 2nd paragraph with double backticks.
Sec-is rendered as `Sec-`.Motivation
Make it look clean (?), and uniform with the way it's displayed in the following paragraph.
Supporting details
It looks like #9630 introduced this, which apparently converted HTML files to markdown, but it seems that the issue existed before as: `
<code>Sec-</code>`. I couldn't find when this was actually introduced.Related issues
Metadata