Made requested changes to warning/note format and text

Author: mattreatMSFT

articles/network-watcher/network-watcher-analyze-nsg-flow-logs-graylog.md

@@ -24,7 +24,8 @@ ms.author: mareat
 
 You can have many network security groups in your network with flow logging enabled. Several network security groups with flow logging enabled can make it cumbersome to parse and gain insights from your logs. This article provides a solution to centrally manage these network security group flow logs using Graylog, an open source log management and analysis tool, and Logstash, an open source server-side data processing pipeline.
 
-[!Warning] This scenario leverages NSG Flow Logs version 1 and will not support version 2 without modification.
+> [!Warning]
+> The following steps work with flow logs version 1. For details, see [Introduction to flow logging for network security groups](network-watcher-nsg-flow-logging-overview.md). The following instructions will not work with version 2 of the log files, without modification.
 
 ## Scenario
 

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

@@ -31,7 +31,8 @@ Network Security Group flow logs are a feature of Network Watcher that allows yo
 
 To perform the steps in this article, you need to [install the Azure command-line interface for Mac, Linux, and Windows (CLI)](/cli/azure/install-azure-cli).
 
-[!NOTE] Flow Logs Version 2 are only available in select the West Central US Region. Configuration is available through the Azure Portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs outputted to your storage account.
+> [!NOTE] 
+> Flow Logs Version 2 are only available in the West Central US Region. Configuration is available through the Azure Portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs outputted to your storage account.
 
 ## Register Insights provider
 

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

@@ -66,8 +66,9 @@ Flow logs include the following properties:
                     * **Packets - Destination to source - Version 2 Only** The total number of TCP or UDP packets sent from destination to source since last update.
                     * **Bytes sent - Destination to source - Version 2 Only** The total number of TCP and UDP packet bytes sent from destination to source since last update. Packet bytes include packet header and payload.
 
-## NSG Flow Logs Version 2
-[!NOTE] Flow Logs Version 2 are only available in select the West Central US Region. Configuration is available through the Azure Portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs outputted to your storage account.
+## NSG flow logs version 2
+> [!NOTE] 
+> Flow Logs Version 2 are only available in the West Central US Region. Configuration is available through the Azure Portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs outputted to your storage account.
 
 Version 2 of the logs introduces flow state. You can configure which version of flow logs you receive. To learn how to enable flow logs, see [Enabling NSG flow logging](network-watcher-nsg-flow-logging-portal.md).
 
@@ -85,15 +86,15 @@ For continuation *C* and end *E* flow states, byte and packet counts are aggrega
 
 The text that follows is an example of a flow log. As you can see, there are multiple records that follow the property list described in the preceding section.
 
-##Sample Log Records
-=======
+## Sample log records
+
 The text that follows is an example of a flow log. As you can see, there are multiple records that follow the property list described in the preceding section.
 
 
 > [!NOTE]
 > Values in the **flowTuples* property are a comma-separated list.
  
-### Version 1 NSG Flow Log Format Sample
+### Version 1 NSG flow log format sample
 ```json
 {
     "records": [
@@ -202,7 +203,7 @@ The text that follows is an example of a flow log. As you can see, there are mul
 		,
 		...
 ```
