review-2

Author: v-thpra

learn-pr/azure/stage-deploy-app-service-deployment-slots/includes/3-exercise-create-deployment-slots.md

@@ -33,11 +33,13 @@ Start by creating a new web app resource in the Azure portal.
     | Windows Plan | Accept default. |
     | Sku and size | Accept default. |
 
+1. Select **Next : Database**.
+1. 
 1. Select **Next : Deployment**.
 
 1. Select **Next : Networking**.
 
-1. Select **Next : Monitoring**, and enter the following value for the setting.
+1. Select **Next : Monitoring + secure**, and enter the following value for the setting.
 
     | Setting | Value |
     |---|---|
@@ -108,7 +110,7 @@ We're going to use git to deploy the source code to the web app's production slo
     :::image type="content" source="../media/3-copy-git-clone-url.png" alt-text="Screenshot of the Essentials section, where you Copy the git clone URL." lightbox="../media/3-copy-git-clone-url.png":::
 
     > [!NOTE]
-    > If you don't see a git clone URL where it's shown in the preceding screenshot, refresh the portal.
+    > If you don't see a git clone URL in the location shown in the preceding screenshot, refresh the portal.
 
 1. Hover over the  **Git clone url** and select the *Copy to clipboard* icon. This value also contains your deployment username.
 
@@ -147,7 +149,7 @@ For your web app, you created one slot, the production slot, and you deployed so
 
 1. In the command bar, select **+ Add Slot**. The **Add a slot** pane appears.
 
-1. In the **Name** field, enter *Staging*, accept the default for **Clone settings from**, and then select **Add**.
+1. In the **Name** field, enter *staging*, accept the default for **Clone settings from**, and then select **Add**.
 
 1. After the deployment slot is successfully created, select **Close**.
 

learn-pr/azure/stage-deploy-app-service-deployment-slots/includes/4-deploy-a-web-app-by-swapping-deployment-slots.md

@@ -8,7 +8,7 @@ Here, you learn the correct configuration to swap the web app into production.
 
 When you swap two slots, the app's configuration travels to the new slot along with the app. You can override this behavior for individual application settings and configuration strings by configuring them as **slot settings**.
 
-Suppose, for example, you have two databases. You use one for production and the other for acceptance testing. You always want the app version in the staging slot to use the testing database. The app version in the production slot should always use the production database. To achieve this, you can configure the database connection string as a slot setting.
+Suppose, for example, you have two databases. You use one for production and the other for acceptance testing. You always want the app version in the staging slot to use the testing database. The app version in the production slot should always use the production database. You can achieve this overall configuration by configuring the database connection string as a slot setting.
 
 ### Configure slot settings
 
@@ -40,15 +40,15 @@ To swap two slots in the Azure portal:
 
 ## Understand the slot-swapping preview
 
-When you swap slots, the settings in the target slot (which is typically the production slot) are applied to the app version in the source slot before the hostnames are swapped. You might discover problems at this point. For example, if the database connection string is configured as a slot setting, the new version of the web app uses the existing production database. If you forgot to upgrade the database schema in the production database before the swap, you could see errors and exceptions when the new app version attempts to use the old schema.
+When you swap slots, the settings in the target slot (typically the production slot) are applied to the app version in the source slot, before the hostnames are swapped. You might discover problems at this point. For example, if the database connection string is configured as a slot setting, the new version of the web app uses the existing production database. If you forgot to upgrade the database schema in the production database before the swap, you could see errors and exceptions when the new app version attempts to use the old schema.
 
 To help you discover problems before your app goes live into production, Azure App Service offers a swap-with-preview feature. When you choose this option, the swap proceeds in two phases:
 
 - **Phase 1**: Slot settings from the target slot are applied to the web app in the source slot. Azure then warms up the source slot. At this point, the swap operation pauses so you can test the app in the source slot to make sure it works with the target slot configuration. If you find no problems, begin the next phase.
 - **Phase 2**: The hostnames for the two sites are swapped. The version of the app now in the source slot receives its slot settings.
 
 > [!IMPORTANT]
