Fixed JSON in fielddata docs

docs/reference/index-modules/fielddata.asciidoc

@@ -73,10 +73,10 @@ data format.
 [source,js]
 --------------------------------------------------
 {
-    tag: {
-        type:      "string",
-        fielddata: {
-            format: "fst"
+    "tag": {
+        "type":      "string",
+        "fielddata": {
+            "format": "fst"
         }
     }
 }
@@ -173,10 +173,10 @@ It is possible to force field data to be loaded and cached eagerly through the
 [source,js]
 --------------------------------------------------
 {
-    category: {
-        type:      "string",
-        fielddata: {
-            loading: "eager"
+    "category": {
+        "type":      "string",
+        "fielddata": {
+            "loading": "eager"
         }
     }
 }
@@ -187,10 +187,10 @@ Global ordinals can also be eagerly loaded:
 [source,js]
 --------------------------------------------------
 {
-    category: {
-        type:      "string",
-        fielddata: {
-            loading: "eager_global_ordinals"
+    "category": {
+        "type":      "string",
+        "fielddata": {
+            "loading": "eager_global_ordinals"
         }
     }
 }
@@ -212,10 +212,10 @@ will return an error.
 [source,js]
 --------------------------------------------------
 {
-    text: {
-        type:      "string",
-        fielddata: {
-            format: "disabled"
+    "text": {
+        "type":      "string",
+        "fielddata": {
+            "format": "disabled"
         }
     }
 }
@@ -253,14 +253,14 @@ number of docs that the segment should contain with `min_segment_size`:
 [source,js]
 --------------------------------------------------
 {
-    tag: {
-        type:      "string",
-        fielddata: {
-            filter: {
-                frequency: {
-                    min:              0.001,
-                    max:              0.1,
-                    min_segment_size: 500
+    "tag": {
+        "type":      "string",
+        "fielddata": {
+            "filter": {
+                "frequency": {
+                    "min":              0.001,
+                    "max":              0.1,
+                    "min_segment_size": 500
                 }
             }
         }
@@ -280,13 +280,13 @@ expression which matches terms beginning with `#`:
 [source,js]
 --------------------------------------------------
 {
-    tweet: {
-        type:      "string",
-        analyzer:  "whitespace"
-        fielddata: {
-            filter: {
-                regex: {
-                    pattern: "^#.*"
+    "tweet": {
+        "type":      "string",
+        "analyzer":  "whitespace"
+        "fielddata": {
+            "filter": {
+                "regex": {
+                    "pattern": "^#.*"
                 }
             }
         }
@@ -302,18 +302,18 @@ The `frequency` and `regex` filters can be combined:
 [source,js]
 --------------------------------------------------
 {
-    tweet: {
-        type:      "string",
-        analyzer:  "whitespace"
-        fielddata: {
-            filter: {
-                regex: {
-                    pattern:          "^#.*",
+    "tweet": {
+        "type":      "string",
+        "analyzer":  "whitespace"
+        "fielddata": {
+            "filter": {
+                "regex": {
+                    "pattern":          "^#.*",
                 },
-                frequency: {
-                    min:              0.001,
-                    max:              0.1,
-                    min_segment_size: 500
+                "frequency": {
+                    "min":              0.001,
+                    "max":              0.1,
+                    "min_segment_size": 500
                 }
             }
         }