Add note about google oauth provider not working in in-app browsers (#…

…1620)

docs/authentication/social-connections/google.mdx

@@ -22,6 +22,9 @@ description: Learn how to allow users to sign up and sign in to your Clerk app w
 
 Enabling OAuth with Google allows your users to sign up and sign in to your Clerk application with their Google account.
 
+> [!WARNING]
+> Google sign-in [**does not** allow users to sign in via in-app browsers](https://developers.googleblog.com/en/modernizing-oauth-interactions-in-native-apps-for-better-usability-and-security/).
+
 ## Configure for your development instance
 
 For _development instances_, Clerk uses preconfigured shared OAuth credentials and redirect URIs—no other configuration is needed.
@@ -33,7 +36,7 @@ For _development instances_, Clerk uses preconfigured shared OAuth credentials a
 
 ## Configure for your production instance
 
-In _production instances_, you must provide custom credentials, which involves generating your own **Client ID** and **Client Secret** using your Google Developer account.
+For _production instances_, you must provide custom credentials, which involves generating your own **Client ID** and **Client Secret** using your Google Developer account.
 
 To make the setup process easier, it's recommended to keep two browser tabs open: one for your [Clerk Dashboard](https://dashboard.clerk.com/last-active?path=user-authentication/sso-connections) and one for your [Google Cloud Console](https://console.cloud.google.com/).
 
@@ -54,7 +57,7 @@ To make the setup process easier, it's recommended to keep two browser tabs open
   1. In the menu on the left, select **Credentials**.
   1. Select **Create Credentials**. Then, select **OAuth client ID.** You may need to [configure your OAuth consent screen](https://support.google.com/cloud/answer/6158849?hl=en#userconsent\&zippy=%2Cuser-consent).
   1. Select the appropriate application type for your project. Most likely, you will choose **Web application**.
-  1. In the **Authorized redirect URIs** setting, add the **Authorized redirect URI** value you saved from the Clerk Dashboard.
+  1. In the **Authorized redirect URIs** setting, paste the **Authorized redirect URI** value you saved from the Clerk Dashboard.
   1. Select **Create**. Keep this page open.
 
   ### Set the Client ID and Client Secret in your Clerk Dashboard
@@ -75,6 +78,9 @@ To make the setup process easier, it's recommended to keep two browser tabs open
      - **For development** – `https://your-domain.accounts.dev/sign-in`
      - **For production** – `https://accounts.your-domain.com/sign-in`
   1. Sign in with your Google account.
+
+  > [!WARNING]
+  > Google sign-in [**does not** allow users to sign in via in-app browsers](https://developers.googleblog.com/en/modernizing-oauth-interactions-in-native-apps-for-better-usability-and-security/).
 </Steps>
 
 ### Important note about switching to production