Apply suggestion from @ethanpalm

Co-authored-by: Ethan Palm <[email protected]>

Author: skeptrunedev

authentication-personalization/authentication-setup.mdx

@@ -103,7 +103,7 @@ Your documentation is hosted at `docs.foo.com` and your team uses the dashboard
       * **Authorization URL**: Your OAuth endpoint.
       * **Client ID**: Your OAuth 2.0 client identifier.
       * **Client Secret**: Your OAuth 2.0 client secret.
-      * **Scopes**: Permissions to request. Copy the **entire** scope string (e.g., for a scope like `provider.users.docs`, copy the complete `provider.users.docs`). Use multiple scopes if you need different access levels.
+      * **Scopes**: Permissions to request. Copy the **entire** scope string (for example, for a scope like `provider.users.docs`, copy the complete `provider.users.docs`). Use multiple scopes if you need different access levels.
       * **Token URL**: Your OAuth token exchange endpoint.
       * **Info API URL** (optional): Endpoint to retrieve user info for personalization. If omitted, the OAuth flow will only be used to verify identity and the user info will be empty.
       * **Logout URL**: The native logout URL for your OAuth provider. If your provider has a `returnTo` or similar parameter, point it back to your docs URL.