Fix VNet and VNET references

Author: ecfan

articles/logic-apps/deploy-single-tenant-logic-apps-private-storage-account.md

@@ -41,7 +41,7 @@ This deployment method requires that temporary public access to your storage acc
 
 1. Deploy your logic app resource by using either the Azure portal or Visual Studio Code.
 
-1. After deployment finishes, enable VNet integration between your logic app and the private endpoints on the virtual network that connects to your storage account.
+1. After deployment finishes, enable virtual network integration between your logic app and the private endpoints on the virtual network that connects to your storage account.
 
    1. In the [Azure portal](https://portal.azure.com), open your logic app resource.
 
@@ -73,11 +73,11 @@ This deployment method requires that temporary public access to your storage acc
 This deployment method doesn't require public access to the storage account. For an example ARM template, review [Deploy logic app using secured storage account with private endpoints](https://github.com/VeeraMS/LogicApp-deployment-with-Secure-Storage). The example template creates the following resources:
 
 - A storage account that denies the public traffic
-- An Azure VNet and subnets
+- An Azure virtual network and subnets
 - Private DNS zones and private endpoints for Blob, File, Queue, and Table services
 - A file share for the Azure Logic Apps runtime directories and files. For more information, review [Host and app settings for logic apps in single-tenant Azure Logic Apps](edit-app-settings-host-settings.md).
 - An App Service plan (Workflow Standard WS1) for hosting Standard logic app resources
-- A Standard logic app resource with a network configuration that's set up to use VNet integration. This configuration enables the logic app to access the storage account through private endpoints.
+- A Standard logic app resource with a network configuration that's set up to use virtual network integration. This configuration enables the logic app to access the storage account through private endpoints.
 
 ## Troubleshoot common errors
 
@@ -91,7 +91,7 @@ The following errors commonly happen with a private storage account that's behin
 
 As the logic app isn't running when these errors occur, you can't use the Kudu console debugging service on the Azure platform to troubleshoot these errors. However, you can use the following methods instead:
 
-- Create an Azure virtual machine (VM) inside a different subnet within the same VNet that's integrated with your logic app. Try to connect from the VM to the storage account.
+- Create an Azure virtual machine (VM) inside a different subnet within the same virtual network that's integrated with your logic app. Try to connect from the VM to the storage account.
 
 - Check access to the storage account services by using the [Storage Explorer tool](https://azure.microsoft.com/features/storage-explorer/#overview).
 
@@ -131,7 +131,7 @@ As the logic app isn't running when these errors occur, you can't use the Kudu c
 
      1. In your logic app, [find and set the `WEBSITE_DNS_SERVER` app setting](edit-app-settings-host-settings.md?tabs=azure-portal?tabs=azure-portal#manage-app-settings---localsettingsjson) to the same DNS server value that you found in the previous step.
 
-     1. Check that the VNet integration is set up correctly with the appropriate VNET and subnet in your logic app.
+     1. Check that the virtual network integration is set up correctly with the appropriate virtual network and subnet in your logic app.
 
 ## Next steps
 

articles/logic-apps/secure-single-tenant-workflow-virtual-network-private-endpoint.md

@@ -156,7 +156,7 @@ For more information, review the following documentation:
 
 1. In the Azure portal, on the logic app resource menu, under **Settings**, select **Networking**.
 
-1. On the **Networking** pane,  on the **Outbound traffic** card, select **VNet integration**.
+1. On the **Networking** pane, on the **Outbound traffic** card, select **VNet integration**.
 
 1. On the **VNet Integration** pane, select **Add Vnet**.