Acrolinx

sethmanheim · sethmanheim · commit 048e22ce4243 · 2025-03-06T14:13:04.000-08:00
diff --git a/azure-stack/operator/azure-stack-troubleshooting.md b/azure-stack/operator/azure-stack-troubleshooting.md
@@ -140,10 +140,9 @@ You may also take a snapshot of the original disk and create a new disk from it
 - [Create a disk from a snapshot](/azure/virtual-machines/troubleshooting/troubleshoot-recovery-disks-portal-linux#create-a-disk-from-the-snapshot)
 - [Changing and resetting the Root password](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-working_with_the_grub_2_boot_loader#sec-Changing_and_Resetting_the_Root_Password)
 
-
 ### License activation fails for Windows Server 2012 R2 during provisioning
 
-In this case, Windows will fail to activate and you will see a watermark on the bottom-right corner of the screen. The WaSetup.xml logs located under C:\Windows\Panther contains the following event:
+In this case, Windows fails to activate and you see a watermark on the bottom-right corner of the screen. The WaSetup.xml logs located under C:\Windows\Panther contains the following event:
 
 ```xml
 <Event time="2019-05-16T21:32:58.660Z" category="ERROR" source="Unattend">
@@ -208,11 +207,11 @@ If the Create-AADIdentityApp.ps1 script that's required for App Service fails, b
 
 The Azure Stack Hub patch and update process is designed to allow operators to apply update packages in a consistent, streamlined way. While uncommon, issues can occur during patch and update process. The following steps are recommended should you encounter an issue during the patch and update process:
 
-0. **Prerequisites**: Be sure that you have followed the [Update Activity Checklist](release-notes-checklist.md) and [enable proactive log collection](./diagnostic-log-collection.md#send-logs-proactively).
+0. **Prerequisites**: Be sure that you follow the [Update Activity Checklist](release-notes-checklist.md) and [enable proactive log collection](./diagnostic-log-collection.md#send-logs-proactively).
 
 1. Follow the remediation steps in the failure alert created when your update failed.
 
-2. If you have been unable to resolve your issue, create an [Azure Stack Hub support ticket](./azure-stack-help-and-support-overview.md). Be sure you have [logs collected](./diagnostic-log-collection.md#send-logs-now) for the time span when the issue occurred. If an update fails, either with a critical alert or a warning, it's important that you review the failure and contact Microsoft Customer Support Services as directed in the alert so that your scale unit does not stay in a failed state for a long time. Leaving a scale unit in a failed update state for an extended period of time can cause additional issues that are more difficult to resolve later.
+2. If you're unable to resolve your issue, create an [Azure Stack Hub support ticket](./azure-stack-help-and-support-overview.md). Make sure you [collect logs](./diagnostic-log-collection.md#send-logs-now) for the time span when the issue occurred. If an update fails, either with a critical alert or a warning, it's important that you review the failure and contact Microsoft Customer Support Services as directed in the alert so that your scale unit does not stay in a failed state for a long time. Leaving a scale unit in a failed update state for an extended period of time can cause additional issues that are more difficult to resolve later.
 
 ## Common Azure Stack Hub patch and update issues
 
diff --git a/azure-stack/user/azure-stack-network-howto-vnet-to-onprem.md b/azure-stack/user/azure-stack-network-howto-vnet-to-onprem.md
@@ -16,7 +16,7 @@ ms.lastreviewed: 12/2/2020
 
 # Set up VPN gateway for Azure Stack Hub using FortiGate NVA
 
-This article describes how to create a VPN connection to your Azure Stack Hub. A VPN gateway is a type of virtual network gateway that sends encrypted traffic between your virtual network in Azure Stack Hub and a remote VPN gateway. The procedure below deploys one VNET with a FortiGate NVA, a network virtual appliance, within a resource group. It also provides steps to set up an IPSec VPN on the FortiGate NVA.
+This article describes how to create a VPN connection to your Azure Stack Hub. A VPN gateway is a type of virtual network gateway that sends encrypted traffic between your virtual network in Azure Stack Hub and a remote VPN gateway. The following procedure deploys one VNET with a FortiGate NVA, a network virtual appliance, within a resource group. It also provides steps to set up an IPSec VPN on the FortiGate NVA.
 
 ## Prerequisites
 
@@ -27,7 +27,7 @@ This article describes how to create a VPN connection to your Azure Stack Hub. A
    > [!NOTE]  
    > If you do not have the **Fortinet FortiGate-VM For Azure BYOL** and **FortiGate NGFW - Single VM Deployment (BYOL)** available in your Azure Stack Hub Marketplace, contact your cloud operator.
 
-- To activate the FortiGate NVA, you will need at least one available FortiGate license file. Information on how to acquire these licenses, see the Fortinet Document Library article [Registering and downloading your license](https://docs.fortinet.com/document/fortigate-private-cloud/6.2.0/nutanix-administration-guide/324840/registering-and-downloading-your-license).
+- To activate the FortiGate NVA, you need at least one available FortiGate license file. Information on how to acquire these licenses, see the Fortinet Document Library article [Registering and downloading your license](https://docs.fortinet.com/document/fortigate-private-cloud/6.2.0/nutanix-administration-guide/324840/registering-and-downloading-your-license).
 
    This procedure uses the [Single FortiGate-VM deployment](https://docs.fortinet.com/document/fortigate-public-cloud/6.2.0/azure-administration-guide/632940/single-fortigate-vm-deployment). You can find steps on how to connect the FortiGate NVA to the Azure Stack Hub VNET to in your on-premises network.
 
@@ -75,7 +75,7 @@ The following table summarizes the parameters that are used in these deployments
 1. Provide the Virtual network, Subnets, and VM Size details using the [Deployment parameters](#deployment-parameters) table.
 
    > [!WARNING]
-   > If the on-premises network overlaps with the IP range `172.16.0.0/16`, you must select and set up a different network range and subnets. If you wish to use different names and ranges than the ones in the [Deployment parameters](#deployment-parameters) table, use parameters that will **not** conflict with the on-premises network. Take care when setting the VNET IP range and subnet ranges within the VNET. You do not want the range to overlap with the IP ranges that exist in your on-premises network.
+   > If the on-premises network overlaps with the IP range `172.16.0.0/16`, you must select and set up a different network range and subnets. If you wish to use different names and ranges than the ones in the [Deployment parameters](#deployment-parameters) table, use parameters that don't conflict with the on-premises network. Take care when setting the VNET IP range and subnet ranges within the VNET. You don't want the range to overlap with the IP ranges that exist in your on-premises network.
 
 1. Select **OK**.
 
@@ -109,15 +109,15 @@ The following table summarizes the parameters that are used in these deployments
 1. Enter the IP network range that defines the network range of the on-premises network to which the VPN connects.
 1. Select **Virtual appliance** for **Next hop type** and `172.16.1.4`. If you use a different IP range, use your IP range.
 
-   ![The Add route dialog box shows the four values that have been entered into the text boxes.](./media/azure-stack-network-howto-vnet-to-onprem/image12a.png)
+   ![The Add route dialog box shows the four values that were entered into the text boxes.](./media/azure-stack-network-howto-vnet-to-onprem/image12a.png)
 
 1. Select **Save**.
 
 ## Activate the FortiGate NVA
 
 Activate the FortiGate NVA and set up an IPSec VPN connection on each NVA.
 
-To activate each FortiGate NVA will require a valid license file from Fortinet. The NVAs will **not** function until you have activated each NVA. For more information how to get a license file and steps to activate the NVA, see the Fortinet Document Library article [Registering and downloading your license](https://docs.fortinet.com/document/fortigate-private-cloud/6.2.0/nutanix-administration-guide/324840/registering-and-downloading-your-license).
+To activate each FortiGate NVA, you need a valid license file from Fortinet. The NVAs don't function until you activate each NVA. For more information how to get a license file and steps to activate the NVA, see the Fortinet Document Library article [Registering and downloading your license](https://docs.fortinet.com/document/fortigate-private-cloud/6.2.0/nutanix-administration-guide/324840/registering-and-downloading-your-license).
 
 Once you've activated the NVAs, create an IPSec VPN tunnel on the NVA.
 
@@ -165,7 +165,7 @@ Once you've activated the NVAs, create an IPSec VPN tunnel on the NVA.
 
    Use your IP range if you are using a different IP range.
 
-1. Enter the appropriate remote subnets that represent the on-premises network, to which you will connect through the on-premises VPN device.
+1. Enter the appropriate remote subnets that represent the on-premises network, to which you connect through the on-premises VPN device.
 
     ![The screenshot of the VPN Creation Wizard shows it to be on the third step, Policy & Routing. It shows the selected and entered values.](./media/azure-stack-network-howto-vnet-to-onprem/image18a.png)
 
@@ -180,7 +180,7 @@ Once you've activated the NVAs, create an IPSec VPN tunnel on the NVA.
 
 ## Configure the on-premises VPN
 
-The on-premises VPN device must be configured to create the IPSec VPN tunnel. The following table provides the parameters you will need to set up the on-premises VPN device. For information on how to configure the on-premises VPN device, refer tp the documentation for your device.
+The on-premises VPN device must be configured to create the IPSec VPN tunnel. The following table provides the parameters you need to set up the on-premises VPN device. For information about how to configure the on-premises VPN device, see the documentation for your device.
 
 | Parameter | Value |
 | --- | --- |
diff --git a/azure-stack/user/azure-stack-network-howto-vnet-to-vnet-stacks.md b/azure-stack/user/azure-stack-network-howto-vnet-to-vnet-stacks.md
@@ -16,9 +16,9 @@ ms.lastreviewed: 12/2/2020
 
 # VNet to VNet connectivity between Azure Stack Hub instances with Fortinet FortiGate NVA
 
-In this article, you'll connect a VNET in one Azure Stack Hub to a VNET in another Azure Stack Hub using Fortinet FortiGate NVA, a network virtual appliance.
+This article describes how to connect a VNET in one Azure Stack Hub to a VNET in another Azure Stack Hub using Fortinet FortiGate NVA, a network virtual appliance.
 
-This article addresses the current Azure Stack Hub limitation, which lets tenants set up only one VPN connection across two environments. Users will learn how to set up a custom gateway on a Linux virtual machine that will allow multiple VPN connections across different Azure Stack Hub. The procedure in this article deploys two VNETs with a FortiGate NVA in each VNET: one deployment per Azure Stack Hub environment. It also details the changes required to set up an IPSec VPN between the two VNETs. The steps in this article should be repeated for each VNET in each Azure Stack Hub.
+This article addresses the current Azure Stack Hub limitation, which lets tenants set up only one VPN connection across two environments. The article describes how to set up a custom gateway on a Linux virtual machine that allows multiple VPN connections across different Azure Stack Hub. The procedure in this article deploys two VNETs with a FortiGate NVA in each VNET: one deployment per Azure Stack Hub environment. It also details the changes required to set up an IPSec VPN between the two VNETs. The steps in this article should be repeated for each VNET in each Azure Stack Hub.
 
 ## Prerequisites
 
@@ -90,10 +90,10 @@ Repeat these steps for both Azure Stack Hub environments.
 1. Select **OK**.
 1. Provide the virtual network, subnets, and VM size details from the [Deployment parameters](#deployment-parameters).
 
-   If you wish to use different names and ranges, take care not to  use parameters that will conflict with the other VNET and FortiGate resources in the other Azure Stack Hub environment. This is especially true when setting the VNET IP range and subnet ranges within the VNET. Check that they don't overlap with the IP ranges for the other VNET you create.
+   If you want to use different names and ranges, take care not to use parameters that conflict with the other VNET and FortiGate resources in the other Azure Stack Hub environment. This limitation is especially true when setting the VNET IP range and subnet ranges within the VNET. Check that they don't overlap with the IP ranges for the other VNET you create.
 
 1. Select **OK**.
-1. Configure the public IP that will be used for the FortiGate NVA:
+1. Configure the public IP to be used for the FortiGate NVA:
 
    ![The "Public IP address name" text box of the IP Assignment dialog box shows a value of "forti1-publicip1" (from the Deployment Table).](./media/azure-stack-network-howto-vnet-to-vnet-stacks/image8.png)
 
@@ -121,7 +121,7 @@ Perform these steps for both deployments, forti1-rg1 and forti2-rg1.
 
 1. Select **Yes**.
 1. Select **Add**.
-1. Name the **Route** `to-forti1` or `to-forti2`. Use your IP range if you are using a different IP range.
+1. Name the **Route** `to-forti1` or `to-forti2`. Use your IP range if you're using a different IP range.
 1. Enter:
 
    - forti1: `172.17.0.0/16`  
@@ -175,7 +175,7 @@ Once the NVAs are activated, follow these steps to create an IPSec VPN between t
    ![The screenshot of the VPN Creation Wizard shows it to be on the first step, VPN Setup. The following values are selected: "Site to Site" for Template Type, "FortiGate" for Remote Device Type, and "This site is behind NAT" for NAT Configuration.](./media/azure-stack-network-howto-vnet-to-vnet-stacks/image16.png)
 
 1. Select **Next**.
-1. Enter the remote IP address of the on-premises VPN device to which you are going to connect.
+1. Enter the remote IP address of the on-premises VPN device to which you're going to connect.
 1. Select **port1** as the **Outgoing Interface**.
 1. Select **Pre-shared Key** and enter (and record) a pre-shared key.
 
@@ -193,7 +193,7 @@ Once the NVAs are activated, follow these steps to create an IPSec VPN between t
 
    If you use a different IP range, enter your IP range.
 
-1. Enter the appropriate Remote Subnet(s) that represent the on-premises network, which you will connect to through the on-premises VPN device.
+1. Enter the appropriate remote subnets that represent the on-premises network to which you connect through the on-premises VPN device:
 
    - forti1: 172.16.0.0/16
    - forti2: 172.17.0.0/16
@@ -231,7 +231,7 @@ You should now be able to route in between each VNET via the FortiGate NVAs. To
 
 - The Azure Stack Hub VMs are placed on the **InsideSubnet** of each VNET.
 - You don't apply any NSGs to the VM upon creation; that is, remove the NSG that gets added by default if creating the VM from the portal.
-- Ensure that the VM firewall rules allow the communication you are going to use to test connectivity. For testing purposes, it's recommended that you disable the firewall completely within the OS, if at all possible.
+- Ensure that the VM firewall rules allow the communication you're going to use to test connectivity. For testing purposes, it's recommended that you disable the firewall completely within the OS, if at all possible.
 
 ## Next steps
 
