Skip to content

Commit 063da7e

Browse files
author
Ankita Dutta
committed
acrolinx suggestions
1 parent ade253e commit 063da7e

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The detailed specification of all NSG flow logs commands for various versions of
3030
3131
## Register Insights provider
3232

33-
In order for flow logging to work successfully, the **Microsoft.Insights** provider must be registered. If you are not sure if the **Microsoft.Insights** provider is registered, run the following script.
33+
In order for flow logging to work successfully, the **Microsoft.Insights** provider must be registered. If you aren't sure if the **Microsoft.Insights** provider is registered, run the following script.
3434

3535
```powershell
3636
Register-AzResourceProvider -ProviderNamespace Microsoft.Insights
@@ -92,6 +92,6 @@ For information about the structure of the log visit [Network Security Group Flo
9292

9393
## Next Steps
9494

95-
Learn how to [Visualize your NSG flow logs with PowerBI](network-watcher-visualize-nsg-flow-logs-power-bi.md)
95+
Learn how to [Visualize your NSG flow logs with Power BI](network-watcher-visualize-nsg-flow-logs-power-bi.md)
9696

9797
Learn how to [Visualize your NSG flow logs with open source tools](network-watcher-visualize-nsg-flow-logs-open-source-tools.md)

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Network Security Group flow logs are a feature of Network Watcher that allows yo
2929

3030
ARMclient is used to call the REST API using PowerShell. ARMClient is found on chocolatey at [ARMClient on Chocolatey](https://chocolatey.org/packages/ARMClient). The detailed specifications of NSG flow logs REST API can be found [here](/rest/api/network-watcher/flowlogs)
3131

32-
This scenario assumes you have already followed the steps in [Create a Network Watcher](network-watcher-create.md) to create a Network Watcher.
32+
This scenario assumes you've already followed the steps in [Create a Network Watcher](network-watcher-create.md) to create a Network Watcher.
3333

3434
> [!Important]
3535
> For Network Watcher REST API calls the resource group name in the request URI is the resource group that contains the Network Watcher, not the resources you are performing the diagnostic actions on.
@@ -54,7 +54,7 @@ armclient login
5454

5555
## Register Insights provider
5656

57-
In order for flow logging to work successfully, the **Microsoft.Insights** provider must be registered. If you are not sure if the **Microsoft.Insights** provider is registered, run the following script.
57+
In order for flow logging to work successfully, the **Microsoft.Insights** provider must be registered. If you aren't sure if the **Microsoft.Insights** provider is registered, run the following script.
5858

5959
```powershell
6060
$subscriptionId = "00000000-0000-0000-0000-000000000000"
@@ -63,7 +63,7 @@ armclient post "https://management.azure.com//subscriptions/${subscriptionId}/pr
6363

6464
## Enable Network Security Group flow logs
6565

66-
The command to enable flow logs version 2 is shown in the following example. For version 1 replace the 'version' field with '1':
66+
The command to enable flow logs version 2 is shown in the following example. For version 1, replace the 'version' field with '1':
6767

6868
```powershell
6969
$subscriptionId = "00000000-0000-0000-0000-000000000000"
@@ -188,7 +188,7 @@ $requestBody = @"
188188
armclient post "https://management.azure.com/subscriptions/${subscriptionId}/ResourceGroups/${resourceGroupName}/providers/Microsoft.Network/networkWatchers/${networkWatcherName}/queryFlowLogStatus?api-version=2016-12-01" $requestBody
189189
```
190190

191-
The following is an example of the response returned:
191+
The following example shows the response returned:
192192

193193
```json
194194
{
@@ -224,6 +224,6 @@ https://{storageAccountName}.blob.core.windows.net/insights-logs-networksecurity
224224

225225
## Next steps
226226

227-
Learn how to [Visualize your NSG flow logs with PowerBI](network-watcher-visualize-nsg-flow-logs-power-bi.md)
227+
Learn how to [Visualize your NSG flow logs with Power BI](network-watcher-visualize-nsg-flow-logs-power-bi.md)
228228

229229
Learn how to [Visualize your NSG flow logs with open source tools](network-watcher-visualize-nsg-flow-logs-open-source-tools.md)

0 commit comments

Comments
 (0)