add a Q&A about AMA/Arc agents limitation

Author: halkazwini

articles/network-watcher/frequently-asked-questions.yml

@@ -6,7 +6,7 @@ metadata:
   ms.author: halkazwini
   ms.service: network-watcher
   ms.topic: faq
-  ms.date: 02/15/2024
+  ms.date: 03/12/2024
 title: "Network Watcher frequently asked questions (FAQ)"
 summary: |
   This article provides answers to some of the frequently asked questions asked about Azure Network Watcher.
@@ -164,11 +164,9 @@ sections:
           There's no protocol selection option in connection monitor (classic). Tests in connection monitor (classic) only use the TCP protocol, and that's why, during the migration, we create a TCP configuration in tests in the new connection monitor.
 
       - question: |
-          Are there current limitations to using AMA and Arc Agents with connection monitor?
+          Are there any limitations to using Azure Monitor and Arc Agents with connection monitor?
         answer: |
-          There is currently a regional boundary when an endpoint uses AMA and Arc agents with the associated log analytics workspace. As a result, this requires the associated log analytics workspace to be in the same region as the Arc endpoint. Data ingested into individual workspaces can be unionized for a single view, see [Query data across Log Analytics workspaces, applications, and resources in Azure Monitor](../azure-monitor/logs/cross-workspace-query.md).
-          
-          
+          There is currently a regional boundary when an endpoint uses Azure Monitor and Arc agents with the associated Log Analytics workspace. As a result to this limitation, the associated Log Analytics workspace must be in the same region as the Arc endpoint. Data ingested into individual workspaces can be unionized for a single view, see [Query data across Log Analytics workspaces, applications, and resources in Azure Monitor](../azure-monitor/logs/cross-workspace-query.md).
 
   - name: Flow logs
     questions: