Merge pull request #294439 from cherylmc/update

add links

Author: prmerger-automator[bot]

articles/virtual-wan/point-to-site-entra-gateway-update.md

@@ -13,14 +13,13 @@ ms.author: cherylmc
 
 # Migrate a manually registered Azure VPN Client to the Microsoft-registered client
 
-This article helps you migrate from a manually registered Azure VPN Client to the Microsoft-registered Azure VPN Client for a User VPN (P2S) connection with Microsoft Entra ID authentication. The Microsoft-registered Azure VPN client uses a different Audience value. When you update an Audience value, you must make the change on both the P2S VPN gateway, and on any previously configured VPN clients. For more information about Audience values, see the [Microsoft-registerd app](point-to-site-entra-gateway.md) article.
+This article helps you migrate from a manually registered Azure VPN Client to the Microsoft-registered Azure VPN Client for a User VPN (P2S) connection with Microsoft Entra ID authentication. The Microsoft-registered Azure VPN client uses a different Audience value. When you update an Audience value, you must make the change on both the P2S VPN gateway, and on any previously configured VPN clients. For more information about Audience values, see the [Microsoft-registered app](point-to-site-entra-gateway.md) article.
+This article doesn't apply to **custom Audience** value configurations. To modify a custom audience app ID, see [Create or modify a custom audience app ID](point-to-site-entra-register-custom-app.md#change).
 
 The following table shows the available supported Audience values.
 
 [!INCLUDE [Audience values](../../includes/vpn-gateway-entra-audience-values.md)]
 
-This article doesn't apply to **custom Audience** value configurations. To modify a custom audience app ID, see [Create or modify a custom audience app ID for P2S VPN Microsoft Entra ID authentication](point-to-site-entra-register-custom-app.md#change).
-
 ## Workflow
 
 The standard workflow is: