From 9af5171d5068d447e7c2e4427954591619c0b0f2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Go=C5=82e=CC=A8biowski?= Date: Wed, 2 Nov 2016 15:07:43 +0100 Subject: [PATCH] Docs: Fix code-blocks in spaced-comment docs The space-comment docs page had indented code blocks with the JSON type. Because of that they weren't converted to HTML correctly, leaving `json` in plain text on the page. --- docs/rules/spaced-comment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/rules/spaced-comment.md b/docs/rules/spaced-comment.md index 1b4bf5a050a..098457974b5 100644 --- a/docs/rules/spaced-comment.md +++ b/docs/rules/spaced-comment.md @@ -26,7 +26,7 @@ The rule takes two options. * The `"exceptions"` value is an array of string patterns which are considered exceptions to the rule. Please note that exceptions are ignored if the first argument is `"never"`. - ```json + ``` "spaced-comment": ["error", "always", { "exceptions": ["-", "+"] }] ``` @@ -34,7 +34,7 @@ The rule takes two options. such as an additional `/`, used to denote documentation read by doxygen, vsdoc, etc. which must have additional characters. The `"markers"` array will apply regardless of the value of the first argument, e.g. `"always"` or `"never"`. - ```json + ``` "spaced-comment": ["error", "always", { "markers": ["/"] }] ```