Update manage-inbound-nat-rules.md

Making doc clearer on NAT rule V1/V2

Author: mahipdeora

articles/load-balancer/manage-inbound-nat-rules.md

@@ -15,9 +15,9 @@ An inbound NAT rule is used to forward traffic from a load balancer frontend to
 
 There are two types of inbound NAT rule:
 
-* Single virtual machine - An inbound NAT rule that targets a single machine in the backend pool of the load balancer
+* Inbound NAT rule V1 for VMs - Targets a single machine in the backend pool of the load balancer
 
-* Multiple virtual machines - An inbound NAT rule that targets multiple virtual machines in the backend pool of the load balancer
+* Inbound NAT rule V2 for VMs and VMSS- Targets multiple virtual machines in the backend pool of the load balancer
 
 In this article, you learn how to add and remove an inbound NAT rule for both types. You learn how to change the frontend port allocation in a multiple instance inbound NAT rule. You can choose from the Azure portal, PowerShell, or CLI examples.
 
@@ -30,7 +30,7 @@ In this article, you learn how to add and remove an inbound NAT rule for both ty
 [!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
 
-## Add a single VM inbound NAT rule
+## Inbound NAT rule V1 for VMs
 
 Choose this option to configure a rule for a single VM. Select Azure portal, PowerShell, or CLI for instructions.
 
@@ -165,7 +165,7 @@ Use [az network nic ip-config inbound-nat-rule add](/cli/azure/network/nic/ip-co
 ```
 ---
 
-## Add a multiple VMs inbound NAT rule
+## Inbound NAT rule V2 for VM and VMSS
 Choose this option to configure a rule with a range of ports to a backend pool of virtual machines. Select Azure portal, PowerShell, or CLI for instructions.
 
 # [**Portal**](#tab/inbound-nat-rule-portal)