Merge pull request #253096 from alexbuckgit/alexbuckgit/docutune-autopr-20230927-234151-7893995-ignore-build

[BULK] - DocuTune - Fix code formatting issues (part 1)

Author: Jill Grant

articles/active-directory/app-provisioning/skip-out-of-scope-deletions.md

@@ -59,10 +59,10 @@ Copy the Response into a text file. It looks like the JSON text shown, with valu
 Here's the JSON block to add to the mapping. 
 
 ```json
-        {
-            "key": "SkipOutOfScopeDeletions",
-            "value": "True"
-        }
+{
+  "key": "SkipOutOfScopeDeletions",
+  "value": "True"
+}
 ```
 
 ## Step 4: Update the secrets endpoint with the SkipOutOfScopeDeletions flag

articles/ai-services/LUIS/luis-tutorial-node-import-utterances-csv.md

@@ -67,22 +67,22 @@ The column entries that contain the utterances in the CSV have to be parsed into
 For example, the entry for "Turn on the lights" maps to this JSON:
 
 ```json
+{
+    "text": "Turn on the lights",
+    "intentName": "TurnOn",
+    "entityLabels": [
         {
-            "text": "Turn on the lights",
-            "intentName": "TurnOn",
-            "entityLabels": [
-                {
-                    "entityName": "Operation",
-                    "startCharIndex": 5,
-                    "endCharIndex": 6
-                },
-                {
-                    "entityName": "Device",
-                    "startCharIndex": 12,
-                    "endCharIndex": 17
-                }
-            ]
+            "entityName": "Operation",
+            "startCharIndex": 5,
+            "endCharIndex": 6
+        },
+        {
+            "entityName": "Device",
+            "startCharIndex": 12,
+            "endCharIndex": 17
         }
+    ]
+}
 ```
 
 In this example, the `intentName` comes from the user request under the **Request** column heading in the CSV file, and the `entityName` comes from the other columns with key information. For example, if there's an entry for **Operation** or **Device**, and that string also occurs in the actual request, then it can be labeled as an entity. The following code demonstrates this parsing process. You can copy or [download](https://github.com/Azure-Samples/cognitive-services-language-understanding/blob/master/examples/build-app-programmatically-csv/_parse.js) it and save it to `_parse.js`.

articles/ai-services/language-service/text-analytics-for-health/concepts/relation-extraction.md

@@ -24,33 +24,33 @@ Text Analytics for health features relation extraction, which is used to  identi
 Relation extraction output contains URI references and assigned roles of the entities of the relation type. For example, in the following JSON:
 
 ```json
-                "relations": [
-                    {
-                        "relationType": "DosageOfMedication",
-                        "entities": [
-                            {
-                                "ref": "#/results/documents/0/entities/0",
-                                "role": "Dosage"
-                            },
-                            {
-                                "ref": "#/results/documents/0/entities/1",
-                                "role": "Medication"
-                            }
-                        ]
-                    },
-                    {
-                        "relationType": "RouteOfMedication",
-                        "entities": [
-                            {
-                                "ref": "#/results/documents/0/entities/1",
-                                "role": "Medication"
-                            },
-                            {
-                                "ref": "#/results/documents/0/entities/2",
-                                "role": "Route"
-                            }
-                        ]
-...
+"relations": [
+    {
+        "relationType": "DosageOfMedication",
+        "entities": [
+            {
+                "ref": "#/results/documents/0/entities/0",
+                "role": "Dosage"
+            },
+            {
+                "ref": "#/results/documents/0/entities/1",
+                "role": "Medication"
+            }
+        ]
+    },
+    {
+        "relationType": "RouteOfMedication",
+        "entities": [
+            {
+                "ref": "#/results/documents/0/entities/1",
+                "role": "Medication"
+            },
+            {
+                "ref": "#/results/documents/0/entities/2",
+                "role": "Route"
+            }
+        ]
+    }
 ]
 ```
 

articles/azure-maps/how-to-manage-pricing-tier.md

@@ -46,26 +46,26 @@ To change your pricing tier from Gen1 to Gen2 in the ARM template, update `prici
 :::image type="content" source="./media/how-to-manage-pricing-tier/arm-template.png" border="true" alt-text="Screenshot of an ARM template that demonstrates updating pricingTier to G2 and kind to Gen2.":::
 
 ```json
-        "pricingTier": { 
-            "type": "string", 
-            "allowedValues":[ 
-                "G2"
-            ], 
-            "defaultValue": "G2",
-            "metadata": { 
-                "description": "The pricing tier SKU for the account." 
-            } 
-        }, 
-        "kind": { 
-            "type": "string", 
-            "allowedValues":[ 
-                "Gen2" 
-            ], 
-            "defaultValue": "Gen2", 
-            "metadata": { 
-                "description": "The pricing tier for the account." 
-            } 
-        } 
+  "pricingTier": { 
+      "type": "string", 
+      "allowedValues":[ 
+          "G2"
+      ], 
+      "defaultValue": "G2",
+      "metadata": { 
+          "description": "The pricing tier SKU for the account." 
+      } 
+  }, 
+  "kind": { 
+      "type": "string", 
+      "allowedValues":[ 
+          "Gen2" 
+      ], 
+      "defaultValue": "Gen2", 
+      "metadata": { 
+          "description": "The pricing tier for the account." 
+      } 
+  } 
 ```
 :::code language="json" source="~/quickstart-templates/quickstarts/microsoft.maps/maps-create/azuredeploy.json" range="27-46":::
 --->