From c4f26120b02af5c3fffc3fa069413795db895a2d Mon Sep 17 00:00:00 2001 From: Zaid Rashid Date: Wed, 2 Oct 2024 18:01:14 +0200 Subject: [PATCH] docs: Fix typo. Use instead yuse (#9431) Fix typo. Use instead of use. I found this while reading through the documents here https://docs.medusajs.com/v2/resources/references/auth/provider#validatecallback --- packages/core/utils/src/auth/abstract-auth-provider.ts | 2 +- .../classes/auth_provider.AbstractAuthModuleProvider/page.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/core/utils/src/auth/abstract-auth-provider.ts b/packages/core/utils/src/auth/abstract-auth-provider.ts index fe17774b7f..cdf0f626f3 100644 --- a/packages/core/utils/src/auth/abstract-auth-provider.ts +++ b/packages/core/utils/src/auth/abstract-auth-provider.ts @@ -351,7 +351,7 @@ export abstract class AbstractAuthModuleProvider implements IAuthProvider { * * If the callback is verified successfully, the provider creates an auth identity for the user, or updates the auth identity's user information. * - * In the auth identity, yuse the following properties to store additional data: + * In the auth identity, use the following properties to store additional data: * * - `provider_metadata`: Store metadata useful for the provider, such as a password hash. * - `user_metadata`: Store metadata of the user's details. For example, if the third-party service returns the user's information such as email diff --git a/www/apps/resources/references/auth_provider/classes/auth_provider.AbstractAuthModuleProvider/page.mdx b/www/apps/resources/references/auth_provider/classes/auth_provider.AbstractAuthModuleProvider/page.mdx index 2d41a15053..2d5995f15d 100644 --- a/www/apps/resources/references/auth_provider/classes/auth_provider.AbstractAuthModuleProvider/page.mdx +++ b/www/apps/resources/references/auth_provider/classes/auth_provider.AbstractAuthModuleProvider/page.mdx @@ -329,7 +329,7 @@ That route uses this method to verify the callback's code. If the callback is verified successfully, the provider creates an auth identity for the user, or updates the auth identity's user information. -In the auth identity, yuse the following properties to store additional data: +In the auth identity, use the following properties to store additional data: - `provider_metadata`: Store metadata useful for the provider, such as a password hash. - `user_metadata`: Store metadata of the user's details. For example, if the third-party service returns the user's information such as email