Merge pull request #107106 from TimShererWithAquent/us1669724j

Code blocks, azurecli.

Author: PRMerger16

articles/spring-cloud/spring-cloud-cli-reference.md

@@ -31,7 +31,7 @@ Install the Azure Spring Cloud extension for the Azure CLI by using the followin
 ```azurecli
 az extension add --name spring-cloud
 ```
-	
+    
 ## View all deployments
 
 Go to your service instance in the Azure portal, and select **Deployment management** to view all deployments. To view more details, you can select each deployment.
@@ -40,7 +40,7 @@ Go to your service instance in the Azure portal, and select **Deployment managem
 
 1. In your local development environment, make a small modification to the PiggyMetrics gateway application. For instance, change the color in the *gateway/src/main/resources/static/css/launch.css* file. Doing so lets you easily differentiate the two deployments. To build the jar package, run the following command: 
 
-    ```azurecli
+    ```console
     mvn clean package
     ```
 

articles/spring-cloud/spring-cloud-howto-staging-environment.md

@@ -43,15 +43,15 @@ Before you begin, ensure that your Azure subscription has the required dependenc
 
 Install the Azure Spring Cloud extension for the Azure CLI with the following command
 
-```Azure CLI
+```azurecli
 az extension add --name spring-cloud
 ```
 
 ## Provision a service instance using the Azure CLI
 
 Login to the Azure CLI and choose your active subscription. Be sure to choose the active subscription that is whitelisted for Azure Spring Cloud
 
-```Azure CLI
+```azurecli
 az login
 az account list -o table
 az account set --subscription

articles/spring-cloud/spring-cloud-launch-from-source.md

@@ -64,6 +64,7 @@ az extension add --name spring-cloud
     ```azurecli
         az group create --location eastus --name <resource group name>
     ```
+
     Learn more about [Azure Resource Groups](../azure-resource-manager/management/overview.md).
 
 4. Open an Azure CLI window and run the following commands to provision an instance of Azure Spring Cloud.
@@ -99,14 +100,14 @@ az spring-cloud config-server git set -n <service instance name> --uri https://g
 
 1. Create a new folder and clone the sample app repository to your Azure Cloud account.  
 
-    ```azurecli
+    ```console
         mkdir source-code
         git clone https://github.com/Azure-Samples/piggymetrics
     ```
 
 2. Change directory and build the project.
 
-    ```azurecli
+    ```console
         cd piggymetrics
         mvn clean package -D skipTests
     ```
@@ -145,16 +146,21 @@ We need a way to access the application via a web browser. Our gateway applicati
 ```azurecli
 az spring-cloud app update -n gateway --is-public true
 ```
+
 2. Query the **gateway** application for its public IP so you can verify that the application is running:
 
 Linux:
+
 ```azurecli
 az spring-cloud app show --name gateway | grep url
 ```
+
 Windows:
+
 ```azurecli
 az spring-cloud app show -s <service name> -g <resource group> -n gateway -o table
 ```
+
 3. Navigate to the URL provided by the previous command to run the PiggyMetrics application.
     ![Screenshot of PiggyMetrics running](media/spring-cloud-quickstart-launch-app-cli/launch-app.png)
 

articles/spring-cloud/spring-cloud-quickstart-launch-app-cli.md

@@ -73,13 +73,13 @@ It takes about 5 minutes for the service to be deployed. After the service is de
 
 1. Clone the Git repository by running the following command:
 
-    ```azurecli
+    ```console
     git clone https://github.com/Azure-Samples/PiggyMetrics
     ```
   
 1. Change directory and build the project by running the following command:
 
-    ```azurecli
+    ```console
     cd piggymetrics
     mvn clean package -DskipTests
     ```
@@ -88,7 +88,7 @@ It takes about 5 minutes for the service to be deployed. After the service is de
 
 1. Generate configurations by running the following command in the root folder of PiggyMetrics containing the parent POM:
 
-    ```azurecli
+    ```console
     mvn com.microsoft.azure:azure-spring-cloud-maven-plugin:1.0.0:config
     ```
 
@@ -102,7 +102,7 @@ It takes about 5 minutes for the service to be deployed. After the service is de
 
 1. The POM now contains the plugin dependencies and configurations. Deploy the apps using the following command:
 
-   ```azurecli
+   ```console
    mvn azure-spring-cloud:deploy
    ```
 

articles/spring-cloud/spring-cloud-quickstart-launch-app-maven.md

@@ -43,7 +43,7 @@ To complete this quickstart:
 
 Install the Azure Spring Cloud extension for the Azure CLI using the following command
 
-```Azure CLI
+```azurecli
 az extension add --name spring-cloud
 ```
 
@@ -109,18 +109,19 @@ It takes about 5 minutes for the service to deploy.  Once it is deployed, the **
 
 1. Open an [Azure Cloud Shell](https://shell.azure.com)  and clone the sample app repository to your local machine.  Here, we first create a temporary directory called `source-code` before cloning the app.
 
-    ```azurecli
+    ```console
     mkdir source-code
     cd source-code
     git clone https://github.com/Azure-Samples/piggymetrics
     ```
 
 2. Build the cloned package.
 
-    ```azurecli
+    ```console
     cd piggymetrics
     mvn clean package -DskipTests
     ```
+
 3. Assign names to your resource group and your service. Be sure to substitute the placeholders below with the resource group name and service name that you provisioned earlier in this tutorial.
 
     ```azurecli

articles/spring-cloud/spring-cloud-quickstart-launch-app-portal.md

@@ -59,7 +59,7 @@ Write-Output "_applicationSecret:" $secret
 
 # [Azure CLI](#tab/azure-cli)
 
-```azure-cli
+```azurecli
 # sign in to Azure
 az login
 

articles/sql-database/sql-database-client-id-keys.md

@@ -61,7 +61,7 @@ For a complete sample PowerShell script, see [Copy a database to a new server](s
 
 # [Azure CLI](#tab/azure-cli)
 
-```azure-cli
+```azurecli
 az sql db copy --dest-name "CopyOfMySampleDatabase" --dest-resource-group "myResourceGroup" --dest-server $targetserver `
     --name "<databaseName>" --resource-group "<resourceGroup>" --server $sourceserver
 ```

articles/sql-database/sql-database-copy.md

@@ -340,21 +340,21 @@ To test a failover:
 
 You can check the role of the disaster recovery server during the test with the following command:
 
-```azure-cli
+```azurecli
 az sql failover-group show --name $failoverGroup --resource-group $resourceGroup --server $drServer
 ```
 
 To test a failover:
 
 1. Start a manual failover of the failover group:
 
-   ```azure-cli
+   ```azurecli
    az sql failover-group set-primary --name $failoverGroup --resource-group $resourceGroup --server $drServer
    ```
 
 1. Revert failover group back to the primary server:
 
-   ```azure-cli
+   ```azurecli
    az sql failover-group set-primary --name $failoverGroup --resource-group $resourceGroup --server $server
    ```