update

msmbaldwin · msmbaldwin · commit 7cbd026b3ad9 · 2023-03-28T11:58:30.000-07:00
diff --git a/articles/payment-hsm/fastpathenabled.md b/articles/payment-hsm/fastpathenabled.md
@@ -15,21 +15,23 @@ ms.author: mbaldwin
 
 # Fastpathenabled
 
-Within the context of Azure Payment HSM, "Fastpathenabled" is used in two related but distinct ways:
+Azure Payment HSM uses the term "Fastpathenabled" in two related but distinct ways:
 
-- "FastPathEnabled" (capitalized) is a an Azure Feature Exposure Control (AFEC) flag. It must be applied to **every** subscription ID that wants to connect to a payment HSM.
-- "fastpathenabled" (lowercased) is a virtual network tag. It must be added to **every** virtual network and NAT gateway (when applicable) that interacts with a payment HSM.
+- "FastPathEnabled" (capitalized) is an Azure Feature Exposure Control (AFEC) flag. It must be applied to **every** subscription ID that wants to connect to a payment HSM.
+- "fastpathenabled" (lowercased) is a virtual network tag. It must be added to **every** virtual network (and NAT gateway, when applicable) that interacts with a payment HSM.
 
 ### Subscriptions
 
-The "FastPathEnabled" feature flag must be added/registered to all subscriptions IDs that connect to a payment HSM. If you have multiple subscriptions IDs that require access to a payment HSM, include them all when contacting [Mirosoft support](support-guide.md#microsoft-support) (after you [Register the resource providers and features](register-payment-hsm-resource-providers.md)).
+The "FastPathEnabled" feature flag must be added/registered to all subscriptions IDs that connect to a payment HSM.  Applying the "FastPathEnabled" feature flag to a subscription that already has resources has **no** effect on existing resources--existing resources must be subsequently registered. 
 
-> [!WARNING]
-Applying the "FastPathEnabled" feature flag to a subscription that already has resources has **no** effect on existing resources. You must register those resources by following the stpes in [Register the resource providers and features](register-payment-hsm-resource-providers.md).
+To apply the "FastPathEnabled" feature flag, see [Register the resource providers and features](register-payment-hsm-resource-providers.md).
+
+> [!IMPORTANT]
+> After registering the "FastPathEnabled" feature flag, you **must** contact the [Azure Payment HSM support team](support-guide.md#microsoft-support) team to have your registration approved.  In your message to Microsoft support, include the subscription IDs of **every** subscription you want to connect to the payment HSM.
 
 ### Virtual networks
 
-The "fastpathenabled" tag must be enabled on every virtual networks that the payment HSM uses, peered or otherwise. For instance, to peer a virtual network of a payment HSM with a virtual network of a VM, you must first add the "fastpathenabled" tag to the latter.
+The "fastpathenabled" tag must be added to every virtual networks that the payment HSM uses, peered or otherwise. For instance, to peer a virtual network of a payment HSM with a virtual network of a VM, you must first add the "fastpathenabled" tag to the latter.
 
 Unfortunately, adding the "fastpathenabled" tag through the Azure portal is insufficient—it must be done from the commandline. To do so, follow the steps outlined in [How to peer Azure Payment HSM virtual networks](peer-vnets.md?tabs=azure-cli).
 
@@ -40,7 +42,8 @@ For an Virtual Network NAT scenario, you must add the "fastpathenabled" tag wi
 ## Next steps
 
 - Learn more about [Azure Payment HSM](overview.md)
-- See common [Deployment scenarios](deployment-scenarios.md)
-- Find out how to [get started with Azure Payment HSM](getting-started.md)
-- Learn how to [Create a payment HSM](create-payment-hsm.md)
+- [Register the resource providers and features](register-payment-hsm-resource-providers.md)
+- [How to peer Azure Payment HSM virtual networks](peer-vnets.md?tabs=azure-cli)
+- [Get started with Azure Payment HSM](getting-started.md)
+- [Create a payment HSM](create-payment-hsm.md)
 - Read the [frequently asked questions](faq.yml)
diff --git a/articles/payment-hsm/quickstart-cli.md b/articles/payment-hsm/quickstart-cli.md
@@ -22,9 +22,9 @@ This article describes how to create, update, and delete an Azure Payment HSM by
 - You must register the "Microsoft.HardwareSecurityModules" and "Microsoft.Network" resource providers, as well as the Azure Payment HSM features. Steps for doing so are at [Register the Azure Payment HSM resource provider and resource provider features](register-payment-hsm-resource-providers.md).
 
   > [!WARNING]
-  > You must apply the "FastPathEnabled" feature flag to **every** subscription ID, and add the "fastpathenabled" tag to **every** virtual network. For more details, see [Fastpathenabled](fastpathenabled.md).
+  > You must apply the "FastPathEnabled" feature flag to **every** subscription ID, and add the "fastpathenabled" tag to **every** virtual network. For more information, see [Fastpathenabled](fastpathenabled.md).
 
-  To quickly ascertain if the resource providers and features are already registered, use the Azure CLI [az provider show](/cli/azure/provider#az-provider-show) command. (You will find the output of this command more readable if you display it in table-format.)
+  To quickly ascertain if the resource providers and features are already registered, use the Azure CLI [az provider show](/cli/azure/provider#az-provider-show) command. (The output of this command is more readable if you display it in table-format.)
 
   ```azurecli-interactive
   az provider show --namespace "Microsoft.HardwareSecurityModules" -o table
@@ -72,7 +72,7 @@ To verify that the VNet and subnet were created correctly, use the Azure CLI [az
 az network vnet show -n "myVNet" -g "myResourceGroup"
 ```
 
-Make note of the value returned as "id", as you will need it for the next step.  The "id" will be in the format:
+Make note of the value returned as `id`, as it is used in the next step.  The `id` is in the format:
 
 ```json
 "id": "/subscriptions/<subscriptionID>/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNet/subnets/myPHSMSubnet",
@@ -100,7 +100,7 @@ To see your payment HSM and its properties, use the Azure CLI [az dedicated-hsm
 az dedicated-hsm show --resource-group "myResourceGroup" --name "myPaymentHSM"
 ```
 
-To list all of your payment HSMs, use the [az dedicated-hsm list](/cli/azure/dedicated-hsm#az-dedicated-hsm-list) command. (You will find the output of this command more readable if you display it in table-format.)
+To list all of your payment HSMs, use the [az dedicated-hsm list](/cli/azure/dedicated-hsm#az-dedicated-hsm-list) command. (The output of this command is more readable if you display it in table-format.)
 
 ```azurecli-interactive
 az dedicated-hsm list --resource-group "myResourceGroup" -o table
@@ -120,7 +120,7 @@ az dedicated-hsm delete --name "myPaymentHSM" -g "myResourceGroup"
 
 ## Next steps
 
-In this quickstart, you created a payment HSM, viewed and updated its properties, and deleted it. To learn more about Payment HSM and how to integrate it with your applications, continue on to the articles below.
+In this quickstart, you created a payment HSM, viewed and updated its properties, and deleted it. To learn more about Payment HSM and how to integrate it with your applications, continue on to these articles.
 
 - Read an [Overview of Payment HSM](overview.md)
 - Find out how to [get started with Azure Payment HSM](getting-started.md)
diff --git a/articles/payment-hsm/quickstart-powershell.md b/articles/payment-hsm/quickstart-powershell.md
@@ -22,7 +22,7 @@ This article describes how you can create an Azure Payment HSM using the [Az.Ded
 - You must register the "Microsoft.HardwareSecurityModules" and "Microsoft.Network" resource providers, as well as the Azure Payment HSM features. Steps for doing so are at [Register the Azure Payment HSM resource provider and resource provider features](register-payment-hsm-resource-providers.md).
 
   > [!WARNING]
-  > You must apply the "FastPathEnabled" feature flag to **every** subscription ID, and add the "fastpathenabled" tag to **every** virtual network. For more details, see [Fastpathenabled](fastpathenabled.md).
+  > You must apply the "FastPathEnabled" feature flag to **every** subscription ID, and add the "fastpathenabled" tag to **every** virtual network. For more information, see [Fastpathenabled](fastpathenabled.md).
 
   To quickly ascertain if the resource providers and features are already registered, use the Azure PowerShell [Get-AzProviderFeature](/powershell/module/az.resources/get-azproviderfeature) cmdlet:
 
@@ -93,7 +93,7 @@ To verify that the VNet was created correctly, use the Azure PowerShell [Get-AzV
 Get-AzVirtualNetwork -Name "myVNet" -ResourceGroupName "myResourceGroup"
 ```
 
-Make note of the value returned as "Id", as you will need it for the next step.  The "Id" will be in the format:
+Make note of the value returned as `Id`, as it is used in the next step.  The `Id` is in the format:
 
 ```json
 "Id": "/subscriptions/<subscriptionID>/resourceGroups/myResourceGroup/providers/Microsoft.Network/virtualNetworks/myVNet/subnets/myPHSMSubnet",
@@ -107,7 +107,7 @@ To create a payment HSM, use the [New-AzDedicatedHsm](/powershell/module/az.dedi
 New-AzDedicatedHsm -Name "myPaymentHSM" -ResourceGroupName "myResourceGroup" -Location "East US" -Sku "payShield10K_LMK1_CPS60" -StampId "stamp1" -SubnetId "<subnet-id>"
 ```
 
-The output of the payment HSM creation will look like this:
+The output of payment HSM creation looks like this:
 
 ```Output
 Name  Provisioning State SKU                     Location
@@ -145,7 +145,7 @@ Remove-AzDedicatedHsm -Name "myPaymentHSM" -ResourceGroupName "myResourceGroup"
 
 ## Next steps
 
-In this quickstart, you created a payment HSM, viewed and updated its properties, and deleted it. To learn more about Payment HSM and how to integrate it with your applications, continue on to the articles below.
+In this quickstart, you created a payment HSM, viewed and updated its properties, and deleted it. To learn more about Payment HSM and how to integrate it with your applications, continue on to these articles.
 
 - Read an [Overview of Payment HSM](overview.md)
 - Find out how to [get started with Azure Payment HSM](getting-started.md)
diff --git a/articles/payment-hsm/register-payment-hsm-resource-providers.md b/articles/payment-hsm/register-payment-hsm-resource-providers.md
@@ -67,7 +67,7 @@ Register-AzProviderFeature -FeatureName "FastPathEnabled" -ProviderNamespace Mic
 ```
 
 > [!IMPORTANT]
-> After registering the "FastPathEnabled" feature flag, you **must** contact the [Azure Payment HSM support team](support-guide.md#microsoft-support) team to have your registration approved.  In your message to Microsoft support, include your subscription ID.  If multiple subsciptions must connect with the payment HSM, you must include **all** the subscriopts IDs.
+> After registering the "FastPathEnabled" feature flag, you **must** contact the [Azure Payment HSM support team](support-guide.md#microsoft-support) team to have your registration approved.  In your message to Microsoft support, include the subscription IDs of **every** subscription you want to connect to the payment HSM.
 
 You can verify that your registrations are complete with the Azure PowerShell [Get-AzProviderFeature](/powershell/module/az.resources/get-azproviderfeature) cmdlet:
 
