improve the Acrolinx score

Author: lucciz01

support/power-platform/power-platform-administration/troubleshoot-virtual-network-power-platform.md

@@ -1,5 +1,5 @@
 ---
-title: Virtual Network troubleshooting
+title: Troubleshoot Virtual Network Issues
 description: Learn how to troubleshoot common scenarios for Virtual Network in Microsoft Power Platform.
 author: faix
 ms.component: pa-admin
@@ -12,13 +12,13 @@ search.audienceType:
 contributors:
 ms.custom: sap:Power Platform Administration
 ---
-# Virtual Network troubleshooting
+# Troubleshoot Virtual Network issues
 
 This article provides guidance on troubleshooting common scenarios for Virtual Network in Power Platform. You can make use of a PowerShell module that can help you identify and resolve issues related to Virtual Network configurations.
 
 ## Diagnostics PowerShell Module
 
-The Diagnostics PowerShell Module is a tool designed to help you diagnose and troubleshoot issues related to Virtual Network configurations in Power Platform. The module can be used to check the connectivity between your Power Platform environment and your Virtual Network, and to identify any misconfigurations that may be causing issues. It's available from the Powershell Gallery and from our GitHub repository: [PowerPlatform-EnterprisePolicies](https://github.com/microsoft/PowerPlatform-EnterprisePolicies)
+The Diagnostics PowerShell Module is a tool designed to help you diagnose and troubleshoot issues related to Virtual Network configurations in Power Platform. The module can be used to check the connectivity between your Power Platform environment and your Virtual Network, and to identify any misconfigurations that might be causing issues. It's available from the PowerShell Gallery and from our GitHub repository: [PowerPlatform-EnterprisePolicies](https://github.com/microsoft/PowerPlatform-EnterprisePolicies)
 
 ### Installing the module
 
@@ -45,21 +45,21 @@ The module includes several functions that can be used to diagnose and troublesh
 
 ### Issues with the diagnostic module
 
