Correcting blockers 2 of 2

Author: v-regandowner

articles/sentinel/data-connectors/netskope-using-azure-functions.md

@@ -70,7 +70,7 @@ To integrate with Netskope (using Azure Functions) make sure you have:
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-This method provides an automated deployment of the Netskope connector using an ARM Tempate.
+This method provides an automated deployment of the Netskope connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
@@ -92,10 +92,10 @@ This method provides the step-by-step instructions to deploy the Netskope connec
 
 **1. Create a Function App**
 
-1.  From the Azure Portal, navigate to [Function App](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites/kind/functionapp), and select **+ Add**.
+1.  From the Azure portal, navigate to [Function App](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites/kind/functionapp), and select **+ Add**.
 2. In the **Basics** tab, ensure Runtime stack is set to **Powershell Core**. 
 3. In the **Hosting** tab, ensure the **Consumption (Serverless)** plan type is selected.
-4. Make other preferrable configuration changes, if needed, then click **Create**.
+4. Make other preferable configuration changes, if needed, then click **Create**.
 
 
 **2. Import Function App Code**
@@ -119,9 +119,9 @@ This method provides the step-by-step instructions to deploy the Netskope connec
 		timeInterval
 		logTypes
 		logAnalyticsUri (optional)
-  - Enter the URI that corresponds to your region. The `uri` value must follow the following schema: `https://<Tenant Name>.goskope.com` - There is no need to add subsquent parameters to the Uri, the Function App will dynamically append the parameteres in the proper format.
+  - Enter the URI that corresponds to your region. The `uri` value must follow the following schema: `https://<Tenant Name>.goskope.com` - There is no need to add subsequent parameters to the Uri, the Function App will dynamically append the parameters in the proper format.
   - Set the `timeInterval` (in minutes) to the default value of `5` to correspond to the default Timer Trigger of every `5` minutes. If the time interval needs to be modified, it is recommended to change the Function App Timer Trigger accordingly to prevent overlapping data ingestion.
-  - Set the `logTypes` to `alert, page, application, audit, infrastructure, network` - This list represents all the avaliable log types. Select the log types based on logging requirements, seperating each by a single comma.
+  - Set the `logTypes` to `alert, page, application, audit, infrastructure, network` - This list represents all the available log types. Select the log types based on logging requirements, separating each by a single comma.
     > [!NOTE]
     > If using Azure Key Vault, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Key Vault references documentation](/azure/app-service/app-service-key-vault-references) for further details. 
   - Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: `https://<CustomerId>.ods.opinsights.azure.us`.