docs: changes for next release (#11708)

* docs: changes for next release

* small fixes

* fix lint error

* small fix

www/apps/resources/app/commerce-modules/auth/authentication-route/page.mdx

@@ -339,8 +339,9 @@ If the authentication is successful, the request returns a `201` response code.
 The Medusa application defines an API route at `/auth/{actor_type}/{auth_provider}/update` that accepts a token and, if valid, updates the user's password.
 
 ```bash
-curl -X POST http://localhost:9000/auth/{actor_type}/{providers}/update?token=123
+curl -X POST http://localhost:9000/auth/{actor_type}/{providers}/update
 -H 'Content-Type: application/json' \
+-H 'Authorization: Bearer {token}' \
 --data-raw '{
   "email": "Whitney_Schultz@gmail.com",
   "password": "supersecret"
@@ -360,9 +361,15 @@ Its path parameters are:
 - `{actor_type}`: the actor type of the user you're authenticating. For example, `customer`.
 - `{provider}`: the auth provider to handle the authentication. For example, `emailpass`.
 
-#### Query Parameters
+#### Pass Token in Authorization Header
 
-The route accepts a `token` query parameter, which is the token generated using the [Generate Reset Password Token route](#generate-reset-password-token-route).
+<Note>
+
+Before [Medusa v2.6](https://github.com/medusajs/medusa/releases/tag/v2.6), you passed the token as a query parameter. Now, you must pass it in the `Authorization` header.
+
+</Note>
+
+In the request's authorization header, you must pass the token generated using the [Generate Reset Password Token route](#generate-reset-password-token-route). You pass it as a bearer token.
 
 ### Request Body Parameters