diff options
| author | Artyom Kazak <yom@artyom.me> | 2014-09-09 21:43:23 +0400 |
|---|---|---|
| committer | Artyom Kazak <yom@artyom.me> | 2014-09-09 21:43:23 +0400 |
| commit | df58eee1f127f5c24631032792672bfe5120e6a3 (patch) | |
| tree | d856474792de75337f0cc880e661200cb1b6b07e | |
| parent | 2cf0750a7a507eded4cf3c9a48fd1f924d0ce538 (diff) | |
`code`, not `pre`.
| -rw-r--r-- | spec.txt | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1058,7 +1058,7 @@ a blank line either before or after. The content of a code fence is treated as literal text, not parsed as inlines. The first word of the info string is typically used to specify the language of the code sample, and rendered in the `class` -attribute of the `pre` tag. However, this spec does not mandate any +attribute of the `code` tag. However, this spec does not mandate any particular treatment of the info string. Here is a simple example with backticks: |