(AzureCXP) fixes MicrosoftDocs/azure-docs#108288

In Line 87, Updated "$myCustomIpPrefix" to "$myCustomIPv6GlobalPrefix"
In Line 101, Updated "$myCustomIpPrefix" to "$myCustomIPv6RegionalPrefix"

resolves MicrosoftDocs/azure-docs#108288

Author: KapilAnanth-MSFT

articles/virtual-network/ip-services/create-custom-ip-address-prefix-ipv6-powershell.md

@@ -84,7 +84,7 @@ $prefix =@{
     AuthorizationMessage = 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|2a05:f500:2::/48|yyyymmdd'
     SignedMessage = $byoipauthsigned
 }
-$myCustomIpPrefix = New-AzCustomIPPrefix @prefix
+$myCustomIPv6GlobalPrefix = New-AzCustomIPPrefix @prefix
 ```
 
 ### Provision a regional custom IPv6 address prefix
@@ -98,7 +98,7 @@ $prefix =@{
     Location = 'EastUS2'
     CIDR = '2a05:f500:2:1::/64'
 }
-$myCustomIpPrefix = New-AzCustomIPPrefix @prefix -Zone 1,2,3
+$myCustomIPv6RegionalPrefix = New-AzCustomIPPrefix @prefix -Zone 1,2,3
 ```
 Similar to IPv4 custom IP prefixes, after the regional custom IP prefix is in a **Provisioned** state, public IP prefixes can be derived from the regional custom IP prefix.  These public IP prefixes and any public IP addresses derived from them can be attached to networking resources, though they are not yet being advertised.