Fixes

Author: alexbuckgit

articles/devtest-labs/devtest-lab-vm-powershell.md

@@ -186,7 +186,7 @@ You can also call the DevTest Labs REST API to get the properties of existing la
 In training, demo, and trial scenarios, you can avoid unnecessary costs by deleting VMs automatically on a certain date. You can set the VM `expirationDate` property when you create a VM. The PowerShell VM creation script earlier in this article sets an expiration date under `properties`:
 
 ```json
-  "expirationDate" = "2022-12-01"
+  "expirationDate": "2022-12-01"
 ```
 
 You can also set expiration dates on existing VMs by using PowerShell. The following PowerShell script sets an expiration date for an existing lab VM if it doesn't already have an expiration date:

articles/machine-learning/how-to-create-compute-instance.md

@@ -402,7 +402,7 @@ In the Resource Manager template, add:
 ```
 
 Then use either cron or LogicApps expressions to define the schedule that starts or stops the instance in your parameter file:
- 
+
 ```json
   "schedules": {
     "value": {
@@ -426,18 +426,18 @@ Then use either cron or LogicApps expressions to define the schedule that starts
           "status": "Enabled"
         },
         { 
-          "triggerType": "Recurrence",
-          "recurrence": {
-            "frequency": "Day",
-            "interval": 1,
-            "timeZone": "UTC",
-            "schedule": {
-              "hours": [17],
-              "minutes": [0]
+          "triggerType": "Recurrence",
+          "recurrence": {
+            "frequency": "Day",
+            "interval": 1,
+            "timeZone": "UTC",
+            "schedule": {
+              "hours": [17],
+              "minutes": [0]
             }
           }, 
-          "action": "Stop",
-          "status": "Enabled"
+          "action": "Stop",
+          "status": "Enabled"
         } 
       ]
     }