Add edits

Author: cdpark

articles/app-service/app-service-web-app-cloning.md

@@ -8,19 +8,19 @@ ms.custom: devx-track-azurepowershell
 author: msangapu-msft
 ms.author: msangapu
 ---
-# Clone an Azure App Service App by using PowerShell
+# Clone an Azure App Service app by using PowerShell
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
-This article explains how you can clone an existing App Service app to a newly created app in a different region or in the same region. You can deploy multiple apps across different regions quickly and easily.
+This article explains how you can clone an existing App Service app to create a new app in a different region or in the same region. You can deploy multiple apps across different regions quickly and easily.
 
-App cloning is supported in **Standard**, **Premium**, **Premium V2**, and **Isolated** pricing tiers. The feature uses the same limitations as the App Service Backup feature, see [Back up an app in Azure App Service](manage-backup.md).
+App cloning is supported in **Standard**, **Premium**, **Premium V2**, and **Isolated** pricing tiers. The feature has the same limitations as the App Service Backup feature, see [Back up an app in Azure App Service](manage-backup.md).
 
 ## Clone an existing app
 
-Scenario: You want to clone the contents of an existing app in the South Central US region to a new app in the North Central US region. You can use the Azure Resource Manager version of the PowerShell cmdlet to create a new app with the `-SourceWebApp` option.
+Scenario: You want to clone the contents of an existing app in the South Central US region to a new app in the North Central US region. You can use the Azure Resource Manager version of the PowerShell cmdlet to create a new app by using the `-SourceWebApp` option.
 
-When you know the name of the resource group that contains the source app, you can use the following PowerShell command to get the source app's information (in this case named `source-webapp`):
+When you know the name of the resource group that contains the source app, you can use the following PowerShell command to get the source app's information, in this case named `source-webapp`:
 
 ```powershell
 $srcapp = Get-AzWebApp -ResourceGroupName SourceAzureResourceGroup -Name source-webapp
@@ -38,7 +38,7 @@ By using the `New-AzWebApp` command, you can create the new app in the North Cen
 $destapp = New-AzWebApp -ResourceGroupName DestinationAzureResourceGroup -Name dest-webapp -Location "North Central US" -AppServicePlan DestinationAppServicePlan -SourceWebApp $srcapp
 ```
 
-To clone an existing app, including all associated deployment slots, you need to use the `IncludeSourceWebAppSlots` parameter. The `IncludeSourceWebAppSlots` parameter is supported only for cloning an entire app including all of its slots. The following PowerShell command demonstrates the use of that parameter with the `New-AzWebApp` command:
+To clone an existing app, including all associated deployment slots, you need to use the `IncludeSourceWebAppSlots` parameter. This parameter is supported only for cloning an entire app including all of its slots. The following PowerShell command demonstrates the use of that parameter with the `New-AzWebApp` command:
 
 ```powershell
 $destapp = New-AzWebApp -ResourceGroupName DestinationAzureResourceGroup -Name dest-webapp -Location "North Central US" -AppServicePlan DestinationAppServicePlan -SourceWebApp $srcapp -IncludeSourceWebAppSlots
@@ -54,7 +54,7 @@ $destapp = New-AzWebApp -ResourceGroupName NewAzureResourceGroup -Name dest-weba
 
 Scenario: You want to clone the contents of an existing app in the South Central US region to a new app in an existing App Service Environment.
 
-When you know the name of the resource group that contains the source app, you can use the following PowerShell command to get the source app's information (in this case named `source-webapp`):
+When you know the name of the resource group that contains the source app, you can use the following PowerShell command to get the source app's information, in this case named `source-webapp`:
 
 ```powershell
 $srcapp = Get-AzWebApp -ResourceGroupName SourceAzureResourceGroup -Name source-webapp

articles/app-service/deploy-ci-cd-custom-container.md

@@ -43,7 +43,7 @@ After you authorize your Azure account with GitHub, select the **Organization**,
 ## 3. Configure registry settings
 
 > [!NOTE]
