Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kramdown usage updates #3569

Merged
merged 3 commits into from
Apr 14, 2020
Merged

Kramdown usage updates #3569

merged 3 commits into from
Apr 14, 2020

Conversation

martinthomson
Copy link
Member

@martinthomson martinthomson commented Apr 8, 2020

Two things:

  • Links are better as [](link) than <link> as the latter puts the link in the text output twice (HTML is fine).

  • Boilerplate is more concise if we let kramdown-rfc2629 add it.

@martinthomson martinthomson added the editorial An issue that does not affect the design of the protocol; does not require consensus. label Apr 8, 2020
@LPardue
Copy link
Member

LPardue commented Apr 8, 2020

❤️ {::boilerplate bcp14}, gonna borrow that one

@@ -85,11 +85,11 @@ subsumed by QUIC, and describes how HTTP/2 extensions can be ported to HTTP/3.

Discussion of this draft takes place on the QUIC working group mailing list
(quic@ietf.org), which is archived at
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should (quic@ietf.org) be changed as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I considered switching to [quic@ietf.org](mailto:quic@ietf.org), yeah. I just have an aversion to mailto: links. But since you asked...

@martinthomson martinthomson merged commit 3514bb3 into master Apr 14, 2020
@martinthomson martinthomson deleted the kramdown-updates branch April 14, 2020 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants