Merge pull request #228611 from halkazwini/nw-nsg-flow2

tweak

Author: prmerger-automator[bot]

articles/network-watcher/network-watcher-nsg-flow-logging-overview.md

@@ -7,7 +7,7 @@ author: halkazwini
 ms.service: network-watcher
 ms.topic: conceptual
 ms.workload: infrastructure-services
-ms.date: 02/26/2023
+ms.date: 02/27/2023
 ms.author: halkazwini
 ms.custom: template-concept, engagement-fy23
 ---
@@ -53,7 +53,7 @@ Key properties of NSG flow logs include:
 - Logs are collected at 1-minute intervals through the Azure platform. They don't affect your Azure resources or network performance in any way.
 - Logs are written in JSON format and show outbound and inbound flows per network security group rule.
 - Each log record contains the network interface (NIC) that the flow applies to, 5-tuple information, the traffic decision, and (for version 2 only) throughput information.
-- NSG Flow logs have a retention feature that allows deleting the logs automatically up to a year after their creation.
+- NSG flow logs have a retention feature that allows deleting the logs automatically up to a year after their creation.
 
 > [!NOTE]
 > Retention is available only if you use [general-purpose v2 storage accounts](../storage/common/storage-account-overview.md#types-of-storage-accounts). 
@@ -63,15 +63,15 @@ Core concepts for flow logs include:
 - Software-defined networks are organized around virtual networks and subnets. You can manage the security of these virtual networks and subnets by using network security groups.
 - A network security group contains *security rules* that allow or deny network traffic to or from the Azure resources that the network security group is connected to. A network security group can be associated with a subnet or a network interface of a virtual machine (VM). For more information, see [Network security group overview](../virtual-network/network-security-groups-overview.md?toc=%2fazure%2fnetwork-watcher%2ftoc.json).
 - All traffic flows in your network are evaluated through the rules in the applicable network security group. The result of these evaluations is NSG flow logs. 
-- NSG Flow logs are collected through the Azure platform and don't require any change to your Azure resources.
+- NSG flow logs are collected through the Azure platform and don't require any change to your Azure resources.
 - There are two types of network security group rules: terminating and non-terminating. Each has different logging behaviors:
   - *Deny* rules are terminating. The network security group that's denying the traffic will log it in the flow logs. Processing in this case stops after any NSG denies traffic.
   - *Allow* rules are non-terminating. If the network security group allows the traffic, processing continues to the next network security group. The last network security group that allows traffic will log the traffic to the flow logs.
 - NSG flow logs are written to storage accounts. You can export, process, analyze, and visualize NSG flow logs by using tools like Network Watcher traffic analytics, Splunk, Grafana, and Stealthwatch.
 
 ## Log format
 
-NSG Flow logs include the following properties:
+NSG flow logs include the following properties:
 
 * `time`: Time when the event was logged.
 * `systemId`: System ID of the network security group.
@@ -342,7 +342,7 @@ To update parameters via command-line tools, use the same command that you used
 - [Read flow logs by using PowerShell functions](./network-watcher-read-nsg-flow-logs.md)
 - [Export NSG flow logs to Splunk](https://www.splunk.com/en_us/blog/platform/splunking-azure-nsg-flow-logs.html)
 
-NSG flow logs target network security groups and aren't displayed the same way as the other logs. NSG Flow logs are stored only in a storage account and follow the logging path shown in the following example:
+NSG flow logs target network security groups and aren't displayed the same way as the other logs. NSG flow logs are stored only in a storage account and follow the logging path shown in the following example:
 
 ```
 https://{storageAccountName}.blob.core.windows.net/insights-logs-networksecuritygroupflowevent/resourceId=/SUBSCRIPTIONS/{subscriptionID}/RESOURCEGROUPS/{resourceGroupName}/PROVIDERS/MICROSOFT.NETWORK/NETWORKSECURITYGROUPS/{nsgName}/y={year}/m={month}/d={day}/h={hour}/m=00/macAddress={macAddress}/PT1H.json