improvements to tone as advised by Acrolinx

Author: apwestgarth

articles/app-service/overview-arc-integration.md

@@ -33,7 +33,7 @@ The following public preview limitations apply to App Service Kubernetes environ
 | Feature: Key vault references                           | Not available (depends on managed identities)                                         |
 | Feature: Pull images from ACR with managed identity     | Not available (depends on managed identities)                                         |
 | Feature: In-portal editing for Functions and Logic Apps | Not available                                                                         |
-| Feature: Portal listing of Functions or keys            | Not available if cluster is not publicly reachable                                    |
+| Feature: Portal listing of Functions or keys            | Not available if cluster isn't publicly reachable                                    |
 | Feature: FTP publishing                                 | Not available                                                                         |
 | Logs                                                    | Log Analytics must be configured with cluster extension; not per-site                 |
 
@@ -82,23 +82,23 @@ App Service on Azure Arc is free during the public preview.
 
 ### Are both Windows and Linux apps supported?
 
-Only Linux-based apps are supported, both code and custom containers. Windows apps are not supported.
+Only Linux-based apps are supported, both code and custom containers. Windows apps aren't supported.
 
 ### Which built-in application stacks are supported?
 
 All built-in Linux stacks are supported.
 
 ### Are all app deployment types supported?
 
-FTP deployment is not supported. Currently `az webapp up` is also not supported. Other deployment methods are supported, including Git, ZIP, CI/CD, Visual Studio, and Visual Studio Code.
+FTP deployment isn't supported. Currently `az webapp up` is also not supported. Other deployment methods are supported, including Git, ZIP, CI/CD, Visual Studio, and Visual Studio Code.
 
 ### Which App Service features are supported?
 
-During the preview period, certain App Service features are being validated. When they're supported, their left navigation options in the Azure portal will be activated. Features that are not yet supported remain grayed out.
+During the preview period, certain App Service features are being validated. When they're supported, their left navigation options in the Azure portal will be activated. Features that aren't yet supported remain grayed out.
 
 ### Are all networking features supported?
 
-No. Networking features such as hybrid connections or Virtual Network integration, are not supported.  [Access restriction](app-service-ip-restrictions.md) support was added in April 2022. Networking should be handled directly in the networking rules in the Kubernetes cluster itself.
+No. Networking features such as hybrid connections or Virtual Network integration, aren't supported.  [Access restriction](app-service-ip-restrictions.md) support was added in April 2022. Networking should be handled directly in the networking rules in the Kubernetes cluster itself.
 
 ### Are managed identities supported?
 
@@ -112,15 +112,15 @@ All applications deployed with Azure App Service on Kubernetes with Azure Arc ar
 
 Logs for both system components and your applications are written to standard output. Both log types can be collected for analysis using standard Kubernetes tools. You can also configure the App Service cluster extension with a [Log Analytics workspace](../azure-monitor/logs/log-analytics-overview.md), and it sends all logs to that workspace.
 
-By default, logs from system components are sent to the Azure team. Application logs are not sent. You can prevent these logs from being transferred by setting `logProcessor.enabled=false` as an extension configuration setting. This configuration setting will also disable forwarding of application to your Log Analytics workspace. Disabling the log processor might impact time needed for any support cases, and you will be asked to collect logs from standard output through some other means.
+By default, logs from system components are sent to the Azure team. Application logs aren't sent. You can prevent these logs from being transferred by setting `logProcessor.enabled=false` as an extension configuration setting. This configuration setting will also disable forwarding of application to your Log Analytics workspace. Disabling the log processor might impact time needed for any support cases, and you will be asked to collect logs from standard output through some other means.
 
 ### What do I do if I see a provider registration error?
 
 When creating a Kubernetes environment resource, some subscriptions might see a "No registered resource provider found" error. The error details might include a set of locations and api versions that are considered valid. If this error message is returned, the subscription must be re-registered with the Microsoft.Web provider, an operation that has no impact on existing applications or APIs. To re-register, use the Azure CLI to run `az provider register --namespace Microsoft.Web --wait`. Then reattempt the Kubernetes environment command.
 
 ### Can I deploy the Application services extension on an ARM64 based cluster?
 
-ARM64 based clusters are not supported at this time.  
+ARM64 based clusters aren't supported at this time.  
 
 ### Which Kubernetes distributions can I deploy the extension on?