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

Fix the backquote escape problem #56

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions _posts/2016-01-01-Markdown Reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Headers use 1-6 hash (`#`) characters at the start of the line, corresponding to
###### This is an H6
```

In Typora, input ‘#’s followed by title content, and press `Return` key will create a header. Or type ⌘1 to ⌘6 as a shortcut.
In Typora, input `#` followed by title content, and press `Return` key will create a header. Or type ⌘1 to ⌘6 as a shortcut.

### Blockquotes

Expand All @@ -52,7 +52,7 @@ Markdown uses email-style > characters for block quoting. They are presented as:
> This is another blockquote with one paragraph. There is three empty line to seperate two blockquote.
```

In Typora, typing ‘>’ followed by your quote contents will generate a quote block. Typora will insert a proper ‘>’ or line break for you. Nested block quotes (a block quote inside another block quote) by adding additional levels of ‘>’.
In Typora, typing `>` followed by your quote contents will generate a quote block. Typora will insert a proper `>` or line break for you. Nested block quotes (a block quote inside another block quote) by adding additional levels of `>`.

### Lists

Expand Down Expand Up @@ -92,7 +92,7 @@ You can change the complete/incomplete state by clicking on the checkbox before

Typora only supports fences in GitHub Flavored Markdown, not the original code block style.

Using fences is easy: type \`\`\` and press `return`. Add an optional language identifier after \`\`\` and Typora runs it through syntax highlighting:
Using fences is easy: type ` ``` ` and press `Return`. Add an optional language identifier after ` ``` ` and Typora runs it through syntax highlighting:

``` markdown
Here's an example:
Expand Down Expand Up @@ -192,7 +192,7 @@ You can create footnotes like this[^fn1] and this[^fn2].
[^fn2]: Here is the *text* of the second **footnote**.
```

Hover over the fn1 or 'fn2' superscript to see content of the footnote. You can use whatever unique identified you like as the footnote marker (e.g. "fn1").
Hover over the `fn1` or `fn2` superscript to see content of the footnote. You can use whatever unique identified you like as the footnote marker (e.g. "fn1").

Hover over the footnote superscripts to see content of the footnote.

Expand Down