Merge pull request #277518 from v-jaswel/aca/v-jaswel_fix_include_tab_discrepancy_20240606

[ACA] Fix discrepancy with tabs in include file.

Author: prmerger-automator[bot]

articles/container-apps/tutorial-ci-cd-runners-jobs.md

@@ -84,7 +84,7 @@ ENVIRONMENT="env-jobs-sample"
 JOB_NAME="github-actions-runner-job"
 ```
 
-# [PowerShell](#tab/powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 ```powershell
 $RESOURCE_GROUP="jobs-sample"
 $LOCATION="northcentralus"
@@ -107,7 +107,7 @@ JOB_NAME="azure-pipelines-agent-job"
 PLACEHOLDER_JOB_NAME="placeholder-agent-job"
 ```
 
-# [PowerShell](#tab/powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 ```powershell
 $RESOURCE_GROUP="jobs-sample"
 $LOCATION="northcentralus"
@@ -136,7 +136,7 @@ The Azure Container Apps environment acts as a secure boundary around container
         --location "$LOCATION"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az group create `
         --name "$RESOURCE_GROUP" `
@@ -155,7 +155,7 @@ The Azure Container Apps environment acts as a secure boundary around container
         --location "$LOCATION"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az containerapp env create `
         --name "$ENVIRONMENT" `
@@ -235,7 +235,7 @@ To run a self-hosted runner, you need to create a personal access token (PAT) in
     REPO_NAME="<REPO_NAME>"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     $GITHUB_PAT="<GITHUB_PAT>"
     $REPO_OWNER="<REPO_OWNER>"
@@ -267,7 +267,7 @@ To create a self-hosted runner, you need to build a container image that execute
     CONTAINER_REGISTRY_NAME="<CONTAINER_REGISTRY_NAME>"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     $CONTAINER_IMAGE_NAME="github-actions-runner:1.0"
     $CONTAINER_REGISTRY_NAME="<CONTAINER_REGISTRY_NAME>"
@@ -289,7 +289,7 @@ To create a self-hosted runner, you need to build a container image that execute
         --admin-enabled true
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az acr create `
         --name "$CONTAINER_REGISTRY_NAME" `
@@ -312,7 +312,7 @@ To create a self-hosted runner, you need to build a container image that execute
         "https://github.com/Azure-Samples/container-apps-ci-cd-runner-tutorial.git"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az acr build `
         --registry "$CONTAINER_REGISTRY_NAME" `
@@ -354,7 +354,7 @@ You can now create a job that uses to use the container image. In this section,
         --registry-server "$CONTAINER_REGISTRY_NAME.azurecr.io"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az containerapp job create -n "$JOB_NAME" -g "$RESOURCE_GROUP" --environment "$ENVIRONMENT" `
         --trigger-type Event `
@@ -439,7 +439,7 @@ To verify the job was configured correctly, you modify the workflow to use a sel
         --query '[].{Status: properties.status, Name: name, StartTime: properties.startTime}'
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az containerapp job execution list `
         --name "$JOB_NAME" `
@@ -535,7 +535,7 @@ To run a self-hosted runner, you need to create a personal access token (PAT) in
     AZP_POOL="container-apps"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     $AZP_TOKEN="<AZP_TOKEN>"
     $ORGANIZATION_URL="<ORGANIZATION_URL>"
@@ -566,7 +566,7 @@ To create a self-hosted agent, you need to build a container image that runs the
     CONTAINER_REGISTRY_NAME="<CONTAINER_REGISTRY_NAME>"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     $CONTAINER_IMAGE_NAME="azure-pipelines-agent:1.0"
     $CONTAINER_REGISTRY_NAME="<CONTAINER_REGISTRY_NAME>"
@@ -590,7 +590,7 @@ To create a self-hosted agent, you need to build a container image that runs the
         --admin-enabled true
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az acr create `
         --name "$CONTAINER_REGISTRY_NAME" `
@@ -613,7 +613,7 @@ To create a self-hosted agent, you need to build a container image that runs the
         "https://github.com/Azure-Samples/container-apps-ci-cd-runner-tutorial.git"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az acr build `
         --registry "$CONTAINER_REGISTRY_NAME" `
@@ -650,7 +650,7 @@ You can run a manual job to register an offline placeholder agent. The job runs
         --registry-server "$CONTAINER_REGISTRY_NAME.azurecr.io"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
         az containerapp job create -n "$PLACEHOLDER_JOB_NAME" -g "$RESOURCE_GROUP" --environment "$ENVIRONMENT" `
         --trigger-type Manual `
@@ -689,7 +689,7 @@ You can run a manual job to register an offline placeholder agent. The job runs
     az containerapp job start -n "$PLACEHOLDER_JOB_NAME" -g "$RESOURCE_GROUP"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az containerapp job start -n "$PLACEHOLDER_JOB_NAME" -g "$RESOURCE_GROUP"
     ```
@@ -707,7 +707,7 @@ You can run a manual job to register an offline placeholder agent. The job runs
         --query '[].{Status: properties.status, Name: name, StartTime: properties.startTime}'
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az containerapp job execution list `
         --name "$PLACEHOLDER_JOB_NAME" `
@@ -731,7 +731,7 @@ You can run a manual job to register an offline placeholder agent. The job runs
     az containerapp job delete -n "$PLACEHOLDER_JOB_NAME" -g "$RESOURCE_GROUP"
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az containerapp job delete -n "$PLACEHOLDER_JOB_NAME" -g "$RESOURCE_GROUP"
     ```
@@ -765,7 +765,7 @@ az containerapp job create -n "$JOB_NAME" -g "$RESOURCE_GROUP" --environment "$E
     --registry-server "$CONTAINER_REGISTRY_NAME.azurecr.io"
 ```
 
-# [PowerShell](#tab/powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 ```powershell
 az containerapp job create -n "$JOB_NAME" -g "$RESOURCE_GROUP" --environment "$ENVIRONMENT" `
     --trigger-type Event `
@@ -842,7 +842,7 @@ Now that you've configured a self-hosted agent job, you can run a pipeline and v
         --query '[].{Status: properties.status, Name: name, StartTime: properties.startTime}'
     ```
 
-    # [PowerShell](#tab/powershell)
+    # [Azure PowerShell](#tab/azure-powershell)
     ```powershell
     az containerapp job execution list `
         --name "$JOB_NAME" `
@@ -871,7 +871,7 @@ az group delete \
     --resource-group $RESOURCE_GROUP
 ```
 
-# [PowerShell](#tab/powershell)
+# [Azure PowerShell](#tab/azure-powershell)
 ```powershell
 az group delete `
     --resource-group $RESOURCE_GROUP