Merge pull request #1048 from petegleeson/master

[Docs] fixes problem with weird highlighting
import-js · Mar 14, 2018 · 1eac942 · 1eac942
2 parents 8c19fb4 + 84b34e8
commit 1eac942
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/rules/extensions.md b/docs/rules/extensions.md
@@ -8,13 +8,13 @@ In order to provide a consistent use of file extensions across your code base, t
 
 This rule either takes one string option, one object option, or a string and an object option. If it is the string `"never"` (the default value), then the rule forbids the use for any extension. If it is the string `"always"`, then the rule enforces the use of extensions for all import statements. If it is the string `"ignorePackages"`, then the rule enforces the use of extensions for all import statements except package imports.
 
-```json
+```
 "import/extensions": [<severity>, "never" | "always" | "ignorePackages"]
 ```
 
 By providing an object you can configure each extension separately.
 
-```json
+```
 "import/extensions": [<severity>, {
   <extension>: "never" | "always" | "ignorePackages"
 }]
@@ -24,7 +24,7 @@ By providing an object you can configure each extension separately.
 
 By providing both a string and an object, the string will set the default setting for all extensions, and the object can be used to set granular overrides for specific extensions.
 
-```json
+```
 "import/extensions": [
   <severity>,
   "never" | "always" | "ignorePackages",