Skip to content

Commit fdbc490

Browse files
committed
acrolinx corrections
1 parent 16066b4 commit fdbc490

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/network-watcher/network-watcher-read-nsg-flow-logs.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ NSG flow logs are stored in a storage account in [block blobs](/rest/api/storage
1818

1919
## Scenario
2020

21-
In the following scenario, you have an example flow log that is stored in a storage account. You learn how to selectively read the latest events in NSG flow logs. In this article you use PowerShell, however, the concepts discussed in the article are not limited to the programming language, and are applicable to all languages supported by the Azure Storage APIs.
21+
In the following scenario, you have an example flow log that is stored in a storage account. You learn how to selectively read the latest events in NSG flow logs. In this article you use PowerShell, however, the concepts discussed in the article aren't limited to the programming language, and are applicable to all languages supported by the Azure Storage APIs.
2222

2323
## Setup
2424

@@ -147,7 +147,7 @@ function Get-NSGFlowLogReadBlock {
147147
$valuearray = Get-NSGFlowLogReadBlock -blockList $blockList -CloudBlockBlob $CloudBlockBlob
148148
```
149149

150-
Now the `$valuearray` array contains the string value of each block. To verify the entry, get the second to the last value from the array by running `$valuearray[$valuearray.Length-2]`. You do not want the last value, because it is the closing bracket.
150+
Now the `$valuearray` array contains the string value of each block. To verify the entry, get the second to the last value from the array by running `$valuearray[$valuearray.Length-2]`. You don't want the last value, because it's the closing bracket.
151151

152152
The results of this value are shown in the following example:
153153

@@ -171,7 +171,7 @@ A","1497646742,10.0.0.4,168.62.32.14,44942,443,T,O,A","1497646742,10.0.0.4,52.24
171171
}
172172
```
173173

174-
This scenario is an example of how to read entries in NSG flow logs without having to parse the entire log. You can read new entries in the log as they are written by using the block ID or by tracking the length of blocks stored in the block blob. This allows you to read only the new entries.
174+
This scenario is an example of how to read entries in NSG flow logs without having to parse the entire log. You can read new entries in the log as they're written by using the block ID or by tracking the length of blocks stored in the block blob. This allows you to read only the new entries.
175175

176176
## Next steps
177177

0 commit comments

Comments
 (0)