Merge pull request #50644 from Brenduns/fix1

Fix1

Author: PRMerger16

articles/azure-stack/azure-stack-supported-os.md

@@ -67,4 +67,4 @@ Linux distributions listed as available in the Marketplace include the necessary
 
 Other Linux distributions may be supported in the future.
 
-For Red Hat Enterprise Linux support information , please refer to [Red Hat and Azure Stack: Frequently Asked Questions](https://access.redhat.com/articles/3413531).
+For Red Hat Enterprise Linux support information, refer to [Red Hat and Azure Stack: Frequently Asked Questions](https://access.redhat.com/articles/3413531).

articles/azure-stack/azure-stack-validation-report.md

@@ -21,7 +21,7 @@ ms.reviewer:
 
 
 # Azure Stack validation report
-The Azure Stack Readiness Checker tool runs validations that support deployment and servicing of an Azure Stack environment. The tool writes validation results to a .json report file. The report displays detailed and summarized data on the state of prerequisites for deployment of Azure Stack and on Secrets Rotation for existing Azure Stack Deployments.  
+Use the Azure Stack Readiness Checker tool to run validations that support deployment and servicing of an Azure Stack environment. The tool writes results to a .json report file. The report displays detailed and summarized data about the state of prerequisites for deployment of Azure Stack. The report also displays information about Secrets Rotation for existing Azure Stack Deployments.  
 
  ## Where to find the report
 When the tool runs, it logs results to **AzsReadinessCheckerReport.json**. The tool also creates a log named **AzsReadinessChecker.log**. The location of these files displays with the validation results in PowerShell.
@@ -35,7 +35,7 @@ By default, both files are written to *C:\Users\<username>\AppData\Local\Temp\Az
 - Use the **-CleanReport** parameter at the end of the run command to clear information from *AzsReadinessCheckerReport.json*. about previous runs of the tool.
 
 ## View the report
-To view the report in PowerShell, supply the path to the report as a value for **-ReportPath**. This command displays the contents of the report and also identifies validations that do not yet have results.
+To view the report in PowerShell, supply the path to the report as a value for **-ReportPath**. This command displays the contents of the report and identifies validations that do not yet have results.
 
 For example, to view the report from a PowerShell prompt that is open to the location where the report is located, run: 
    > `Start-AzsReadinessChecker -ReportPath .\AzsReadinessReport.json` 
@@ -54,7 +54,7 @@ The summary shows validations that don't have results and indicates pass or fail
 
 
 ## View a filtered report
-To view a report filtered on a single type of validation, use the **-ReportSections** parameter and specify one of the following values that correspond to the validation type you want to view:
+To view a report that is filtered on a single type of validation, use the **-ReportSections** parameter with one of the following values:
 - Certificate
 - AzureRegistration
 - AzureIdentity

articles/azure-stack/azure-stack-vpn-gateway-settings.md

@@ -23,7 +23,7 @@ ms.author: brenduns
 
 A VPN gateway is a type of virtual network gateway that sends encrypted traffic between your virtual network in Azure Stack and a remote VPN gateway. The remote VPN gateway can be in Azure, a device in your datacenter or a device in another site.  If there is network connectivity between the two endpoints, you can establish a secure Site-to-Site (S2S) VPN connection between the two networks.
 
-A VPN gateway connection relies on the configuration of multiple resources, each of which contains configurable settings. The sections in this article discuss the resources and settings that relate to a VPN gateway for a virtual network created in Resource Manager deployment model. You can find descriptions and topology diagrams for each connection solution in [About VPN Gateway for Azure Stack](azure-stack-vpn-gateway-about-vpn-gateways.md).
+A VPN gateway connection relies on the configuration of multiple resources, each of which contains configurable settings. This article discusses the resources and settings that relate to a VPN gateway for a virtual network that you create in the Resource Manager deployment model. You can find descriptions and topology diagrams for each connection solution in [About VPN Gateway for Azure Stack](azure-stack-vpn-gateway-about-vpn-gateways.md).
 
 ## VPN gateway settings
 
@@ -96,7 +96,7 @@ When you create the virtual network gateway for a VPN gateway configuration, you
 >
 > In addition, Azure Stack doesn't support using Policy Based Traffic Selectors for Route Based Gateways at this time, because custom IPSec/IKE policy configurations aren't supported.
 
-* **PolicyBased**: Policy-based VPNs encrypt and direct packets through IPsec tunnels based on the IPsec policies that are configured with the combinations of address prefixes between your on-premises network and the Azure Stack VNet. The policy, or traffic selector, is usually defined as an access list in the VPN device configuration.
+* **PolicyBased**: Policy-based VPNs encrypt and direct packets through IPsec tunnels based on the IPsec policies that are configured with the combinations of address prefixes between your on-premises network and the Azure Stack VNet. The policy, or traffic selector, is usually an access list in the VPN device configuration.
 
   >[!NOTE]
   >PolicyBased is supported in Azure, but not in Azure Stack.
@@ -159,7 +159,7 @@ Sometimes you need to modify the local network gateway settings. For example, wh
 
 ## IPsec/IKE parameters
 
-When you set up a VPN Connection in Azure Stack, you need to configure the connection at both ends.  If you are configuring a VPN Connection between Azure Stack and a hardware device like a switch or router, that is acting as a VPN Gateway, that device may ask you for additional settings.
+When you set up a VPN Connection in Azure Stack, you need to configure the connection at both ends.  If you are configuring a VPN Connection between Azure Stack and a hardware device like a switch or router that is acting as a VPN Gateway, that device might ask you for additional settings.
 
 Unlike Azure, which supports multiple offers as both an initiator and a responder, Azure Stack supports only one offer.
 
@@ -180,14 +180,12 @@ Unlike Azure, which supports multiple offers as both an initiator and a responde
 |IKE Version |IKEv2 |
 |Encryption & Hashing Algorithms (Encryption)     | GCMAES256|
 |Encryption & Hashing Algorithms (Authentication) | GCMAES256|
-|SA Lifetime (Time)  | 27,000 seconds<sup>See note 1</sup> |
-|SA Lifetime (Bytes) | 33,553,408<sup>See note 2</sup>     |
-|Perfect Forward Secrecy (PFS) |None<sup>See note 3</sup> |
+|SA Lifetime (Time)  | 27,000 seconds  |
+|SA Lifetime (Bytes) | 33,553,408     |
+|Perfect Forward Secrecy (PFS) |None<sup>See note 1</sup> |
 |Dead Peer Detection | Supported|  
 
-* *Note 1:*  Prior to version 1803, Azure Stack uses a value of 14,400 for the SA Lifetime (Time).
-* *Note 2:*  Prior to version 1803, Azure Stack uses a value of 819,200 for the SA Lifetime (Bytes).
-* *Note 3:*  Prior to version 1807, Azure Stack uses a value of PFS2048 for the Perfect Forward Secrecy (PFS).
+* *Note 1:*  Prior to version 1807, Azure Stack uses a value of PFS2048 for the Perfect Forward Secrecy (PFS).
 
 ## Next steps