-If you encounter issues while running the diagnostic module, report them through the Github repository where the module is hosted. The repository is available at: [PowerPlatform-EnterprisePolicies](https://github.com/microsoft/PowerPlatform-EnterprisePolicies).
+If you encounter issues while running the diagnostic module, report them through the GitHub repository where the module is hosted. The repository is available at: [PowerPlatform-EnterprisePolicies](https://github.com/microsoft/PowerPlatform-EnterprisePolicies).
 
-To report an issue, go to the Issues section of the repository and create a [new issue](https://github.com/microsoft/PowerPlatform-EnterprisePolicies/issues/new). Provide detailed information about the problem you're facing, including any error messages or logs that may help in diagnosing the issue. The more information you provide, the easier it is for us to assist you. Don't include any sensitive information in your report.
+To report an issue, go to the Issues section of the repository and create a [new issue](https://github.com/microsoft/PowerPlatform-EnterprisePolicies/issues/new). Provide detailed information about the problem you're facing, including any error messages or logs that might help in diagnosing the issue. The more information you provide, the easier it is for us to assist you. Don't include any sensitive information in your report.
 
 ## How to troubleshoot common scenarios
 
 ### Scenario: Misconfiguration of regions
 
-If you have verified that everything is correctly configured but you are still experiencing issues, you can use the `Get-EnvironmentRegion` function from the Diagnostics PowerShell Module to check if the region of your Power Platform environment is the same as the regions where you have been configuring your Virtual Network. You can run the following command:
+If you have verified that everything is correctly configured but you're still experiencing issues, you can use the `Get-EnvironmentRegion` function from the Diagnostics PowerShell Module to check if the region of your Power Platform environment is the same as the regions where you have been configuring your Virtual Network. You can run the following command:
 
 ```powershell
 Get-EnvironmentRegion -EnvironmentId "00000000-0000-0000-0000-000000000000"
 ```
 
-Your environment belongs to a specific PowerPlatform region. However, a PowerPlatform region can span multiple Azure regions. You need to ensure that your Virtual Network is configured in both of the Azure regions that correspond to your PowerPlatform region. Your environment can be located in either of the two Azure regions, and it can also automatically failover between them. Therefore, to ensure high availability and connectivity, you should configure your Virtual Network in both Azure regions associated with your PowerPlatform region. You can find the mapping of the PowerPlatform regions to Azure regions that are support for the Virtual Network functionality at [Power Platform regions](/power-platform/admin/vnet-support-overview#supported-regions).
+Your environment belongs to a specific PowerPlatform region. However, a PowerPlatform region can span multiple Azure regions. You need to ensure that your Virtual Network is configured in both of the Azure regions that correspond to your PowerPlatform region. Your environment can be located in either of the two Azure regions, and it can also automatically fail over between them. Therefore, to ensure high availability and connectivity, you should configure your Virtual Network in both Azure regions associated with your PowerPlatform region. You can find the mapping of the PowerPlatform regions to Azure regions that are support for the Virtual Network functionality at [Power Platform regions](/power-platform/admin/vnet-support-overview#supported-regions).
 
 ### Scenario: Hostname not found
 
@@ -69,7 +69,7 @@ If you're experiencing issues with hostname resolution, you can use the `Test-Dn
 Test-DnsResolution -EnvironmentId "00000000-0000-0000-0000-000000000000" -HostName "microsoft.com"
 ```
 
-This command tests the DNS resolution for the specified hostname in the context of your Power Platform environment. The request will initiate from the subnet that you have delegated and will attempt to resolve the hostname using the DNS server that is configured for your Virtual Network. If the hostname isn't being resolved correctly, you may need to check your DNS settings and ensure that the hostname is correctly configured.
+This command tests the DNS resolution for the specified hostname in the context of your Power Platform environment. The request will initiate from the subnet that you have delegated and will attempt to resolve the hostname using the DNS server that is configured for your Virtual Network. If the hostname isn't being resolved correctly, you might need to check your DNS settings and ensure that the hostname is correctly configured.
 
 > [!IMPORTANT]
 > If you notice that your DNS setup is incorrect and need to update the DNS server settings for your Virtual Network, see [Can I update the DNS address of my Virtual Network after it's delegated to "Microsoft.PowerPlatform/enterprisePolicies"?](/power-platform/admin/vnet-support-overview#can-i-update-the-dns-address-of-my-virtual-network-after-its-delegated-to-microsoftpowerplatformenterprisepolicies)
@@ -82,18 +82,18 @@ If you're experiencing issues with connectivity to a resource, you can use the `
 Test-NetworkConnectivity -EnvironmentId "00000000-0000-0000-0000-000000000000" -Destination "unknowndb.database.windows.net" -Port 1433
 ```
 
-This command attempts to establish a TCP connection to the specified destination and port in the context of your Power Platform environment. The request will initiate from the subnet that you have delegated and will attempt to connect to the specified destination using the network configuration that is set up for your Virtual Network. If the connection fails, you may need to check your network settings and ensure that the destination is reachable from your Virtual Network. If the connection is successful, it indicates that there's network connectivity between the Power Platform environment and the specified resource.
+This command attempts to establish a TCP connection to the specified destination and port in the context of your Power Platform environment. The request will initiate from the subnet that you have delegated and will attempt to connect to the specified destination using the network configuration that is set up for your Virtual Network. If the connection fails, you might need to check your network settings and ensure that the destination is reachable from your Virtual Network. If the connection is successful, it indicates that there's network connectivity between the Power Platform environment and the specified resource.
 
 > [!NOTE]
-> This command only tests if a TCP connection can be established to the specified destination and port. It doesn't test if the resource is actually available or if there are any application-level issues that may be preventing access to the resource.
-> Furthermore, some firewalls may be allowing TCP connections to be established but blocking actual traffic to the resource (i.e. HTTPS). Therefore, even if the command indicates that there's network connectivity, it doesn't guarantee that the resource is fully accessible.
+> This command only tests if a TCP connection can be established to the specified destination and port. It doesn't test if the resource is actually available or if there are any application-level issues that might be preventing access to the resource.
+> Furthermore, some firewalls might be allowing TCP connections to be established but blocking actual traffic to the resource (that is, HTTPS). Therefore, even if the command indicates that there's network connectivity, it doesn't guarantee that the resource is fully accessible.
 
 ### Scenario: Connectivity is successful, but the application is still not working
 
-If the connectivity tests are successful, but you're still experiencing issues with your application, you may need to check the application-level settings and configurations. Things that you can check include:
+If the connectivity tests are successful, but you're still experiencing issues with your application, you might need to check the application-level settings and configurations. Things that you can check include:
 
 - Validate in your firewall that the delegated subnet is allowed to access the resource.
-- Validate that the certificate presented by the resource are publicly trusted.
-- Ensure that there are no authentication or authorization issues that may be preventing access to the resource.
+- Validate that the certificate presented by the resource is publicly trusted.
+- Ensure that there are no authentication or authorization issues that might be preventing access to the resource.
 
-If our existing tools aren't sufficient to diagnose the issue further. You may want to create a subnet without delegation in your Virtual Network and deploy a virtual machine in that subnet. You can then use the virtual machine to perform additional diagnostics and troubleshooting steps, such as checking network traffic, analyzing logs, and testing application-level connectivity.
+If our existing tools aren't sufficient to diagnose the issue further. You might want to create a subnet without delegation in your Virtual Network and deploy a virtual machine in that subnet. You can then use the virtual machine to perform additional diagnostics and troubleshooting steps, such as checking network traffic, analyzing logs, and testing application-level connectivity.