-> Test your web app thoroughly while it's in the staging slot. Eliminate code bugs and problems with non-slot settings. The swap-with-preview feature can only help you spot and eliminate problems caused by the production-slot settings. Make sure everything else is sound before you start any kind of swap into production.
+> Test your web app thoroughly while it's in the staging slot. Eliminate code bugs and problems with nonslot settings. The swap-with-preview feature can only help you spot and eliminate problems caused by the production-slot settings. Make sure everything else is sound before you start any kind of swap into production.
 
 ### Preview slot swapping
 

learn-pr/azure/stage-deploy-app-service-deployment-slots/includes/5-exercise-deploy-a-web-app-by-using-deployment-slots.md

@@ -14,13 +14,13 @@ To configure slot settings:
 
 1. Navigate to the **Configuration** pane for the deployment slot.
 
-1. Select **+ New application setting**. Add a new setting with the name **ENVIRONMENT_NAME**, and a value of **production**. Check the **deployment slot setting** box to make this a slot setting. Select **OK**.
+1. Select **+ New application setting**. Add a new setting with the name **ENVIRONMENT_NAME**, and a value of **production**. Check the **deployment slot setting** box to make this setting a slot setting. Select **OK**.
 
-1. Add another setting called **APP_VERSION**, and enter the value *1*. *Don't* make this a slot setting. Select **OK**.
+1. Add another setting called **APP_VERSION**, and enter the value *1*. *Don't* make this setting a slot setting. Select **OK**.
 
 1. In the top menu bar, select **Save**, then select **Continue**.
 
-1. Repeat the preceding steps on the **Staging** slot, but use the following values:
+1. Repeat the preceding steps on the **staging** slot, but use the following values:
 
     | Name | Value | Deployment slot setting |
     |---|---|---|
@@ -29,7 +29,7 @@ To configure slot settings:
 
 ## Swap the slots
 
-Now that you've tested version 2 of the web app in the staging slot, you can deploy it by swapping the slots. Follow these steps:
+Now that you tested version 2 of the web app in the staging slot, you can deploy it by swapping the slots. Follow these steps:
 
 1. To make sure you're configuring the production slot, select **All resources**, and then select the production slot of the web app.
 
@@ -47,7 +47,7 @@ Now that you've tested version 2 of the web app in the staging slot, you can dep
 
 ## Configure auto swap for the staging slot
 
-Suppose that now that you're using deployment slots, you want to enable continuous deployment. You do this by using the auto swap feature for your web app. In a system that uses auto swap, when you deploy new code to the staging slot, Azure automatically warms it up and deploys it to production by swapping the staging and production slots. To configure auto swap, follow these steps:
+Now that you're using deployment slots, you can use the auto swap feature for your web app to enable continuous deployment. When auto swap is enabled, you can deploy new code to the staging slot and Azure automatically warms it up and deploys it to production by swapping the staging and production slots. To configure auto swap, follow these steps:
 
 1. Go to the **Configuration** pane of the staging slot's web app and go to the **General settings** tab.
 
@@ -92,9 +92,9 @@ Now, you modify the code to create version 3 of the web app. When you deploy it
     git push staging
     ```
 
-    Wait for the deployment to finish. Near the end of the text output, you see a message that indicates that the deployment has requested an auto swap to the production slot.
+    Wait for the deployment to finish. Near the end of the text output, you see a message that indicates that the deployment requested an auto swap to the production slot.
 
-1. In the Azure portal, go to the **Overview** page for the production slot's web app, and select **Browse**. The third version of the web app appears on a new browser tab. If the old version is shown, you mightneed to wait briefly and then refresh the page. The swap operation is atomic and occurs instantly, but it takes App Service a few moments to prepare the swap operation before running it.
+1. In the Azure portal, go to the **Overview** page for the production slot's web app, and select **Browse**. The third version of the web app appears on a new browser tab. If the old version is shown, you might need to wait briefly and then refresh the page. The swap operation is atomic and occurs instantly, but it takes App Service a few moments to prepare the swap operation before running it.
 
 ## Roll back the new version
 
@@ -104,4 +104,4 @@ Suppose that deploying version 3 of your app to production revealed an unexpecte
 
 1. Swap the staging and production slots.
 
-1. When the swap finishes, on the **Overview** page, select **Browse** to view the app one last time. You'll see that version 2 was redeployed to production.
+1. When the swap finishes, on the **Overview** page, select **Browse** to view the app one last time. You can see that version 2 was redeployed to production.