[BULK] DocuTune - Fix formatting issues

Author: alexbuckgit

articles/automation/learn/automation-tutorial-runbook-textual.md

@@ -4,7 +4,7 @@ description: This tutorial teaches you to create, test, and publish a PowerShell
 services: automation
 ms.subservice: process-automation
 ms.date: 10/16/2022
-ms.topic: tutorial 
+ms.topic: tutorial
 ms.custom:
 #Customer intent: As a developer, I want use workflow runbooks so that I can automate the parallel starting of VMs.
 ---
@@ -46,7 +46,7 @@ Assign permissions to the appropriate [managed identity](../automation-security-
 
    :::image type="content" source="../media/automation-tutorial-runbook-textual/system-assigned-role-assignments-portal.png" alt-text="Selecting Azure role assignments in portal.":::
 
-1. Select **+ Add role assignment (Preview)** to open the **Add role assignment (Preview)** page. 
+1. Select **+ Add role assignment (Preview)** to open the **Add role assignment (Preview)** page.
 
    :::image type="content" source="../media/automation-tutorial-runbook-textual/system-assigned-add-role-assignment-portal.png" alt-text="Add role assignments in portal.":::
 
@@ -71,7 +71,7 @@ Assign permissions to the appropriate [managed identity](../automation-security-
 
    :::image type="content" source="../media/automation-tutorial-runbook-textual/managed-identity-client-id-portal.png" alt-text="Showing Client ID for managed identity in portal":::
 
-1. From the left menu, select **Azure role assignments** and then **+ Add role assignment (Preview)** to open the **Add role assignment (Preview)** page. 
+1. From the left menu, select **Azure role assignments** and then **+ Add role assignment (Preview)** to open the **Add role assignment (Preview)** page.
 
    :::image type="content" source="../media/automation-tutorial-runbook-textual/user-assigned-add-role-assignment-portal.png" alt-text="Add role assignments in portal for user-assigned identity.":::
 
@@ -91,7 +91,7 @@ Assign permissions to the appropriate [managed identity](../automation-security-
 Start by creating a simple [PowerShell Workflow runbook](../automation-runbook-types.md#powershell-workflow-runbooks). One advantage of Windows PowerShell Workflows is the ability to perform a set of commands in parallel instead of sequentially as with a typical script.
 
 >[!NOTE]
-> With release runbook creation has a new experience in the Azure portal. When you select **Runbooks** blade > **Create a runbook**, a new page **Create a runbook** opens with applicable options. 
+> With release runbook creation has a new experience in the Azure portal. When you select **Runbooks** blade > **Create a runbook**, a new page **Create a runbook** opens with applicable options.
 
 1. From your open Automation account page, under **Process Automation**, select **Runbooks**
 
@@ -103,9 +103,9 @@ Start by creating a simple [PowerShell Workflow runbook](../automation-runbook-t
     1. From the  **Runtime version** drop-down, select **5.1**.
     1. Enter applicable **Description**.
     1. Select **Create**.
-   
+
     :::image type="content" source="../media/automation-tutorial-runbook-textual/create-powershell-workflow-runbook-options.png" alt-text="PowerShell workflow runbook options from portal":::
-   
+
 
 ## Add code to the runbook
 
@@ -133,7 +133,7 @@ Workflow MyFirstRunbook-Workflow
    Write-Output "Non-Parallel"
    Get-Date
    Start-Sleep -s 3
-   Get-Date  
+   Get-Date
    ```
 
 1. Save the runbook by selecting **Save**.
@@ -152,7 +152,7 @@ Before you publish the runbook to make it available in production, you should te
 
    :::image type="content" source="../media/automation-tutorial-runbook-textual/workflow-runbook-parallel-output.png" alt-text="PowerShell workflow runbook parallel output":::
 
-   Review the output. Everything in the `Parallel` block, including the `Start-Sleep` command, executed at the same time. The same commands outside the `Parallel` block ran sequentially, as shown by the different date time stamps. 
+   Review the output. Everything in the `Parallel` block, including the `Start-Sleep` command, executed at the same time. The same commands outside the `Parallel` block ran sequentially, as shown by the different date time stamps.
 
 1. Close the **Test** page to return to the canvas.
 
@@ -190,15 +190,15 @@ You've tested and published your runbook, but so far it doesn't do anything usef
    workflow MyFirstRunbook-Workflow
    {
    $resourceGroup = "resourceGroupName"
-    
+
    # Ensures you do not inherit an AzContext in your runbook
    Disable-AzContextAutosave -Scope Process
-    
+
    # Connect to Azure with system-assigned managed identity
    Connect-AzAccount -Identity
-    
+
    # set and store context
-   $AzureContext = Set-AzContext –SubscriptionId "<SubscriptionID>"   
+   $AzureContext = Set-AzContext –SubscriptionId "<SubscriptionID>"
    }
    ```
 
@@ -219,9 +219,9 @@ You've tested and published your runbook, but so far it doesn't do anything usef
 
 ## Add code to start a virtual machine
 
-Now that your runbook is authenticating to the Azure subscription, you can manage resources. Add a command to start a virtual machine. You can pick any VM in your Azure subscription, and for now you're hardcoding that name in the runbook. 
+Now that your runbook is authenticating to the Azure subscription, you can manage resources. Add a command to start a virtual machine. You can pick any VM in your Azure subscription, and for now you're hardcoding that name in the runbook.
 
-1. Add the code below as the last line immediately before the closing brace. Replace `VMName` with the actual name of a VM. 
+1. Add the code below as the last line immediately before the closing brace. Replace `VMName` with the actual name of a VM.
 
    ```powershell
    Start-AzVM -Name "VMName" -ResourceGroupName $resourceGroup -DefaultProfile $AzureContext
@@ -262,43 +262,42 @@ You can use the `ForEach -Parallel` construct to process commands for each item
     ```powershell
     workflow MyFirstRunbook-Workflow
     {
-    Param(
-        [string]$resourceGroup,
-        [string[]]$VMs,
-        [string]$action
-    )
-    
-    # Ensures you do not inherit an AzContext in your runbook
-    Disable-AzContextAutosave -Scope Process
-    
-    # Connect to Azure with system-assigned managed identity
-    Connect-AzAccount -Identity
-    
-    # set and store context
-    $AzureContext = Set-AzContext –SubscriptionId "<SubscriptionID>"   
-    
-    # Start or stop VMs in parallel
-    if($action -eq "Start")
-        {
-            ForEach -Parallel ($vm in $VMs)
-            {
-                Start-AzVM -Name $vm -ResourceGroupName $resourceGroup -DefaultProfile $AzureContext
-            }
-        }
-    elseif ($action -eq "Stop")
-        {
-            ForEach -Parallel ($vm in $VMs)
-            {
-                Stop-AzVM -Name $vm -ResourceGroupName $resourceGroup -DefaultProfile $AzureContext -Force
-            }
-        }
-    else {
-    	    Write-Output "`r`n Action not allowed. Please enter 'stop' or 'start'."
-    	}
-    }
+       Param(
+           [string]$resourceGroup,
+           [string[]]$VMs,
+           [string]$action
+       )
+
+       # Ensures you do not inherit an AzContext in your runbook
+       Disable-AzContextAutosave -Scope Process
+
+       # Connect to Azure with system-assigned managed identity
+       Connect-AzAccount -Identity
+
+       # set and store context
+       $AzureContext = Set-AzContext –SubscriptionId "<SubscriptionID>"
+
+       # Start or stop VMs in parallel
+       if ($action -eq "Start") {
+           ForEach -Parallel ($vm in $VMs)
+           {
+               Start-AzVM -Name $vm -ResourceGroupName $resourceGroup -DefaultProfile $AzureContext
+           }
+       }
+       elseif ($action -eq "Stop") {
+           ForEach -Parallel ($vm in $VMs)
+           {
+               Stop-AzVM -Name $vm -ResourceGroupName $resourceGroup -DefaultProfile $AzureContext -Force
+           }
+       }
+       else {
+           Write-Output "`r`n Action not allowed. Please enter 'stop' or 'start'."
+       }
+       }
     ```
 
 1. If you want the runbook to execute with the system-assigned managed identity, leave the code as-is. If you prefer to use a user-assigned managed identity, then:
+
     1. From line 9, remove `Connect-AzAccount -Identity`,
     1. Replace it with `Connect-AzAccount -Identity -AccountId <ClientId>`, and
     1. Enter the Client ID you obtained earlier.

articles/automation/update-management/enable-from-template.md

@@ -5,7 +5,7 @@ services:  automation
 ms.subservice: update-management
 ms.custom: devx-track-arm-template
 ms.topic: conceptual
-ms.date: 09/18/2020 
+ms.date: 09/18/2020
 ---
 
 # Enable Update Management using Azure Resource Manager template
@@ -178,25 +178,25 @@ If you're new to Azure Automation and Azure Monitor, it's important that you und
             }
           }
         },
-    	{
-    		"apiVersion": "2015-11-01-preview",
-    		"location": "[parameters('location')]",
-    		"name": "[variables('Updates').name]",
-    		"type": "Microsoft.OperationsManagement/solutions",
-    		"id": "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.OperationsManagement/solutions/', variables('Updates').name)]",
-    		"dependsOn": [
-    			"[concat('Microsoft.OperationalInsights/workspaces/', parameters('workspaceName'))]"
-    		],
-    		"properties": {
-    			"workspaceResourceId": "[resourceId('Microsoft.OperationalInsights/workspaces/', parameters('workspaceName'))]"
-    		},
-    		"plan": {
-    			"name": "[variables('Updates').name]",
-    			"publisher": "Microsoft",
-    			"promotionCode": "",
-    			"product": "[concat('OMSGallery/', variables('Updates').galleryName)]"
-    		}
-    	},
+      {
+        "apiVersion": "2015-11-01-preview",
+        "location": "[parameters('location')]",
+        "name": "[variables('Updates').name]",
+        "type": "Microsoft.OperationsManagement/solutions",
+        "id": "[concat('/subscriptions/', subscription().subscriptionId, '/resourceGroups/', resourceGroup().name, '/providers/Microsoft.OperationsManagement/solutions/', variables('Updates').name)]",
+        "dependsOn": [
+          "[concat('Microsoft.OperationalInsights/workspaces/', parameters('workspaceName'))]"
+        ],
+        "properties": {
+          "workspaceResourceId": "[resourceId('Microsoft.OperationalInsights/workspaces/', parameters('workspaceName'))]"
+        },
+        "plan": {
+          "name": "[variables('Updates').name]",
+          "publisher": "Microsoft",
+          "promotionCode": "",
+          "product": "[concat('OMSGallery/', variables('Updates').galleryName)]"
+        }
+      },
         {
           "type": "Microsoft.Automation/automationAccounts",
           "apiVersion": "2020-01-13-preview",

articles/azure-arc/data/includes/upgrade-rollback.md

@@ -22,7 +22,7 @@ When the desired version is set to a specific version, the bootstrapper job will
    ```
 1. To get a list of the containers in the pods, run 
 
-   ```console 
+   ```console
    kubectl get pods <pod name> --namespace <namespace> -o jsonpath='{.spec.containers[*].name}*'
    ```
 1. To get the logs for a container, run  

articles/azure-monitor/agents/azure-monitor-agent-migration-tools.md

@@ -56,35 +56,35 @@ To install DCR Config Generator:
 
 1. Run the script:
 
-	Option 1: Outputs **ready-to-deploy ARM template files** only, which creates the generated DCR in the specified subscription and resource group, when deployed.
-
-	```powershell
-	.\WorkspaceConfigToDCRMigrationTool.ps1 -SubscriptionId $subId -ResourceGroupName $rgName -WorkspaceName $workspaceName -DCRName $dcrName -Location $location -FolderPath $folderPath
-	```
-	Option 2: Outputs **ready-to-deploy ARM template files** and **the DCR JSON files** separately for you to deploy via other means. You need to set the `GetDcrPayload` parameter.
-
-	```powershell
-	.\WorkspaceConfigToDCRMigrationTool.ps1 -SubscriptionId $subId -ResourceGroupName $rgName -WorkspaceName $workspaceName -DCRName $dcrName -Location $location -FolderPath $folderPath -GetDcrPayload
-	```
-
-	**Parameters**  
-	
-	| Parameter | Required? | Description |
-	|------|------|------|
-	| `SubscriptionId` | Yes | ID of the subscription that contains the target workspace. |
-	| `ResourceGroupName` | Yes | Resource group that contains the target workspace. |
-	| `WorkspaceName` | Yes | Name of the target workspace. |
-	| `DCRName` | Yes | Name of the new DCR. |
-	| `Location` | Yes | Region location for the new DCR. |
-	| `GetDcrPayload` | No | When set, it generates additional DCR JSON files 
-	| `FolderPath` | No | Path in which to save the ARM template files and JSON files (optional). By default, Azure Monitor uses the current directory. |  
-	
+    Option 1: Outputs **ready-to-deploy ARM template files** only, which creates the generated DCR in the specified subscription and resource group, when deployed.
+
+    ```powershell
+    .\WorkspaceConfigToDCRMigrationTool.ps1 -SubscriptionId $subId -ResourceGroupName $rgName -WorkspaceName $workspaceName -DCRName $dcrName -Location $location -FolderPath $folderPath
+    ```
+    Option 2: Outputs **ready-to-deploy ARM template files** and **the DCR JSON files** separately for you to deploy via other means. You need to set the `GetDcrPayload` parameter.
+
+    ```powershell
+    .\WorkspaceConfigToDCRMigrationTool.ps1 -SubscriptionId $subId -ResourceGroupName $rgName -WorkspaceName $workspaceName -DCRName $dcrName -Location $location -FolderPath $folderPath -GetDcrPayload
+    ```
+
+    **Parameters**
+
+    | Parameter | Required? | Description |
+    |------|------|------|
+    | `SubscriptionId` | Yes | ID of the subscription that contains the target workspace. |
+    | `ResourceGroupName` | Yes | Resource group that contains the target workspace. |
+    | `WorkspaceName` | Yes | Name of the target workspace. |
+    | `DCRName` | Yes | Name of the new DCR. |
+    | `Location` | Yes | Region location for the new DCR. |
+    | `GetDcrPayload` | No | When set, it generates additional DCR JSON files 
+    | `FolderPath` | No | Path in which to save the ARM template files and JSON files (optional). By default, Azure Monitor uses the current directory. |
+
 1. Review the output ARM template files. The script can produce two types of ARM template files, depending on the agent configuration in the target workspace:
 
-	- Windows ARM template and parameter files - if the target workspace contains Windows performance counters or Windows events.
-	- Linux ARM template and parameter files - if the target workspace contains Linux performance counters or Linux Syslog events.
-	
-	If the Log Analytics workspace wasn't [configured to collect data](./log-analytics-agent.md#data-collected) from connected agents, the generated files will be empty. This is a scenario in which the agent was connected to a Log Analytics workspace, but wasn't configured to send any data from the host machine.
+    - Windows ARM template and parameter files - if the target workspace contains Windows performance counters or Windows events.
+    - Linux ARM template and parameter files - if the target workspace contains Linux performance counters or Linux Syslog events.
+
+    If the Log Analytics workspace wasn't [configured to collect data](./log-analytics-agent.md#data-collected) from connected agents, the generated files will be empty. This is a scenario in which the agent was connected to a Log Analytics workspace, but wasn't configured to send any data from the host machine.
 
 1. Deploy the generated ARM templates:
     

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-linux-vm-rsyslog.md

@@ -19,8 +19,8 @@ Overview of Azure Monitor Agent for Linux Syslog collection and supported RFC st
 - Azure Monitor Agent ingests Syslog events via the previously mentioned socket and filters them based on facility or severity combination from data collection rule (DCR) configuration in `/etc/opt/microsoft/azuremonitoragent/config-cache/configchunks/`. Any `facility` or `severity` not present in the DCR is dropped.
 - Azure Monitor Agent attempts to parse events in accordance with **RFC3164** and **RFC5424**. It also knows how to parse the message formats listed on [this website](./azure-monitor-agent-overview.md#data-sources-and-destinations).
 - Azure Monitor Agent identifies the destination endpoint for Syslog events from the DCR configuration and attempts to upload the events.
-	> [!NOTE]
-	> Azure Monitor Agent uses local persistency by default. All events received from `rsyslog` or `syslog-ng` are queued in `/var/opt/microsoft/azuremonitoragent/events` if they fail to be uploaded.
+  > [!NOTE]
+  > Azure Monitor Agent uses local persistency by default. All events received from `rsyslog` or `syslog-ng` are queued in `/var/opt/microsoft/azuremonitoragent/events` if they fail to be uploaded.
 
 ## Issues
 
@@ -92,15 +92,15 @@ If you're sending a high log volume through rsyslog and your system is set up to
 
 1. For example, to remove `local4` events from being logged at `/var/log/syslog` or `/var/log/messages`, change this line in `/etc/rsyslog.d/50-default.conf` from this snippet:
 
-	```config
-	*.*;auth,authpriv.none          -/var/log/syslog
-	```
+    ```config
+    *.*;auth,authpriv.none          -/var/log/syslog
+    ```
 
-	To this snippet (add `local4.none;`):
+    To this snippet (add `local4.none;`):
 
-	```config
-	*.*;local4.none;auth,authpriv.none          -/var/log/syslog
-	```
+    ```config
+    *.*;local4.none;auth,authpriv.none          -/var/log/syslog
+    ```
 
 1. `sudo systemctl restart rsyslog`