Apply suggestions from code review

Co-authored-by: Chris Werner <[email protected]>

Author: rmca14

articles/active-directory-b2c/claim-resolver-overview.md

@@ -61,7 +61,7 @@ The following table lists the claim resolvers with information about the policy
 | ----- | ----------- | --------|
 | {Policy:PolicyId} | The relying party policy name. | B2C_1A_signup_signin |
 | {Policy:RelyingPartyTenantId} | The tenant ID of the relying party policy. | your-tenant.onmicrosoft.com |
-| {Policy:TenantObjectId} | The tenant object ID of the relying party policy. | ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0 |
+| {Policy:TenantObjectId} | The tenant object ID of the relying party policy. | 00000000-0000-0000-0000-000000000000 |
 | {Policy:TrustFrameworkTenantId} | The tenant ID of the trust framework. | your-tenant.onmicrosoft.com |
 
 Check out the [Live demo](https://github.com/azure-ad-b2c/unit-tests/tree/main/claims-resolver#policy) of the policy claim resolvers.
@@ -73,7 +73,7 @@ The following table lists the contextual claim resolvers of the authorization re
 | Claim | Description | Example |
 | ----- | ----------- | --------|
 | {Context:BuildNumber} | The Identity Experience Framework version (build number).  | 1.0.507.0 |
-| {Context:CorrelationId} | The correlation ID.  | ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0 |
+| {Context:CorrelationId} | The correlation ID.  | 00000000-0000-0000-0000-000000000000 |
 | {Context:DateTimeInUtc} |The date time in UTC.  | 10/10/2021 12:00:00 PM |
 | {Context:DeploymentMode} |The policy deployment mode.  | Production |
 | {Context:HostName} | The host name of the current request.  | contoso.b2clogin.com |

articles/active-directory-b2c/identity-provider-azure-ad-multi-tenant.md

@@ -169,7 +169,7 @@ To obtain the values, look at the OpenID Connect discovery metadata for each of
 
 Perform these steps for each Microsoft Entra tenant that should be used to sign in:
 
-1. Open your browser and go to the OpenID Connect metadata URL for the tenant. Find the `issuer` object and record its value. It should look similar to `https://login.microsoftonline.com/ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0/v2.0`.
+1. Open your browser and go to the OpenID Connect metadata URL for the tenant. Find the `issuer` object and record its value. It should look similar to `https://login.microsoftonline.com/ aaaabbbb-0000-cccc-1111-dddd2222eeee/v2.0`.
 1. Copy and paste the value into the **ValidTokenIssuerPrefixes** key. Separate multiple issuers with a comma. An example with two issuers appears in the previous `ClaimsProvider` XML sample.
 
 [!INCLUDE [active-directory-b2c-add-identity-provider-to-user-journey](../../includes/active-directory-b2c-add-identity-provider-to-user-journey.md)]