Acrolinx and update concept

Author: Michael Bender

articles/virtual-network-manager/TOC.yml

@@ -89,7 +89,7 @@
       href: how-to-configure-cross-tenant-cli.md
   - name: Monitoring
     items:
-    - name: configure Event Logs for Azure Virtual Network Manager
+    - name: Configure Event Logs for Azure Virtual Network Manager
       href: how-to-configure-event-logs.md
   - name: View applied configurations
     href: how-to-view-applied-configurations.md

articles/virtual-network-manager/concept-event-logs.md

@@ -10,7 +10,7 @@ ms.date: 04/12/2023
 
 # Event Log Options for Azure Virtual Network Manager
 
-Azure Virtual Network Manager uses Azure Monitor for telemetry collection and analysis like many other Azure services. Azure Virtual Network Manager provides event logs for each network manager that you can interact with through Azure Monitor’s Log Analytics tool in the Azure Portal, as well as through a storage account. You may also send these logs to an event hub or partner solution. 
+Azure Virtual Network Manager uses Azure Monitor for data collection and analysis like many other Azure services. Azure Virtual Network Manager provides event logs for each network manager. You can store and view event logs with Azure Monitor’s Log Analytics tool in the Azure portal, and through a storage account. You may also send these logs to an event hub or partner solution. 
 
 ## Supported log categories
 
@@ -20,7 +20,7 @@ Azure Virtual Network Manager currently provides the following log categories:
 
 ## Network group membership change attributes 
 
-This category emits one log per network group membership change. So, when a virtual network is added to or removed from a network group, a log is emitted correlating to that single addition or removal for that particular virtual network. The following attributes correspond to the logs that would be sent to your storage account; Log Analytics logs will have slightly different attributes. 
+This category emits one log per network group membership change. So, when a virtual network is added to or removed from a network group, a log is emitted correlating to that single addition or removal for that particular virtual network. The following attributes correspond to the logs that would be sent to your storage account; Log Analytics logs have slightly different attributes. 
 
 | Attribute | Description |
 |-----------|-------------|
@@ -55,19 +55,19 @@ Within the Sources attribute are several nested attributes:
 | Sources attributes | Description |
 |-------------------|-------------|
 | Type | Denotes whether the virtual network was added manually (StaticMembership) or conditionally via Azure Policy (Policy). |
-| StaticMemberId | If the Type value is StaticMembership, this property will appear. |
-| PolicyAssignmentId | If the Type value is Policy, this property will appear. ID of the Azure Policy assignment that associates the Azure Policy definition to the network group. |
-| PolicyDefinitionId | If the Type value is Policy, this property will appear. ID of the Azure Policy definition that contains the conditions for the network group’s membership. |
+| StaticMemberId | If the Type value is StaticMembership, this property appears. |
+| PolicyAssignmentId | If the Type value is Policy, this property appears. ID of the Azure Policy assignment that associates the Azure Policy definition to the network group. |
+| PolicyDefinitionId | If the Type value is Policy, this property appears. ID of the Azure Policy definition that contains the conditions for the network group’s membership. |
 
 ## Accessing logs
 
-Depending on how you'll consume event logs, you’ll need to set up a Log Analytics workspace or a storage account for storing your log events. 
+Depending on how you consume event logs, you need to set up a Log Analytics workspace or a storage account for storing your log events. 
 - Learn to [create a Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md).
 - Learn to [create a storage account](../storage/common/storage-account-create.md).
 
-When setting up a Log Analytics workspace or a storage account, you’ll need to select a region. If you’re using a storage account or [event hub](../event-hubs/event-hubs-create.md), it will need to be in the same region of the virtual network manager you’re accessing logs from. If you’re using a Log Analytics workspace, it can be in any region. 
+When setting up a Log Analytics workspace or a storage account, you need to select a region. If you’re using a storage account, it needs to be in the same region of the virtual network manager you’re accessing logs from. If you’re using a Log Analytics workspace, it can be in any region. 
 
-The network manager you’re accessing the logs of won’t need to belong to the same subscription as your Log Analytics workspace or storage account, but permissions may restrict your ability to access logs across different subscriptions. 
+The network manager accessing the events isn't required to be in the same subscription as the Log Analytics workspace or the storage account used for storage, but permissions may restrict your ability to access logs across different subscriptions. 
 
 > [!NOTE]
 > At least one virtual network must be added or removed from a network group in order to generate logs. A log will generate for this event a couple minutes after network group membership change occurs.