bad -> revoked

Author: GladwinJohnson

src/client/Microsoft.Identity.Client/Internal/Requests/ManagedIdentityAuthRequest.cs

@@ -63,19 +63,19 @@ protected override async Task<AuthenticationResult> ExecuteAsync(CancellationTok
                 _managedIdentityParameters.Claims = AuthenticationRequestParameters.Claims;
                 AuthenticationRequestParameters.RequestContext.ApiEvent.CacheInfo = CacheRefreshReason.ForceRefreshOrClaims;
 
-                // If there is a cached token, compute its hash for the “bad token” scenario
+                // If there is a cached token, compute its hash for the “revoked token” scenario
                 if (cachedAccessTokenItem != null)
                 {
                     string cachedTokenHash = _cryptoManager.CreateSha256HashHex(cachedAccessTokenItem.Secret);
                     _managedIdentityParameters.RevokedTokenHash = cachedTokenHash;
 
-                    logger.Info("[ManagedIdentityRequest] Claims are present. Computed hash of the cached (bad) token. " +
+                    logger.Info("[ManagedIdentityRequest] Claims are present. Computed hash of the cached (revoked) token. " +
                                 "Will now request a fresh token from the MI endpoint.");
                 }
                 else
                 {
                     logger.Info("[ManagedIdentityRequest] Claims are present, but no cached token was found. " +
-                                "Requesting a fresh token from the MI endpoint without a bad-token hash.");
+                                "Requesting a fresh token from the MI endpoint without a revoked-token hash.");
                 }
 
                 // In both cases, we skip using the cached token and get a new one