Merge pull request #253098 from alexbuckgit/alexbuckgit/docutune-autopr-20230927-234151-7917831-ignore-build

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

Author: Jill Grant

articles/service-fabric/service-fabric-cluster-config-upgrade-azure.md

@@ -29,15 +29,15 @@ Azure clusters can be configured through the JSON Resource Manager template. To
 4. Select **Edit** and update the `fabricSettings` JSON element and add a new element:
 
 ```json
-      {
-        "name": "Diagnostics",
-        "parameters": [
-          {
-            "name": "MaxDiskQuotaInMB",
-            "value": "65536"
-          }
-        ]
-      }
+{
+  "name": "Diagnostics",
+  "parameters": [
+    {
+      "name": "MaxDiskQuotaInMB",
+      "value": "65536"
+    }
+  ]
+}
 ```
 
 You can also customize cluster settings in one of the following ways with Azure Resource Manager:

articles/service-fabric/service-fabric-cluster-config-upgrade-windows-server.md

@@ -21,15 +21,15 @@ You can add, update, or remove settings in the `fabricSettings` section under th
 For example, the following JSON adds a new setting *MaxDiskQuotaInMB* to the *Diagnostics* section under `fabricSettings`:
 
 ```json
-      {
-        "name": "Diagnostics",
-        "parameters": [
-          {
-            "name": "MaxDiskQuotaInMB",
-            "value": "65536"
-          }
-        ]
-      }
+{
+  "name": "Diagnostics",
+  "parameters": [
+    {
+      "name": "MaxDiskQuotaInMB",
+      "value": "65536"
+    }
+  ]
+}
 ```
 
 After you've modified the settings in your ClusterConfig.json file, [test the cluster configuration](#test-the-cluster-configuration) and then [upgrade the cluster configuration](#upgrade-the-cluster-configuration) to apply the settings to your cluster. 

articles/service-fabric/service-fabric-diagnostics-event-aggregation-wad.md

@@ -202,25 +202,26 @@ Logs from additional channels are also available for collection, here are some o
 
 * Operational Channel - Base: Enabled by default, high-level operations performed by Service Fabric and the cluster, including events for a node coming up, a new application being deployed, or an upgrade rollback, etc. For a list of events, refer to [Operational Channel Events](./service-fabric-diagnostics-event-generation-operational.md).
 
-```json
-      scheduledTransferKeywordFilter: "4611686018427387904"
+  ```json
+    "scheduledTransferKeywordFilter": "4611686018427387904"
   ```
+
 * Operational Channel - Detailed: This includes health reports and load balancing decisions, plus everything in the base operational channel. These events are generated by either the system or your code by using the health or load reporting APIs such as [ReportPartitionHealth](/previous-versions/azure/reference/mt645153(v=azure.100)) or [ReportLoad](/previous-versions/azure/reference/mt161491(v=azure.100)). To view these events in Visual Studio's Diagnostic Event Viewer add "Microsoft-ServiceFabric:4:0x4000000000000008" to the list of ETW providers.
 
-```json
-      scheduledTransferKeywordFilter: "4611686018427387912"
+  ```json
+    "scheduledTransferKeywordFilter": "4611686018427387912"
   ```
 
 * Data and Messaging Channel - Base: Critical logs and events generated in the messaging (currently only the ReverseProxy) and data path, in addition to detailed operational channel logs. These events are request processing failures and other critical issues in the ReverseProxy, as well as requests processed. **This is our recommendation for comprehensive logging**. To view these events in Visual Studio's Diagnostic Event Viewer, add "Microsoft-ServiceFabric:4:0x4000000000000010" to the list of ETW providers.
 
-```json
-      scheduledTransferKeywordFilter: "4611686018427387928"
+  ```json
+    "scheduledTransferKeywordFilter": "4611686018427387928"
   ```
 
 * Data & Messaging Channel - Detailed: Verbose channel that contains all the non-critical logs from data and messaging in the cluster and the detailed operational channel. For detailed troubleshooting of all reverse proxy events, refer to the [reverse proxy diagnostics guide](service-fabric-reverse-proxy-diagnostics.md).  To view these events in Visual Studio's Diagnostic Event viewer, add "Microsoft-ServiceFabric:4:0x4000000000000020" to the list of ETW providers.
 
-```json
-      scheduledTransferKeywordFilter: "4611686018427387944"
+  ```json
+    "scheduledTransferKeywordFilter": "4611686018427387944"
   ```
 
 >[!NOTE]
@@ -285,13 +286,13 @@ Update the `EtwEventSourceProviderConfiguration` section in the template.json fi
 For example, if your event source is named My-Eventsource, add the following code to place the events from My-Eventsource into a table named MyDestinationTableName.
 
 ```json
-        {
-            "provider": "My-Eventsource",
-            "scheduledTransferPeriod": "PT5M",
-            "DefaultEvents": {
-            "eventDestination": "MyDestinationTableName"
-            }
-        }
+{
+  "provider": "My-Eventsource",
+  "scheduledTransferPeriod": "PT5M",
+  "DefaultEvents": {
+    "eventDestination": "MyDestinationTableName"
+  }
+}
 ```
 
 To collect performance counters or event logs, modify the Resource Manager template by using the examples provided in [Create a Windows virtual machine with monitoring and diagnostics by using an Azure Resource Manager template](../virtual-machines/extensions/diagnostics-template.md?toc=/azure/virtual-machines/windows/toc.json). Then, republish the Resource Manager template.

articles/service-fabric/service-fabric-tutorial-standalone-create-service-fabric-cluster.md

@@ -39,13 +39,13 @@ Next, update the three ipAddress lines that occur in the file on lines 8, 15, an
 After updating the nodes, they appear as follows:
 
 ```json
-        {
-            "nodeName": "vm0",
-            "ipAddress": "172.31.27.1",
-            "nodeTypeRef": "NodeType0",
-            "faultDomain": "fd:/dc1/r0",
-            "upgradeDomain": "UD0"
-        }
+{
+  "nodeName": "vm0",
+  "ipAddress": "172.31.27.1",
+  "nodeTypeRef": "NodeType0",
+  "faultDomain": "fd:/dc1/r0",
+  "upgradeDomain": "UD0"
+}
 ```
 
 Then you need to update a couple of the properties.  On line 34, you need to modify the connection string for the diagnostic store it should look like this `"connectionstring": "C:\\ProgramData\\SF\\DiagnosticsStore"`

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-mvss-custom-image.md

@@ -90,13 +90,16 @@ In the scale set resource, add a `dependsOn` clause referring to the custom imag
 In the `imageReference` of the scale set `storageProfile`, instead of specifying the publisher, offer, sku, and version of a platform image, specify the `id` of the `Microsoft.Compute/images` resource:
 
 ```json
-         "virtualMachineProfile": {
-           "storageProfile": {
-             "imageReference": {
-              "id": "[resourceId('Microsoft.Compute/images', 'myCustomImage')]"
-             }
-           },
-           "osProfile": {
+  "virtualMachineProfile": {
+    "storageProfile": {
+      "imageReference": {
+        "id": "[resourceId('Microsoft.Compute/images', omImage')]"
+      }
+    },
+    "osProfile": {
+      ...
+    }
+  }
 ```
 
 In this example, use the `resourceId` function to get the resource ID of the image created in the same template. If you have created the managed disk image beforehand, you should provide the ID of that image instead. This ID must be of the form: `/subscriptions/<subscription-id>resourceGroups/<resource-group-name>/providers/Microsoft.Compute/images/<image-name>`.