edit pass: content-pattern-and-metadata-edits-for-app-service-376111

Author: ShawnJackson

articles/app-service/overview-diagnostics.md

@@ -12,7 +12,7 @@ ms.custom: UpdateFrequency3
 ---
 # Diagnostics in Azure App Service
 
-When you're running a web application, you want to be prepared for any problems that might arise. Such problems can range from 500 errors to your users telling you that your site is down. Azure App Service diagnostics is an interactive experience to help you troubleshoot your app with no configuration required. If you have problems with your app, App Service diagnostics points out what's wrong and guides you to the right information to more easily and quickly troubleshoot and resolve the problem.
+When you're running a web application, you want to be prepared for any problems that might arise. Such problems can range from HTTP 500 errors to your users telling you that your site is down. Azure App Service diagnostics is an interactive experience to help you troubleshoot your app with no configuration required. If you have problems with your app, App Service diagnostics points out what's wrong and guides you to the right information to more easily and quickly troubleshoot and resolve the problem.
 
 Although this experience is most helpful when you're having problems with your app within the last 24 hours, all the diagnostic graphs are always available for you to analyze.
 
@@ -94,7 +94,7 @@ The tiles or the **Troubleshoot** link shows the available diagnostics for the c
 
 To investigate the problem further, you can select a topic and view more details in a diagnostic report. These details are often supplemented with graphs and Markdown.
 
-The diagnostic report can be a powerful tool for pinpointing the problem with your app. The following example is the **Web App Down** report from **Availability and Performance**.
+The diagnostic report can be a powerful tool for pinpointing the problem with your app. The following example is the **Web App Down** report in **Availability and Performance**.
 
 :::image type="content" source="./media/app-service-diagnostics/full-diagnostic-report-5.png" alt-text="Screenshot that shows the Web App Down diagnostic report in the portal.":::
 
@@ -130,7 +130,7 @@ Proactive CPU monitoring helps you take action when your app or a child process
 
 ### Auto-healing
 
