Fix wording in table

Author: sethmanheim

AKS-Arc/connectivity-modes-aks-local.md

@@ -31,14 +31,14 @@ The connectivity status of a cluster is determined by the time of the latest hea
 
 | AKS operation | Impact of temporary disconnection | Details | Workaround |
 | ------------- | ---------------------------------- |---------|------------|
-| Creating, updating, upgrading & deleting Kubernetes cluster | Not supported | Since Kubernetes CRUD operations are driven via Azure, you will not be able to perform any CRUD operation while disconnected. | No supported workaround |
-| Scaling the Kubernetes cluster | Partially supported | You will not be able to manually scale an existing nodepool or add a new nodepool to the Kubernetes cluster | Your Kubernetes cluster will scale dynamically if you've [enabled autoscalar](auto-scale-aks-arc.md) while creating the Kubernetes cluster. |
-| Access the Kubernetes cluster | Partially supported | You will not be able to use [Azure Entra](enable-authentication-microsoft-entra-id.md) and `az connectedk8s proxy` since these require connectivity to Azure. | [Retrieve admin kubeconfig](retrieve-admin-kubeconfig.md) to access the Kubernetes cluster. |
-| Viewing Kubernetes cluster status | Partially supported | You will not be able to use Azure portal or ARM APIs to view Kubernetes cluster status. | Use local tools such as [kubectl get](https://kubernetes.io/docs/reference/kubectl/quick-reference/#viewing-and-finding-resources). |
-| MetalLB Arc extension | Partially supported | Your load balancer will continue working but you will not be able to add/remove IP pools or update MetalLB configuration | No supported workaround |
-| AKS cluster and application observability | Partially supported | You will not be able to use Container Insights and [create diagnostic settings using Container Insights](kubernetes-monitor-audit-events.md#create-a-diagnostic-setting) since these require connectivity to Azure | Use [3rd party on-premises monitoring solutions](aks-monitor-logging.md).
-| SSH into the Kubernetes VMs | Supported | You will be able to SSH into Kubernetes VMs. | No workaround needed |
-| Collect logs for troubleshooting | Supported | You will be able to collect logs for troubleshooting issues. | No workaround needed |
+| Creating, updating, upgrading, and deleting Kubernetes clusters | Not supported | Since Kubernetes CRUD operations are driven by Azure, you can't perform any CRUD operations while disconnected. | No supported workaround |
+| Scaling the Kubernetes cluster | Partially supported | You can't manually scale an existing nodepool or add a new nodepool to the Kubernetes cluster. | Your Kubernetes cluster scales dynamically if you [enabled autoscalar](auto-scale-aks-arc.md) while creating the Kubernetes cluster. |
+| Access the Kubernetes cluster | Partially supported | You can't use [Azure Entra](enable-authentication-microsoft-entra-id.md) and `az connectedk8s proxy`, since these require connectivity to Azure. | [Retrieve admin kubeconfig](retrieve-admin-kubeconfig.md) to access the Kubernetes cluster. |
+| Viewing Kubernetes cluster status | Partially supported | You can't use the Azure portal or Azure Resource Manager APIs to view Kubernetes cluster status. | Use local tools such as [kubectl get](https://kubernetes.io/docs/reference/kubectl/quick-reference/#viewing-and-finding-resources). |
+| MetalLB Arc extension | Partially supported | Your load balancer continues working but you can't add or remove IP pools or update MetalLB configuration. | No supported workaround. |
+| AKS cluster and application observability | Partially supported | You can't use Container Insights and [create diagnostic settings using Container Insights](kubernetes-monitor-audit-events.md#create-a-diagnostic-setting), since these require connectivity to Azure. | Use [3rd party on-premises monitoring solutions](aks-monitor-logging.md). |
+| SSH into the Kubernetes VMs | Supported | You can SSH into Kubernetes VMs. | No workaround needed. |
+| Collect logs for troubleshooting | Supported | You can collect logs for troubleshooting issues. | No workaround needed. |
 
 ## Next steps