Merge pull request #216004 from alexbuckgit/alexbuckgit/docutune-autopr-20221026-161844-0971231

[BULK] Fix code block spacing issues (part 1)

Author: prmerger-automator[bot]

articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-cosmos-db.md

@@ -68,6 +68,7 @@ To gain access to the Azure Cosmos DB account access keys from the Resource Mana
 ```azurecli-interactive
 az resource show --id /subscriptions/<SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP>/providers/Microsoft.Compute/virtualMachines/<VM NAMe> --api-version 2017-12-01
 ```
+
 The response includes the details of the system-assigned managed identity (note the principalID as it is used in the next section):
 
 ```output  

articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-storage-access-key.md

@@ -116,6 +116,7 @@ The CURL response gives you the list of Keys:
 ```bash 
 {"keys":[{"keyName":"key1","permissions":"Full","value":"iqDPNt..."},{"keyName":"key2","permissions":"Full","value":"U+uI0B..."}]} 
 ```
+
 Create a sample blob file to upload to your blob storage container. On a Linux VM, you can do this with the following command. 
 
 ```bash

articles/app-service/deploy-container-github-action.md

@@ -151,6 +151,7 @@ When you configure the workflow file later, you use the secret for the input `cr
   with:
     creds: ${{ secrets.AZURE_CREDENTIALS }}
 ```
+
 # [OpenID Connect](#tab/openid)
 
 You need to provide your application's **Client ID**, **Tenant ID** and **Subscription ID** to the login action. These values can either be provided directly in the workflow or can be stored in GitHub secrets and referenced in your workflow. Saving the values as GitHub secrets is the more secure option.
@@ -277,6 +278,7 @@ jobs:
         publish-profile: ${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}
         images: 'mycontainer.azurecr.io/myapp:${{ github.sha }}'
 ```
+
 # [Service principal](#tab/service-principal)
 
 ```yaml
@@ -359,6 +361,7 @@ jobs:
       run: |
         az logout
 ```
+
 ---
 
 ## Next steps

articles/applied-ai-services/immersive-reader/tutorial-ios-picture-immersive-reader.md

@@ -44,8 +44,11 @@ Choose **Single View App**.
 The easiest way to use the Immersive Reader SDK is via CocoaPods. To install via Cocoapods:
 
 1. [Install CocoaPods](http://guides.cocoapods.org/using/getting-started.html) - Follow the getting started guide to install Cocoapods.
+
 2. Create a Podfile by running `pod init` in your Xcode project's root directory.
+
 3. Add the CocoaPod to your Podfile by adding `pod 'immersive-reader-sdk', :path => 'https://github.com/microsoft/immersive-reader-sdk/tree/master/iOS/immersive-reader-sdk'`. Your Podfile should look like the following, with your target's name replacing picture-to-immersive-reader-swift:
+
    ```ruby
    platform :ios, '9.0'
 
@@ -55,8 +58,11 @@ The easiest way to use the Immersive Reader SDK is via CocoaPods. To install via
    pod 'immersive-reader-sdk', :git => 'https://github.com/microsoft/immersive-reader-sdk.git'
    end
    ```
+
 4. In the terminal, in the directory of your Xcode project, run the command `pod install` to install the Immersive Reader SDK pod.
+
 5. Add `import immersive_reader_sdk` to all files that need to reference the SDK.
+
 6. Ensure to open the project by opening the `.xcworkspace` file and not the `.xcodeproj` file.
 
 ## Acquire an Azure AD authentication token

articles/cognitive-services/Speech-Service/includes/quickstarts/speaker-recognition-basics/go.md

@@ -194,6 +194,7 @@ Now build and run the code:
 go build
 go run independent-identification
 ```
+
 ## Perform independent verification
 
 Follow these steps to create a new GO module.

articles/databox-online/azure-stack-edge-gpu-deploy-virtual-machine-install-gpu-extension.md

@@ -216,6 +216,7 @@ $templateParameterFile = "<Path to addGPUExtWindowsVM.parameters.json>"
 RGName = "<Name of your resource group>"
 New-AzureRmResourceGroupDeployment -ResourceGroupName $RGName -TemplateFile $templateFile -TemplateParameterFile $templateParameterFile -Name "<Name for your deployment>"
 ```
+
 > [!NOTE]
 > The extension deployment is a long running job and takes about 10 minutes to complete.