From df58eee1f127f5c24631032792672bfe5120e6a3 Mon Sep 17 00:00:00 2001 From: Artyom Kazak Date: Tue, 9 Sep 2014 21:43:23 +0400 Subject: `code`, not `pre`. --- spec.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.txt b/spec.txt index 82ae0b6..c06f750 100644 --- a/spec.txt +++ b/spec.txt @@ -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: -- cgit v1.2.3