Acrlinx edits

Author: v-ksreedevan

articles/network-watcher/network-watcher-alert-triggered-packet-capture.md

@@ -19,7 +19,7 @@ Network Watcher packet capture creates capture sessions to track traffic in and
 
 This capability can be started remotely from other automation scenarios such as Azure Functions. Packet capture gives you the capability to run proactive captures based on defined network anomalies. Other uses include gathering network statistics, getting information about network intrusions, debugging client-server communications, and more.
 
-Resources that are deployed in Azure run 24/7. You and your staff cannot actively monitor the status of all resources 24/7. For example, what happens if an issue occurs at 2 AM?
+Resources that are deployed in Azure run 24/7. You and your staff can't actively monitor the status of all resources 24/7. For example, what happens if an issue occurs at 2 AM?
 
 By using Network Watcher, alerting and functions from within the Azure ecosystem, you can proactively respond with the data and tools to solve problems in your network.
 
@@ -35,7 +35,7 @@ By using Network Watcher, alerting and functions from within the Azure ecosystem
 
 In this example, your VM is sending more TCP segments than usual and you want to be alerted. TCP segments are used as an example here, but you can use any alert condition.
 
-When you are alerted, the packet-level data helps to understand why communication has increased. You can take steps to return the virtual machine to regular communication.
+When you're alerted, the packet-level data helps to understand why communication has increased. You can take steps to return the virtual machine to regular communication.
 
 This scenario assumes that you have an existing instance of Network Watcher and a resource group with a valid Virtual machine.
 
@@ -67,13 +67,13 @@ The first step is to create an Azure function to process the alert and create a
     |**Setting** | **Value** | **Details** |
     |---|---|---|
     |**App name**|PacketCaptureExample|The name of the function app.|
-    |**Subscription**|[Your subscription]The subscription for which to create the function app.||
+    |**Subscription**|[Your subscription]The subscription for which you want to create the function app.||
     |**Resource Group**|PacketCaptureRG|The resource group to contain the function app.|
     |**Hosting Plan**|Consumption Plan| The type of plan your function app uses. Options are Consumption or Azure App Service plan. |
-    |**Location**|Central US| The region in which to create the function app.|
+    |**Location**|Central US| The region in which you want to create the function app.|
     |**Storage Account**|{autogenerated}| The storage account that Azure Functions needs for general-purpose storage.|
 
-3. On the **PacketCaptureExample Function Apps** blade, select **Functions** > **Custom function** >**+**.
+3. In **PacketCaptureExample Function Apps**, select **Functions** > **Custom function** > **+**.
 
 4. Select **HttpTrigger-Powershell** and enter the remaining information. Finally, to create the function, select **Create**.
 
@@ -159,7 +159,7 @@ The client ID is the Application ID of an application in Azure Active Directory.
 
 #### AzureTenant
 
-Obtain the tenant ID  by running the following PowerShell sample:
+Obtain the tenant ID by running the following PowerShell sample:
 
 ```powershell
 (Get-AzSubscription -SubscriptionName "<subscriptionName>").TenantId
@@ -272,7 +272,7 @@ The following example is PowerShell code that can be used in the function. There
             } 
  ``` 
 
-Use the following PowerShell code if you are using the old schema:
+Use the following PowerShell code if you're using the old schema:
 
 ```powershell
             #Import Azure PowerShell modules required to make calls to Network Watcher