Skip to content

Commit

Permalink
Fixed CommonMark test fixture
Browse files Browse the repository at this point in the history
  • Loading branch information
jkphl committed May 16, 2016
1 parent cf7a5f2 commit 68a0316
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 9 deletions.
6 changes: 3 additions & 3 deletions src/Resource/Tests/Fixture/commonmark.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,8 +48,8 @@ Readability, however, is emphasized above all else. A Markdown-formatted
document should be publishable as-is, as plain text, without looking
like it's been marked up with tags or formatting instructions. While
Markdown's syntax has been influenced by several existing text-to-HTML
filters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [4],
[Grutatext] [5], and [EtText] [6] -- the single biggest source of
filters -- including [Setext][1], [atx][2], [Textile][3], [reStructuredText][4],
[Grutatext][5], and [EtText][6] -- the single biggest source of
inspiration for Markdown's syntax is the format of plain text email.

[1]: http://docutils.sourceforge.net/mirror/setext.html
Expand Down Expand Up @@ -209,7 +209,7 @@ work best -- and look better -- when you format them with hard breaks.

<h3 id="header">Headers</h3>

Markdown supports two styles of headers, [Setext] [1] and [atx] [2].
Markdown supports two styles of headers, [Setext][1] and [atx][2].

Setext-style headers are "underlined" using equal signs (for first-level
headers) and dashes (for second-level headers). For example:
Expand Down
6 changes: 3 additions & 3 deletions src/Resource/Tests/Fixture/json-frontmark.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,8 @@ Readability, however, is emphasized above all else. A Markdown-formatted
document should be publishable as-is, as plain text, without looking
like it's been marked up with tags or formatting instructions. While
Markdown's syntax has been influenced by several existing text-to-HTML
filters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [4],
[Grutatext] [5], and [EtText] [6] -- the single biggest source of
filters -- including [Setext][1], [atx][2], [Textile][3], [reStructuredText][4],
[Grutatext][5], and [EtText][6] -- the single biggest source of
inspiration for Markdown's syntax is the format of plain text email.

[1]: http://docutils.sourceforge.net/mirror/setext.html
Expand Down Expand Up @@ -213,7 +213,7 @@ work best -- and look better -- when you format them with hard breaks.

<h3 id="header">Headers</h3>

Markdown supports two styles of headers, [Setext] [1] and [atx] [2].
Markdown supports two styles of headers, [Setext][1] and [atx][2].

Setext-style headers are "underlined" using equal signs (for first-level
headers) and dashes (for second-level headers). For example:
Expand Down
6 changes: 3 additions & 3 deletions src/Resource/Tests/Fixture/yaml-frontmark.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,8 +52,8 @@ Readability, however, is emphasized above all else. A Markdown-formatted
document should be publishable as-is, as plain text, without looking
like it's been marked up with tags or formatting instructions. While
Markdown's syntax has been influenced by several existing text-to-HTML
filters -- including [Setext] [1], [atx] [2], [Textile] [3], [reStructuredText] [4],
[Grutatext] [5], and [EtText] [6] -- the single biggest source of
filters -- including [Setext][1], [atx][2], [Textile][3], [reStructuredText][4],
[Grutatext][5], and [EtText][6] -- the single biggest source of
inspiration for Markdown's syntax is the format of plain text email.

[1]: http://docutils.sourceforge.net/mirror/setext.html
Expand Down Expand Up @@ -213,7 +213,7 @@ work best -- and look better -- when you format them with hard breaks.

<h3 id="header">Headers</h3>

Markdown supports two styles of headers, [Setext] [1] and [atx] [2].
Markdown supports two styles of headers, [Setext][1] and [atx][2].

Setext-style headers are "underlined" using equal signs (for first-level
headers) and dashes (for second-level headers). For example:
Expand Down

0 comments on commit 68a0316

Please sign in to comment.