update

docs/advanced-usage/clerk-idp.mdx

@@ -58,7 +58,9 @@ Scopes define the level of access and specific user data that will be shared wit
 
 ## OAuth 2.0
 
-After a user has successfully completed an OAuth 2.0 flow, you can retrieve additional user information from Clerk's [`/oauth/userinfo`](/docs/reference/frontend-api/tag/OAuth2-Identify-Provider#operation/getOAuthUserInfo){{ target: '_blank' }} endpoint, based on the granted scopes. When making the request to this endpoint, you must include the Clerk access token in the `Authorization` header.
+### Get additional user information
+
+After a user has successfully completed an OAuth 2.0 flow, you can retrieve additional user information from Clerk's [`/oauth/userinfo`](/docs/reference/frontend-api/tag/OAuth2-Identify-Provider#operation/getOAuthUserInfo){{ target: '_blank' }} endpoint. When making the request to this endpoint, you must include the Clerk access token in the `Authorization` header.
 
 The `/oauth/userinfo` endpoint provides the following user properties, depending on the granted scopes:
 
@@ -133,8 +135,6 @@ Depending on the granted scopes, the ID token can include the following addition
 
 ### OIDC prompt
 
-{/* TODO: Where do they use the `prompt` parameter? */}
-
 As part of an OIDC request, you can indicate the desired sign-in experience for the user by using the `prompt` parameter. The following values are supported:
 
 - `none`: The user doesn't interact with the provider, thus they need to have an active session already. If not, the provider responds with an error.