Skip to content

Commit 21a1d69

Browse files
authored
Update network-watcher-packet-capture-overview.md
Line 51, changed the heading to H2 to comply with the correct content structure guidance.
1 parent e87c86e commit 21a1d69

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/network-watcher/network-watcher-packet-capture-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ To control the size of captured data and only capture required information, use
4848

4949
There's a limit of 10,000 parallel packet capture sessions per region per subscription. This limit applies only to the sessions and doesn't apply to the saved packet capture files either locally on the VM or in a storage account. See the [Network Watcher service limits page](../azure-resource-manager/management/azure-subscription-service-limits.md#network-watcher-limits) for a full list of limits.
5050

51-
### Next steps
51+
## Next steps
5252

5353
- To learn how to manage packet captures using the Azure portal, see [Manage packet captures in virtual machines using the Azure portal](network-watcher-packet-capture-manage-portal.md) and [Manage packet captures in Virtual Machine Scale Sets using the Azure portal](network-watcher-packet-capture-manage-portal-vmss.md).
5454
- To learn how to manage packet captures using Azure PowerShell, see [Manage packet captures in virtual machines using PowerShell](network-watcher-packet-capture-manage-powershell.md) and [Manage packet captures in Virtual Machine Scale Sets using PowerShell](network-watcher-packet-capture-manage-powershell-vmss.md).

0 commit comments

Comments
 (0)