acro

Author: msangapu-msft

articles/app-service/tutorial-troubleshoot-monitor.md

@@ -1,6 +1,6 @@
 ---
 title: 'Tutorial: Troubleshoot with Azure Monitor'
-description: Learn how Azure Monitor and Log Analytics helps you monitor your App Service web app. Azure Monitor maximizes the availability by delivery a comprehensive solution for monitoring your environments.
+description: Learn how Azure Monitor and Log Analytics help you monitor your App Service web app. Azure Monitor maximizes the availability by delivery a comprehensive solution for monitoring your environments.
 author: msangapu-msft
 ms.author: msangapu
 ms.topic: tutorial
@@ -9,7 +9,7 @@ ms.date: 06/20/2020
 ---
 # Tutorial: Troubleshoot an App Service app with Azure Monitor
 
-This tutorial shows how to troubleshoot an [App Service](overview.md) app using [Azure Monitor](../azure-monitor/overview.md). The sample app includes code meant to exhaust memory and cause HTTP 500 errors, so you can diagnose and fix the problem using Azure Monitor. When you're finished, you'll have a sample app running on App Service on Linux integrated with [Azure Monitor](../azure-monitor/overview.md).
+This tutorial shows how to troubleshoot an [App Service](overview.md) app using [Azure Monitor](../azure-monitor/overview.md). The sample app includes code meant to exhaust memory and cause HTTP 500 errors, so you can diagnose and fix the problem using Azure Monitor. When you're finished, you have a sample app running on App Service on Linux integrated with [Azure Monitor](../azure-monitor/overview.md).
 
 [Azure Monitor](../azure-monitor/overview.md) maximizes the availability and performance of your applications and services by delivering a comprehensive solution for collecting, analyzing, and acting on telemetry from your cloud and on-premises environments.
 
@@ -26,7 +26,7 @@ You can follow the steps in this tutorial on macOS, Linux, Windows.
 
 ## Prerequisites
 
-To complete this tutorial, you'll need:
+To complete this tutorial, you need:
 
 - [Azure subscription](https://azure.microsoft.com/free/?ref=microsoft.com&utm_source=microsoft.com&utm_medium=docs&utm_campaign=visualstudio)
 
@@ -36,7 +36,7 @@ To complete this tutorial, you'll need:
 
 ## Create Azure resources
 
-First, you run several commands locally to setup a sample app to use with this tutorial. The commands create Azure resources, create a deployment user, and deploy the sample app to Azure. You'll be prompted for the password supplied as a part of the creation of the deployment user. 
+First, you run several commands locally to set up a sample app to use with this tutorial. The commands create Azure resources, create a deployment user, and deploy the sample app to Azure. You're prompted for the password supplied as a part of the creation of the deployment user. 
 
 ```azurecli
 az group create --name myResourceGroup --location "South Central US"
@@ -55,7 +55,7 @@ git push azure main
 
 ### Create a Log Analytics Workspace
 
-Now that you've deployed the sample app to Azure App Service, you'll configure monitoring capability to troubleshoot the app when problems arise. Azure Monitor stores log data in a Log Analytics workspace. A workspace is a container that includes data and configuration information.
+Now that you've deployed the sample app to Azure App Service, you configure monitoring capability to troubleshoot the app when problems arise. Azure Monitor stores log data in a Log Analytics workspace. A workspace is a container that includes data and configuration information.
 
 In this step, you create a Log Analytics workspace to configure Azure Monitor with your app.
 
@@ -93,21 +93,21 @@ az monitor diagnostic-settings create --resource $resourceID \
 
 Browse to `http://<app-name>.azurewebsites.net`.
 
-The sample app, ImageConverter, converts included images from `JPG` to `PNG`. A bug has been deliberately placed in the code for this tutorial. If you select enough images, the the app produces a HTTP 500 error during image conversion. Imagine this scenario wasn't considered during the development phase. You'll use Azure Monitor to troubleshoot the error.
+The sample app, ImageConverter, converts included images from `JPG` to `PNG`. A bug has been deliberately placed in the code for this tutorial. If you select enough images, the app produces an HTTP 500 error during image conversion. Imagine this scenario wasn't considered during the development phase. You'll use Azure Monitor to troubleshoot the error.
 
 ### Verify the app works
 
 To convert images, click `Tools` and select `Convert to PNG`.
 
 ![Click `Tools` and select `Convert to PNG`](./media/tutorial-azure-monitor/sample-monitor-app-tools-menu.png)
 
-Select the first two images and click `convert`. This will convert successfully.
+Select the first two images and click `convert`. This converts successfully.
 
 ![Select the first two images](./media/tutorial-azure-monitor/sample-monitor-app-convert-two-images.png)
 
 ### Break the app
 
-Now that you've verified the app by converting two images successfully, we'll try to convert the first five images.
+Now that you've verified the app by converting two images successfully, we try to convert the first five images.
 
 ![Convert first five images](./media/tutorial-azure-monitor/sample-monitor-app-convert-five-images.png)
 
@@ -165,7 +165,7 @@ AppServiceConsoleLogs |
 where ResultDescription  contains "error" 
 ```
 
-In the `ResultDescription` column, you'll see the following error:
+In the `ResultDescription` column, you see the following error:
 
 ```output
 PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted 
@@ -213,7 +213,7 @@ In the local directory, open the `process.php` and look at line 20.
 imagepng($imgArray[$x], $filename);
 ```
 
-The first argument, `$imgArray[$x]`, is a variable holding all JPGs (in-memory) needing conversion. However, `imagepng` only needs the image being converted and not all images. Pre-loading images is not necessary and may be causing the memory exhaustion, leading to HTTP 500s. Let's update the code to load images on-demand to see if it resolves the issue. Next, you will improve the code to address the memory problem.
+The first argument, `$imgArray[$x]`, is a variable holding all JPGs (in-memory) needing conversion. However, `imagepng` only needs the image being converted and not all images. Pre-loading images is not necessary and may be causing the memory exhaustion, leading to HTTP 500s. Let's update the code to load images on-demand to see if it resolves the issue. Next, you improve the code to address the memory problem.
 
 ## Fix the app