(AzureCXP) fixes MicrosoftDocs/azure-docs#45756

Explained <instance> and <tenant> parameters with examples in line 116.
-------
cc: @TylerMSFT

Author: AmanpreetSingh-MSFT

articles/active-directory/develop/msal-js-initializing-client-applications.md

@@ -113,7 +113,7 @@ Below is the total set of configurable options that are supported currently in t
         * `https://login.microsoftonline.com/common`- Used to sign in users with work and school accounts or a Microsoft personal account.
         * `https://login.microsoftonline.com/organizations/`- Used to sign in users with work and school accounts.
         * `https://login.microsoftonline.com/consumers/` - Used to sign in users with only personal Microsoft account (live).
-    * In Azure AD B2C, it is of the form `https://<instance>/tfp/<tenant>/<policyName>/`, where instance is the Azure AD B2C domain, tenant is the name of the Azure AD B2C tenant, policyName is the name of the B2C policy to apply.
+    * In Azure AD B2C, it is of the form `https://<instance>/tfp/<tenant>/<policyName>/`, where instance is the Azure AD B2C domain i.e. {your-tenant-name}.b2clogin.com, tenant is the name of the Azure AD B2C tenant i.e. {your-tenant-name}.onmicrosoft.com, policyName is the name of the B2C policy to apply.
 
 
 - **validateAuthority**: Optional.  Validate the issuer of tokens. Default is `true`. For B2C applications, since the authority value is known and can be different per policy, the authority validation will not work and has to be set to `false`.