Merge pull request #9350 from auth0/rkhoriander-cms-launch-cleanup

CMS launch cleanup for files left on production

Author: tamigoodall

articles/api/authentication/_userinfo.md

@@ -91,7 +91,7 @@ This endpoint will work only if `openid` was granted as a <dfn data-key="scope">
 ### Remarks
 
 - The sample auth0.js script uses the library version 8. If you are using auth0.js version 7, please see this [reference guide](/libraries/auth0js/v7).
-- The auth0.js `parseHash` method, requires that your tokens are signed with `RS256`, rather than `HS256`. For more information about this, check the [Auth0.js v8 Migration Guide](/libraries/auth0js/migration-guide#the-parsehash-method).
+- The auth0.js `parseHash` method, requires that your tokens are signed with `RS256`, rather than `HS256`.
 - If you want this endpoint to return `user_metadata` or other custom information, you can use [rules](/rules/guides/metadata). For more information refer to [User profile claims and scope](/api-auth/tutorials/adoption/scope-custom-claims).
 - This endpoint will return three HTTP Response Headers, that provide relevant data on its rate limits:
   - `X-RateLimit-Limit`: Number of requests allowed per minute.

articles/architecture-scenarios/_includes/_authorization/_api-integration.md

@@ -16,7 +16,7 @@ On the other hand, if your organization *owns* the application(s), the user data
 Though you can configure your applications to be first-party and subsequently configure your APIs to allow first-party clients to ignore consent, if you are using `localhost` then Auth0 cannot verify that the application is truly a first-party app so your users will be prompted for consent anyway. To work around this constraint, when testing on your local machine during development, create a [fake local hostname and use that instead](https://community.auth0.com/t/how-do-i-skip-the-consent-page-for-my-api-authorization-flow/6035).
 :::
 
-Alternatively, you may have data relating to a user for which additional [functionality is provided](/scopes/current/api-scopes#example-an-api-called-by-a-back-end-service) and for which explicit user consent cannot be obtained (i.e. there is no authenticated user who can provide it). In this scenario, a [list of applications for which Client Credentials grant is enabled](docs/flows/concepts/client-credentials) can be defined. 
+Alternatively, you may have data relating to a user for which additional [functionality is provided](/scopes/current/api-scopes#example-an-api-called-by-a-back-end-service) and for which explicit user consent cannot be obtained (i.e. there is no authenticated user who can provide it). In this scenario, a [list of applications for which Client Credentials grant is enabled](/flows/concepts/client-credentials) can be defined. 
 
 ### Access Token claims
 

articles/architecture-scenarios/_includes/_operations/_notifications.md

@@ -18,4 +18,4 @@ It is a best practice to check the Auth0 [Security Bulletins](/security/bulletin
 
 ### Change log
 
-Auth0 provides information on changes to the service in the Auth0 [change log](https://auth0.com/changelog). You should make a regular practice of reviewing Auth0 change logs to be aware of changes. Support teams researching an issue may find it useful to review the change log to determine if recent changes might be related, especially if these are [breaking changes](docs/migrations). Development teams will also want to review the change logs to identify new features that may be beneficial.
+Auth0 provides information on changes to the service in the Auth0 [change log](https://auth0.com/changelog). You should make a regular practice of reviewing Auth0 change logs to be aware of changes. Support teams researching an issue may find it useful to review the change log to determine if recent changes might be related, especially if these are [breaking changes](/migrations). Development teams will also want to review the change logs to identify new features that may be beneficial.