-### Version 2 NSG Flow Log Format Sample
+### Version 2 NSG flow log format sample
 ```json
  {
     "records": [

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

@@ -34,7 +34,8 @@ A network security group (NSG) enables you to filter inbound traffic to, and out
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
-[!NOTE] Flow Logs Version 2 are only available in select the West Central US Region. Configuration is available through the Azure portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs saved to your storage account.
+> [!NOTE] 
+> Flow Logs Version 2 are only available in the West Central US Region. Configuration is available through the Azure portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs saved to your storage account.
 
 ## Create a VM
 

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

@@ -29,7 +29,8 @@ ms.author: jdial
 
 Network Security Group flow logs are a feature of Network Watcher that allows you to view information about ingress and egress IP traffic through a Network Security Group. These flow logs are written in json format and show outbound and inbound flows on a per rule basis, the NIC the flow applies to, 5-tuple information about the flow (Source/Destination IP, Source/Destination Port, Protocol), and if the traffic was allowed or denied.
 
-[!NOTE] Flow Logs Version 2 are only availble in select the West Central US Region. Configuration is available through the Azure Portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs outputted to your storage account.
+> [!NOTE] 
+> Flow Logs Version 2 are only availble in the West Central US Region. Configuration is available through the Azure Portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs outputted to your storage account.
 
 ## Register Insights provider
 

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

@@ -29,7 +29,8 @@ ms.author: jdial
 
 Network Security Group flow logs are a feature of Network Watcher that allows you to view information about ingress and egress IP traffic through a Network Security Group. These flow logs are written in json format and show outbound and inbound flows on a per rule basis, the NIC the flow applies to, 5-tuple information about the flow (Source/Destination IP, Source/Destination Port, Protocol), and if the traffic was allowed or denied.
 
-[!NOTE] Flow Logs Version 2 are only available in select the West Central US Region. Configuration is available through the Azure Portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs outputted to your storage account.
+> [!NOTE] 
+> Flow Logs Version 2 are only available in the West Central US Region. Configuration is available through the Azure Portal and REST API. Enabling Version 2 logs in an unsupported region will result in Version 1 logs outputted to your storage account.
 
 ## Before you begin
 

articles/network-watcher/network-watcher-nsg-grafana.md

@@ -22,7 +22,8 @@ ms.author: mareat
 
 [Network Security Group (NSG) flow logs](network-watcher-nsg-flow-logging-overview.md) provide information that can be used to understand ingress and egress IP traffic on network interfaces. These flow logs show outbound and inbound flows on a per NSG rule basis, the NIC the flow applies to, 5-tuple information about the flow (Source/Destination IP, Source/Destination Port, Protocol), and if the traffic was allowed or denied.
 
-[!Warning]  The following steps work with flow logs version 1. For details, see [Introduction to flow logging for network security groups](network-watcher-nsg-flow-logging-overview.md). The following instructions will not work with version 2 of the log files, without modification.
+> [!Warning]  
+> The following steps work with flow logs version 1. For details, see [Introduction to flow logging for network security groups](network-watcher-nsg-flow-logging-overview.md). The following instructions will not work with version 2 of the log files, without modification.
 
 You can have many NSGs in your network with flow logging enabled. This amount of logging data makes it cumbersome to parse and gain insights from your logs. This article provides a solution to centrally manage these NSG flow logs using Grafana, an open source graphing tool, ElasticSearch, a distributed search and analytics engine, and Logstash, which is an open source server-side data processing pipeline.  
 

articles/network-watcher/network-watcher-visualize-nsg-flow-logs-open-source-tools.md

@@ -23,7 +23,8 @@ Network Security Group flow logs provide information that can be used understand
 
 These flow logs can be difficult to manually parse and gain insights from. However, there are several open source tools that can help visualize this data. This article will provide a solution to visualize these logs using the Elastic Stack, which will allow you to quickly index and visualize your flow logs on a Kibana dashboard.
 
-[!Warning]  The following steps work with flow logs version 1. For details, see [Introduction to flow logging for network security groups](network-watcher-nsg-flow-logging-overview.md). The following instructions will not work with version 2 of the log files, without modification.
+> [!Warning]  
+> The following steps work with flow logs version 1. For details, see [Introduction to flow logging for network security groups](network-watcher-nsg-flow-logging-overview.md). The following instructions will not work with version 2 of the log files, without modification.
 
 ## Scenario
 

articles/network-watcher/network-watcher-visualize-nsg-flow-logs-power-bi.md

@@ -23,7 +23,8 @@ Network Security Group flow logs allow you to view information about ingress and
 
 It can be difficult to gain insights into flow logging data by manually searching the log files. In this article, we provide a solution to visualize your most recent flow logs and learn about traffic on your network.
 
-[!Warning]  The following steps work with flow logs version 1. For details, see [Introduction to flow logging for network security groups](network-watcher-nsg-flow-logging-overview.md). The following instructions will not work with version 2 of the log files, without modification.
+> [!Warning]  
+> The following steps work with flow logs version 1. For details, see [Introduction to flow logging for network security groups](network-watcher-nsg-flow-logging-overview.md). The following instructions will not work with version 2 of the log files, without modification.
 
 ## Scenario