add clarification about the peer name

Author: halkazwini

articles/route-server/quickstart-create-route-server-cli.md

@@ -74,7 +74,9 @@ In this section, you learn how to configure BGP peering with a network virtual a
 # Add a peer.
 az network routeserver peering create --name 'myNVA' --peer-ip '10.0.0.4' --peer-asn '65001' --routeserver 'myRouteServer' --resource-group 'myResourceGroup'
 ``` 
-
+> [!NOTE]
+> The peer name doesn't have to be the same name of the NVA.
+ 
 ## Complete the configuration on the NVA 
 
 To complete the peering setup, you must configure the NVA to establish a BGP session with the route server's peer IPs and ASN. Use [az network routeserver show](/cli/azure/network/routeserver#az-network-routeserver-show) command to get the IP and ASN of the route server.

articles/route-server/quickstart-create-route-server-portal.md

@@ -75,7 +75,7 @@ In this section, you learn how to configure BGP peering with a network virtual a
 
     | Setting | Value |
     | ------- | ----- |
-    | Name | A name to identify the peer. This example uses **myNVA**. |
+    | Name | A name to identify the peer. It doesn't have to be the same name of the NVA. |
     | ASN | The Autonomous System Number (ASN) of the NVA. For more information, see [What Autonomous System Numbers (ASNs) can I use?](route-server-faq.md#what-autonomous-system-numbers-asns-can-i-use) |
     | IPv4 Address | The private IP address of the NVA that **myRouteServer** will communicate with to establish BGP. |
 

articles/route-server/quickstart-create-route-server-powershell.md

@@ -80,6 +80,8 @@ In this section, you learn how to configure BGP peering with a network virtual a
 # Add a peer.
 Add-AzRouteServerPeer -ResourceGroupName 'myResourceGroup' -RouteServerName 'myRouteServer' -PeerName 'myNVA' -PeerAsn '65001' -PeerIp '10.0.0.4'
 ```
+> [!NOTE]
+> The peer name doesn't have to be the same name of the NVA.
 
 ## Complete the configuration on the NVA