-> Sidecar containers (preview) will succeed multi-container (Docker Compose) apps in App Service. To get started, see [Tutorial: Configure a sidecar container for custom containers in Azure App Service (preview)](tutorial-custom-container-sidecar.md).
+> Sidecar containers will succeed multi-container (Docker Compose) apps in App Service. To get started, see [Tutorial: Configure a sidecar container for custom containers in Azure App Service](tutorial-custom-container-sidecar.md).
 
 To deploy a multi-container (Docker Compose) app, select **Docker Compose** in **Container Type**.
 
@@ -144,25 +144,18 @@ To verify whether **Basic Auth Publishing Credentials** is enabled, go to your w
 
 For other private registries, you can post to the webhook manually or as a step in a CI/CD pipeline. In **Webhook URL**, select the **Copy** button to get the webhook URL.
 
+Select **Save** to save your settings.
+
 ::: zone pivot="container-linux"
 > [!NOTE]
 > Support for multi-container (Docker Compose) apps is limited. For Azure Container Registry, App Service creates a webhook in the selected registry with the registry as the scope. A `docker push` to any repository in the registry (including the ones not referenced by your Docker Compose file) triggers an app restart. You might want to [modify the webhook](/azure/container-registry/container-registry-webhook) to a narrower scope. Docker Hub doesn't support webhooks at the registry level. You must add the webhooks manually to the images specified in your Docker Compose file.
 ::: zone-end
 
-::: zone pivot="container-windows"
-## 4. Save your settings
-::: zone-end
-::: zone pivot="container-linux"
-## 5. Save your settings
-::: zone-end
-
-Select **Save**.
-
 ::: zone pivot="container-linux"
 
 ## How CI/CD works with GitHub Actions
 
-If you choose **GitHub Actions** in **Source** (see [Choose deployment source](#2-choose-deployment-source)), App Service sets up CI/CD in the following ways:
+If you choose **GitHub Actions** from the [Select code source](#2-select-code-source) dropdown menu, App Service sets up CI/CD in the following ways:
 
 * It deposits a GitHub Actions workflow file into your GitHub repository to handle build and deploy tasks to App Service.
 * It adds the credentials for your private registry as GitHub secrets. The generated workflow file runs the [`Azure/docker-login`](https://github.com/Azure/docker-login) action to sign in with your private registry, and then runs `docker push` to deploy to it.

articles/app-service/manage-scale-per-app.md

@@ -9,11 +9,11 @@ ms.date: 05/02/2025
 ms.author: msangapu
 ms.custom: devx-track-azurepowershell, devx-track-arm-template
 ---
-# High-density hosting on Azure App Service using per-app scaling
+# High-density hosting using per-app scaling
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
-You can scale your apps by scaling the [App Service plan](overview-hosting-plans.md) they run on. When multiple apps are running in the same App Service plan, each scaled-out instance runs all the apps in the plan.
+You can scale your Azure App Service apps by scaling the [App Service plan](overview-hosting-plans.md) they run on. When multiple apps run in the same App Service plan, each scaled-out instance runs all the apps in the plan.
 
 In contrast, *per-app scaling* can be enabled at the App Service plan level to scale an app independently from the
 App Service plan that hosts it. This way, an App Service plan can be scaled to 10 instances, but an app can be set to use only five.
@@ -125,9 +125,12 @@ Per-app scaling is a feature that's enabled in both global Azure regions and [Ap
 Follow these steps to configure high-density hosting for your apps:
 
 1. Designate an App Service plan as the high-density plan and scale it out to the desired capacity.
+
 1. Set the `PerSiteScaling` flag to true on the App Service plan.
+
 1. New apps are created and assigned to that App Service plan with the `numberOfWorkers` property set to *1*.
    - Using this configuration yields the highest density possible.
+
 1. The number of workers can be configured independently per app to grant additional resources as needed. For example:
    - A high-use app can set `numberOfWorkers` to *3* to have more processing capacity for that app.
    - Low-use apps would set `numberOfWorkers` to *1*.