-Auto-healing is a mitigation action that you can take when your app is having unexpected behavior. You can set your own rules based on request count, slow request, memory limit, and HTTP status code to trigger mitigation actions. Use the tool to temporarily mitigate an unexpected behavior until you find the root cause.
+Auto-healing is a mitigation action that you can take when your app has unexpected behavior. You can set your own rules based on request count, slow request, memory limit, and HTTP status code to trigger mitigation actions. Use the tool to temporarily mitigate an unexpected behavior until you find the root cause.
 
 The tool is currently available for Windows web apps, Linux web apps, and Linux custom containers. Supported conditions and mitigation vary, depending on the type of the web app. For more information, see the blog posts [Announcing the New Auto Healing Experience in App Service Diagnostics](https://azure.github.io/AppService/2018/09/10/Announcing-the-New-Auto-Healing-Experience-in-App-Service-Diagnostics.html) and [Announcing Auto Heal for Linux](https://azure.github.io/AppService/2021/04/21/Announcing-Autoheal-for-Azure-App-Service-Linux.html).
 

articles/app-service/overview-local-cache.md

@@ -24,7 +24,7 @@ ms.collection: ce-skilling-ai-copilot
 >
 > To find Copilot in Azure, on the [Azure portal](https://portal.azure.com) toolbar, select **Copilot**.
 
-Azure App Service content is stored on Azure Storage and is exposed as a durable content share. This design works with various apps and has the following attributes:  
+Azure App Service content is stored in Azure Storage and is exposed as a durable content share. This design works with various apps and has the following attributes:  
 
 - The content is shared across multiple virtual machine (VM) instances of the app.
 - The content is durable, and running apps can modify it.
@@ -37,7 +37,7 @@ The local cache feature in Azure App Service provides a web role view of your co
 
 Apps running with a local cache benefit in these ways:
 
-- They're immune to latencies associated with accessing content on Azure Storage.
+- They're immune to latencies associated with accessing content in Azure Storage.
 - Problems with connecting to the storage don't affect them, because the read-only copy is cached locally.
 - They experience fewer app restarts from changes in the storage share.
 
@@ -127,7 +127,7 @@ Sticky settings are tied to the slot. When the staging slot is swapped into prod
 
 ### What if I exceed the size limit for the local cache?
 
-If the copied files exceed the size limit of the local cache, the app reverts to reading from the remote share. The following table shows the details.
+If the copied files exceed the size limit for the local cache, the app reverts to reading from the remote share. The following table shows the details.
 
 | Local cache size | Copied files         | Result                                                                                          |
 | -------------------- | ------------------------ | --------------------------------------------------------------------------------------------------- |

articles/app-service/provision-resource-bicep.md

@@ -15,7 +15,7 @@ In this quickstart, you get started with [Azure App Service](overview.md) by dep
 
 Bicep is a domain-specific language (DSL) that uses declarative syntax to deploy Azure resources. It provides concise syntax, reliable type safety, and support for code reuse.
 
-You can use Bicep instead of JSON to develop your Azure Resource Manager templates ([ARM templates](../azure-resource-manager/templates/overview.md)). The JSON syntax to create an ARM template can be verbose and require complicated expressions. Bicep syntax reduces that complexity and improves the development experience. Bicep is a transparent abstraction over ARM template JSON and doesn't lose any of the JSON template capabilities. During deployment, the Bicep CLI transpiles a Bicep file into ARM template JSON.
+You can use Bicep instead of JSON to develop your [Azure Resource Manager templates (ARM templates)](../azure-resource-manager/templates/overview.md). The JSON syntax to create an ARM template can be verbose and require complicated expressions. Bicep syntax reduces that complexity and improves the development experience. Bicep is a transparent abstraction over ARM template JSON and doesn't lose any of the JSON template capabilities. During deployment, the Bicep CLI transpiles a Bicep file into ARM template JSON.
 
 ## Prerequisites
 
@@ -27,12 +27,12 @@ To effectively create resources by using Bicep, you need to set up a Bicep [deve
 
 ::: zone pivot="app-service-bicep-linux"
 
-This quickstart use the following template. It deploys an App Service plan and an App Service app on Linux. It also deploys a sample Node.js "Hello World" app from the [Azure Samples](https://github.com/Azure-Samples) repo.
+This quickstart uses the following template. It deploys an App Service plan and an App Service app on Linux. It also deploys a sample Node.js "Hello World" app from the [Azure Samples](https://github.com/Azure-Samples) repo.
 
 ```bicep
-param webAppName string = uniqueString(resourceGroup().id) // Generate unique String for web app name
-param sku string = 'F1' // The SKU of App Service Plan
-param linuxFxVersion string = 'node|14-lts' // The runtime stack of web app
+param webAppName string = uniqueString(resourceGroup().id) // Generate a unique string for the web app name
+param sku string = 'F1' // Tier of the App Service plan
+param linuxFxVersion string = 'node|14-lts' // Runtime stack of the web app
 param location string = resourceGroup().location // Location for all resources
 param repositoryUrl string = 'https://github.com/Azure-Samples/nodejs-docs-hello-world'
 param branch string = 'main'
@@ -95,9 +95,9 @@ The template contains the following parameters that are predefined for your conv
 
 Copy and paste the template to your preferred editor or IDE. Then save the file to your local working directory.
 
-Here, you use the Azure CLI to deploy the template. You can also use the Azure portal, Azure PowerShell, and the REST API. To learn about other deployment methods, see [Deploy Bicep files with the Azure CLI](../azure-resource-manager/bicep/deploy-cli.md).
+Here, you use the Azure CLI to deploy the template. You can also use the Azure portal, Azure PowerShell, or the REST API. To learn about other deployment methods, see [Deploy Bicep files with the Azure CLI](../azure-resource-manager/bicep/deploy-cli.md).
 
-The following code creates a resource group, an App Service plan, and a web app. A default resource group, App Service plan, and location are set for you. Replace `<app-name>` with a globally unique app name. Valid characters are `a-z`, `0-9`, and `-`.
+The following code creates a resource group, an App Service plan, and a web app. A default resource group, App Service plan, and location are set for you. Replace `<app-name>` with a globally unique app name. Valid characters are `a-z`, `0-9`, and a hyphen (`-`).
 
 Open a terminal where the Azure CLI is installed. Run this code to create a Node.js app on Linux:
 
@@ -125,11 +125,11 @@ To deploy a different language stack, update `linuxFxVersion` with appropriate v
 This quickstart uses the following template. It deploys an App Service plan and an App Service app on Windows. It also deploys a sample .NET "Hello World" app from the [Azure Samples](https://github.com/Azure-Samples) repo.
 
 ```bicep
-param webAppName string = uniqueString(resourceGroup().id) // generate unique name for web app
-param location string = resourceGroup().location // location for all resources
-param sku string = 'P1V3' // The SKU of App Service Plan
-param dockerContainerImage string = 'mcr.microsoft.com/dotnet/framework/samples:aspnetapp' // sample .NET app
-var appServicePlanName = toLower('ASP-${webAppName}') // generate unique name for App Service Plan
+param webAppName string = uniqueString(resourceGroup().id) // Generate a unique name for the web app
+param location string = resourceGroup().location // Location for all resources
+param sku string = 'P1V3' // Tier of the App Service plan
+param dockerContainerImage string = 'mcr.microsoft.com/dotnet/framework/samples:aspnetapp' // Sample .NET app
+var appServicePlanName = toLower('ASP-${webAppName}') // Generate a unique name for the App Service plan
 
 resource appServicePlan 'Microsoft.Web/serverfarms@2021-02-01' = {
   name: appServicePlanName
@@ -181,9 +181,9 @@ The template contains the following parameters that are predefined for your conv
 
 Copy and paste the template to your preferred editor or IDE. Then save the file to your local working directory.
 
-Here, you use the Azure CLI to deploy the template. You can also use the Azure portal, Azure PowerShell, and the REST API. To learn about other deployment methods, see [Deploy Bicep files with the Azure CLI](../azure-resource-manager/bicep/deploy-cli.md).
+Here, you use the Azure CLI to deploy the template. You can also use the Azure portal, Azure PowerShell, or the REST API. To learn about other deployment methods, see [Deploy Bicep files with the Azure CLI](../azure-resource-manager/bicep/deploy-cli.md).
 
-The following code creates a resource group, an App Service plan, and a web app. A default resource group, App Service plan, and location are set for you. Replace `<app-name>` with a globally unique app name. Valid characters are `a-z`, `0-9`, and `-`.
+The following code creates a resource group, an App Service plan, and a web app. A default resource group, App Service plan, and location are set for you. Replace `<app-name>` with a globally unique app name. Valid characters are `a-z`, `0-9`, and a hyphen (`-`).
 
 Open a terminal where the Azure CLI is installed. Run this code to create a .NET app:
 

articles/app-service/troubleshoot-http-502-http-503.md

@@ -15,7 +15,7 @@ author: msangapu-msft
 
 HTTP "502 Bad Gateway" and "503 Service Unavailable" are common errors that you can get when you try to open your app that's hosted in [Azure App Service](./overview.md). This article helps you troubleshoot these errors.
 
-If you need more help at any point in this article, you can contact the Azure experts on [the MSDN Azure and the Stack Overflow forums](https://azure.microsoft.com/support/forums/). Alternatively, you can file an Azure support incident on the [Azure Support site](https://azure.microsoft.com/support/options/) by selecting **Get Support**.
+If you need more help at any point in this article, you can contact the Azure experts on [the MSDN Azure and Stack Overflow forums](https://azure.microsoft.com/support/forums/). Alternatively, you can file an Azure support incident on the [Azure Support site](https://azure.microsoft.com/support/options/) by selecting **Get Support**.
 
 The cause of these errors is often an application-level problem, such as:
 
@@ -99,7 +99,7 @@ In Azure App Service, for increased performance and throughput, you can adjust t
 
 For more information on scaling, see [Scale an app in Azure App Service](manage-scale-up.md).
 
-Additionally, you can choose to run your application on more than one instance. This choice not only provides you with more processing capability, but also gives you some amount of fault tolerance. If the process goes down on one instance, the other instance continues to serve requests.
+Additionally, you can choose to run your application on more than one instance. This choice not only provides you with more processing capability but also gives you some amount of fault tolerance. If the process goes down on one instance, the other instance continues to serve requests.
 
 You can set the scaling to be manual or automatic.
 

articles/app-service/web-sites-monitor.md

@@ -22,11 +22,7 @@ Apps that are hosted in App Service are subject to certain limits on the resourc
 [!INCLUDE [app-service-dev-test-note](../../includes/app-service-dev-test-note.md)]
 
 If the app is hosted in a Free or Shared plan, quotas define the limits
-on the resources that the app can use.
-
-If the app is hosted in a Basic, Standard, or Premium plan, the limits on the resources that it can use are set by the *size* (small, medium, large) and *instance count* (1, 2, 3, and so on) of the App Service plan.
-
-Quotas for apps in a Free or Shared plan are:
+on the resources that the app can use. Quotas for apps in a Free or Shared plan are:
 
 | Quota | Description |
 | --- | --- |
@@ -36,7 +32,7 @@ Quotas for apps in a Free or Shared plan are:
 | **Bandwidth** | The total amount of outgoing bandwidth allowed for this app in a day. This quota resets every 24 hours at midnight UTC. |
 | **Filesystem** | The total amount of storage allowed. |
 
-The only quota applicable to apps that are hosted in a Basic, Standard, or Premium plan is **Filesystem**.
+If the app is hosted in a Basic, Standard, or Premium plan, the limits on the resources that it can use are set by the *size* (small, medium, large) and *instance count* (1, 2, 3, and so on) of the App Service plan. The only quota applicable to apps that are hosted in a Basic, Standard, or Premium plan is **Filesystem**.
 
 For more information about the specific quotas, limits, and features available to the App Service tiers, see [Azure App Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-app-service-limits).
 
@@ -54,7 +50,7 @@ You can increase or remove quotas from your app by upgrading your App Service pl
 
 ## <a name = "understand-metrics"></a> Metrics
 
-Metrics provide information about the app or the App Service plan's behavior. App Service plan metrics are available only for plans in Basic, Standard, Premium, and Isolated tiers.
+Metrics provide information about the app's or the App Service plan's behavior. App Service plan metrics are available only for plans in Basic, Standard, Premium, and Isolated tiers.
 
 For a list of available metrics for apps or for App Service plans, see [Supported metrics for Microsoft.Web](monitor-app-service-reference.md#supported-metrics-for-microsoftweb).
 
@@ -69,7 +65,7 @@ Two metrics reflect CPU usage:
 
 - **CPU Time**: Useful for apps hosted in Free or Shared plans, because one of their quotas is defined in CPU minutes that the app uses.
 
-- **CPU percentage**: Useful for apps hosted in Basic, Standard, and Premium plans, because they can be scaled out. CPU percentage is a good indication of the overall usage across instances.
+- **CPU Percentage**: Useful for apps hosted in Basic, Standard, and Premium plans, because they can be scaled out. CPU percentage is a good indication of the overall usage across instances.
 
 ### <a name = "metrics-granularity-and-retention-policy"></a> Retention policy
 
@@ -98,6 +94,6 @@ To learn more about metrics, see [Azure Monitor data platform](/azure/azure-moni
 
 Metrics for an app or an App Service plan can be connected to alerts. For more information, see [Alerts](monitor-app-service.md#alerts).
 
-App Service apps hosted in Basic or higher App Service plans support autoscale. With autoscale, you can configure rules that monitor the App Service plan metrics. Rules can increase or decrease the instance count, which can provide additional resources as needed. Rules can also help you save money when the app is overprovisioned.
+Apps hosted in Basic or higher App Service plans support autoscale. With autoscale, you can configure rules that monitor the App Service plan metrics. Rules can increase or decrease the instance count, which can provide additional resources as needed. Rules can also help you save money when the app is overprovisioned.
 
 For more information about autoscale, see [Get started with autoscale in Azure](/azure/azure-monitor/autoscale/autoscale-get-started) and [Best practices for autoscale](/azure/azure-monitor/autoscale/autoscale-best-practices).