more changes

v2/thirdparty/common-customizations/account-linking/overview.mdx

@@ -32,7 +32,7 @@ The `isPrimaryUser` boolean in the user object dictates if the user is a primary
 - 1) A primary user is one whose primary user ID does not change when accounts are linked to it. A user can become a primary user if, and only if there are no other primary users with the same email, third party info or phone number as this user across all the tenants that this user is a part of.
 
     For example, you **cannot** have the following scenarios:
-    - User A is a primary user with email `[email protected]` using email passoword login and User B is a primary user with email `[email protected]` using social login. This is not allowed because we have two primary users with the same email.
+    - User A is a primary user with email `[email protected]` using email password login and User B is a primary user with email `[email protected]` using social login. This is not allowed because we have two primary users with the same email.
     - User A is a primary user with email `[email protected]` and belongs to tenant `t1` and `t2`. User B is a primary user with email `[email protected]` and belongs to tenant `t2`. This is not allowed because we have two primary users with the same email in tenant `t2` However, if User B was in tenant `t3`, or if User A was not a part of tenant `t2`, then this would be allowed.
 
     You **can** have the following scenarios:

v2/thirdpartyemailpassword/common-customizations/account-linking/overview.mdx

@@ -32,7 +32,7 @@ The `isPrimaryUser` boolean in the user object dictates if the user is a primary
 - 1) A primary user is one whose primary user ID does not change when accounts are linked to it. A user can become a primary user if, and only if there are no other primary users with the same email, third party info or phone number as this user across all the tenants that this user is a part of.
 
     For example, you **cannot** have the following scenarios:
-    - User A is a primary user with email `[email protected]` using email passoword login and User B is a primary user with email `[email protected]` using social login. This is not allowed because we have two primary users with the same email.
+    - User A is a primary user with email `[email protected]` using email password login and User B is a primary user with email `[email protected]` using social login. This is not allowed because we have two primary users with the same email.
     - User A is a primary user with email `[email protected]` and belongs to tenant `t1` and `t2`. User B is a primary user with email `[email protected]` and belongs to tenant `t2`. This is not allowed because we have two primary users with the same email in tenant `t2` However, if User B was in tenant `t3`, or if User A was not a part of tenant `t2`, then this would be allowed.
 
     You **can** have the following scenarios:

v2/thirdpartypasswordless/common-customizations/account-linking/overview.mdx

@@ -32,7 +32,7 @@ The `isPrimaryUser` boolean in the user object dictates if the user is a primary
 - 1) A primary user is one whose primary user ID does not change when accounts are linked to it. A user can become a primary user if, and only if there are no other primary users with the same email, third party info or phone number as this user across all the tenants that this user is a part of.
 
     For example, you **cannot** have the following scenarios:
-    - User A is a primary user with email `[email protected]` using email passoword login and User B is a primary user with email `[email protected]` using social login. This is not allowed because we have two primary users with the same email.
+    - User A is a primary user with email `[email protected]` using email password login and User B is a primary user with email `[email protected]` using social login. This is not allowed because we have two primary users with the same email.
     - User A is a primary user with email `[email protected]` and belongs to tenant `t1` and `t2`. User B is a primary user with email `[email protected]` and belongs to tenant `t2`. This is not allowed because we have two primary users with the same email in tenant `t2` However, if User B was in tenant `t3`, or if User A was not a part of tenant `t2`, then this would be allowed.
 
     You **can** have the following scenarios: