Skip to content

Conversation

@silverwind
Copy link
Contributor

The example added in #3147 was wrongly using a 2-space indent, but markdown requires 4-space for code blocks. This fixes it so this code example is now correctly formatted as a code block.

@silverwindsilverwind added the doc Issues and PRs related to the documentations. label Oct 14, 2015
@thefourtheye
Copy link
Contributor

LGTM

@mscdexmscdex added the tls Issues and PRs related to the tls subsystem. label Oct 14, 2015
silverwind added a commit that referenced this pull request Oct 15, 2015
Markdown requires 4-space indent to correctly format code blocks. This fixes the example so it's correctly presented as code. PR-URL: #3372 Reviewed-By: Sakthipriyan Vairamani <[email protected]>
@silverwind
Copy link
ContributorAuthor

Thanks for review, landed in 503f279.

@silverwindsilverwind deleted the doc-fix-markdown branch October 15, 2015 09:32
@MylesBorins
Copy link
Contributor

Should docfixes also land in LTS?

@jasnell
perhaps add lts-watch-v4x

@jasnell
Copy link
Member

Yes. So long as they're relevant to that branch ;-)

@rvaggrvagg mentioned this pull request Oct 21, 2015
silverwind added a commit that referenced this pull request Oct 26, 2015
Markdown requires 4-space indent to correctly format code blocks. This fixes the example so it's correctly presented as code. PR-URL: #3372 Reviewed-By: Sakthipriyan Vairamani <[email protected]>
@jasnell
Copy link
Member

Landed in v4.x-staging in e223fc7

silverwind added a commit that referenced this pull request Oct 29, 2015
Markdown requires 4-space indent to correctly format code blocks. This fixes the example so it's correctly presented as code. PR-URL: #3372 Reviewed-By: Sakthipriyan Vairamani <[email protected]>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docIssues and PRs related to the documentations.tlsIssues and PRs related to the tls subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@silverwind@thefourtheye@MylesBorins@jasnell@mscdex