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

Author: ShawnJackson

articles/app-service/app-service-key-vault-references.md

@@ -58,7 +58,7 @@ If your vault is configured with [network restrictions](/azure/key-vault/general
 
 ### Access vaults with a user-assigned identity
 
-Some apps need to reference secrets at creation time, when a system-assigned identity isn't available yet. In these cases, a you can create a user-assigned identity and give it access to the vault in advance.
+Some apps need to reference secrets at creation time, when a system-assigned identity isn't available yet. In these cases, you can create a user-assigned identity and give it access to the vault in advance.
 
 After you grant permissions to the user-assigned identity, follow these steps:
 
@@ -124,7 +124,7 @@ Alternatively:
 
 Apps can use the `WEBSITE_CONTENTAZUREFILECONNECTIONSTRING` application setting to mount [Azure Files](../storage/files/storage-files-introduction.md) as the file system. This setting has validation checks to ensure that the app can be properly started.
 
-The platform relies on having a content share within Azure Files, and it assumes a default name unless one is specified via the `WEBSITE_CONTENTSHARE` setting. For any requests that modify these settings, the platform validates if this content share exists. If the content share doesn't exist, the plaform tries to create it. If the platform can't locate or create the content share, it blocks the request.
+The platform relies on having a content share within Azure Files, and it assumes a default name unless one is specified via the `WEBSITE_CONTENTSHARE` setting. For any requests that modify these settings, the platform validates if this content share exists. If the content share doesn't exist, the platform tries to create it. If the platform can't locate or create the content share, it blocks the request.
 
 When you use Key Vault references in this setting, the validation check fails by default, because the secret itself can't be resolved while during processing of the incoming request. To avoid this problem, you can skip the validation by setting `WEBSITE_SKIP_CONTENTSHARE_VALIDATION` to `1`. This setting tells App Service to bypass all checks, and it doesn't create the content share for you. You should ensure that it's created in advance.
 

articles/app-service/configure-common.md

@@ -60,7 +60,7 @@ App settings are always encrypted when they're stored (encrypted at rest).
 1. In the dialog, you can [stick the setting to the current slot](deploy-staging-slots.md#which-settings-are-swapped).
 
     > [!NOTE]
-    > In a default Linux app service or a custom Linux container, any nested JSON key structure in the app setting name needs to be configured differently for the key name. Replace any colon (`:`) with a double underscore (`__`), and replace any period (`.`) with with a single underscore (`_`). For example, `ApplicationInsights:InstrumentationKey` needs to be configured in App Service as `ApplicationInsights__InstrumentationKey` for the key name.
+    > In a default Linux app service or a custom Linux container, any nested JSON key structure in the app setting name needs to be configured differently for the key name. Replace any colon (`:`) with a double underscore (`__`), and replace any period (`.`) with a single underscore (`_`). For example, `ApplicationInsights:InstrumentationKey` needs to be configured in App Service as `ApplicationInsights__InstrumentationKey` for the key name.
 
 1. When you finish, select **Apply**. Don't forget to also select **Apply** on the **Environment variables** page.
 
@@ -227,7 +227,7 @@ At runtime, connection strings are available as environment variables, prefixed
 - Redis cache: `REDISCACHECONNSTR_`
 
 > [!NOTE]
-> .NET apps that target PostgreSQL, Notification Hubs, Service Bus, Event Hubs, Azure Cosmos DB, and Redis cache should set the connection string to **Custom** as workaround for a [known issue in .NET EnvironmentVariablesConfigurationProvider](https://github.com/dotnet/runtime/issues/36123).
+> .NET apps that target PostgreSQL, Notification Hubs, Service Bus, Event Hubs, Azure Cosmos DB, and Redis cache should set the connection string to **Custom** as a workaround for a [known issue in .NET EnvironmentVariablesConfigurationProvider](https://github.com/dotnet/runtime/issues/36123).
 
 For example, a MySQL connection string named *connectionstring1* can be accessed as the environment variable `MYSQLCONNSTR_connectionString1`. For steps that are specific to each language stack, see:
 
@@ -450,7 +450,7 @@ Here, you can configure some common settings for the app. Some settings require
   - **FTP state**: Allow only FTPS, or disable FTP altogether.
   - **HTTP version**: Set to **2.0** to enable support for the [HTTPS/2](https://wikipedia.org/wiki/HTTP/2) protocol.
     > [!NOTE]
-    > Most modern browsers support the HTTP/2 protocol over TLS only, while non-encrypted traffic continues to use HTTP/1.1. To ensure that client browsers connect to your app with HTTP/2, secure your custom DNS name. For more information, see [Provide security for a custom DNS name with a TLS/SSL binding in App Service](configure-ssl-bindings.md).
+    > Most modern browsers support the HTTP/2 protocol over TLS only, while unencrypted traffic continues to use HTTP/1.1. To ensure that client browsers connect to your app with HTTP/2, secure your custom DNS name. For more information, see [Provide security for a custom DNS name with a TLS/SSL binding in App Service](configure-ssl-bindings.md).
   - **Web sockets**: Configure for [ASP.NET SignalR] or [socket.io](https://socket.io/), for example.
   - **Always On**: Turn on if you want to keep the app loaded even when there's no traffic.
 
@@ -489,7 +489,7 @@ To show the existing settings, use the [Get-AzWebApp](/powershell/module/az.webs
 -----
 ## Configure default documents
 
-The default document is the webpage that's displayed at the root URL of an App Service app. The first matching file in the list is used. If the app uses modules that route based on URL instead of serving static content, there's no need for default documents.
+The default document is the webpage that appears at the root URL of an App Service app. The first matching file in the list is used. If the app uses modules that route based on URL instead of serving static content, there's no need for default documents.
 
 The setting to configure default documents is only for Windows apps.
 

articles/app-service/overview-hosting-plans.md

@@ -106,7 +106,7 @@ If you integrate App Service with another Azure service, you might need to consi
 
 ## Scaling for capabilities or features
 
-You can sale your App Service plan up or down at any time. It's as simple as changing the pricing tier of the plan. You can choose a lower pricing tier at first, and then scale up later when you need more App Service features.
+You can scale your App Service plan up or down at any time. It's as simple as changing the pricing tier of the plan. You can choose a lower pricing tier at first, and then scale up later when you need more App Service features.
 
 For example, you can start testing your web app in a Free-tier App Service plan and pay nothing. When you add your [custom DNS name](app-service-web-tutorial-custom-domain.md) to the web app, just scale your plan up to the Shared tier. Later, when you want to [create a TLS binding](configure-ssl-bindings.md), scale your plan up to the Basic tier. When you want to have [staging environments](deploy-staging-slots.md), scale up to the Standard tier. When you need more cores, memory, or storage, scale up to a bigger VM size in the same tier.