docs: readability updates

Author: vonovak

.yarn/releases/yarn-4.7.0.cjs

@@ -1,3 +1,3 @@
 nodeLinker: node-modules
 
-yarnPath: .yarn/releases/yarn-4.7.0.cjs
+yarnPath: .yarn/releases/yarn-4.9.2.cjs

.yarn/releases/yarn-4.9.2.cjs

@@ -4,7 +4,7 @@ sidebar_class_name: sponsor-heart
 
 # GoogleLogoButton
 
-A Google Sign-In button that follows Google's official branding guidelines. Intended for native apps.
+A Google Sign-In button that follows Google's official branding guidelines. Intended for native apps. It renders null when used on the web.
 
 import Banner from '../_sponsorBanner.mdx';
 

.yarnrc.yml

@@ -19,7 +19,7 @@ As the Universal sign in Guide explains, there are two ways to sign in on the we
 
 One-tap UI may not always be available: This happens if user has [opted out](https://developers.google.com/identity/gsi/web/guides/features#globally_opt_out) or when they close the dialog several times in a row, entering the [cooldown period](https://developers.google.com/identity/gsi/web/guides/features#exponential_cooldown).
 
-The Google Sign-In button serves as a fallback. Tapping it will open the regular Google Sign-In dialog.
+The Google Sign-In button serves as a fallback. Tapping it opens the regular Google Sign-In dialog.
 
 ```tsx
 import { WebGoogleSigninButton } from '@react-native-google-signin/google-signin';

babel.config.js

@@ -36,14 +36,14 @@ try {
 import { statusCodes } from '@react-native-google-signin/google-signin';
 ```
 
-Status codes are useful when determining which kind of error has occurred during the sign-in process. Under the hood, these constants are derived from native GoogleSignIn error codes and are platform-specific. Always compare `error.code` to `statusCodes.*` and do not rely on the raw value of `error.code`.
+Status codes are useful when determining which kind of error has occurred during the sign-in process. Under the hood, these constants are derived from native error codes and are platform-specific. Always compare `error.code` to `statusCodes.*` and do not rely on the raw value of `error.code`.
 
 See [example usage](one-tap#signin).
 
-| Name                          | Description                                                                                                                                                                                                                                                                                                                                                                 |
-| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `IN_PROGRESS`                 | Trying to invoke another operation (e.g. `signInSilently`) when previous one has not yet finished. If you call e.g. `signInSilently` twice, two calls to `signInSilently` in the native module will be done. The promise from the first call to `signInSilently` will be rejected with this error, and the second will resolve / reject with the result of the native call. |
-| `PLAY_SERVICES_NOT_AVAILABLE` | Play services are not available or outdated. This happens on Android, or on the web when you're calling the exposed APIs [before the Client library is loaded](setting-up/web).                                                                                                                                                                                             |
+| Name                          | Description                                                                                                                                                                                                                                                                                                                                                             |
+| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `IN_PROGRESS`                 | Trying to invoke another operation (e.g. `signInSilently`) when previous one has not yet finished. If you call e.g. `signInSilently` twice, two calls to `signInSilently` in the native module are done. The promise from the first call to `signInSilently` will be rejected with this error, and the second will resolve / reject with the result of the native call. |
+| `PLAY_SERVICES_NOT_AVAILABLE` | Play services are not available or outdated. This happens on Android, or on the web when you're calling the exposed APIs [before the Client library is loaded](setting-up/web).                                                                                                                                                                                         |
 
 ### Status codes specific to Universal sign in {#universal-status-codes}
 

docs/buttons/google-logo-button.mdx

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 55
+sidebar_position: 61
 ---
 
 # Integration notes
@@ -18,6 +18,7 @@ sidebar_position: 55
 
 The default requested scopes are `email` and `profile`.
 
-If you want to manage other data from your application (for example access user agenda or upload a file to drive) you need to request additional permissions. This can be accomplished by adding the necessary scopes when configuring the GoogleSignin instance.
+If you want to manage other data from your application (for example, access user agenda or upload a file to drive) you need to request additional permissions. This can be accomplished by calling [`requestAuthorization`](one-tap#requestauthorization) or by
+adding the necessary scopes when calling [`configure`](one-tap#configure).
 
 Visit https://developers.google.com/identity/protocols/googlescopes or https://developers.google.com/oauthplayground/ for a list of available scopes.

docs/buttons/web.mdx

@@ -4,7 +4,7 @@ sidebar_label: Universal Google sign in
 sidebar_class_name: sponsor-heart
 ---
 
-# Universal Google sign in
+# Universal sign in
 
 This is Google's recommended way to implement Google Sign In. This API is available on Android, iOS, macOS and web (with a little extra work [described below](#web-support)). It is a replacement for the [Original Google sign in](original). The module APIs are named `GoogleOneTapSignIn` for historical reasons.
 
@@ -71,7 +71,7 @@ signature: (`params`: [`OneTapConfigureParams`](api#onetapconfigureparams)) => `
 
 It is mandatory to call `configure` before attempting to call any of the sign-in methods. This method is synchronous, meaning you can call e.g. `signIn` right after it. Typically, you would call `configure` only once, soon after your app starts.
 
-`webClientId` is a required parameter. Use "autoDetect" for [automatic webClientId detection](#automatic-config).
+`webClientId` is a required parameter. Use `"autoDetect"` for [automatic webClientId detection](#automatic-config).
 
 If you're using neither Expo nor Firebase, you also need to provide the `iosClientId` parameter. All other parameters are optional.
 
@@ -93,9 +93,7 @@ signature: (`params`?: [`OneTapSignInParams`](api#onetapsigninparams)) => `Promi
 | Apple    | Attempts to restore a previous user sign-in without interaction. [Docs](https://developers.google.com/identity/sign-in/ios/reference/Classes/GIDSignIn#-restoreprevioussigninwithcompletion:).                                                                                   |
 | Web      | Attempts to sign in user automatically, without interaction. [Docs](https://developers.google.com/identity/gsi/web/reference/js-reference#auto_select). If none is found, presents a sign-in UI. [Read below](#web-support) for web support.                                     |
 
-Returns a `Promise` that resolves with [`OneTapResponse`](api#onetapresponse) or rejects in case of error.
-
-If there is no user that was previously signed in, the promise resolves with [`NoSavedCredentialFound`](api#nosavedcredentialfound) object. In that case, you can call [`createAccount`](one-tap#createaccount) to start a flow to create a new account. You don't need to call `signIn` as a response to a user action - you can call it when your app starts or when suitable.
+If there is no user that was previously signed in, the returned promise resolves with [`NoSavedCredentialFound`](api#nosavedcredentialfound) object. In that case, you can call [`createAccount`](one-tap#createaccount) to start a flow to create a new account. You don't need to call `signIn` as a response to a user action - you can call it when your app starts or when suitable.
 
 import SignInScreenshots from './screenshots/_signIn.mdx';
 
@@ -170,61 +168,51 @@ You don't need to call `createAccount` as a response to a user action - you can
 
 Use `createAccount` if `signIn` resolved with [`NoSavedCredentialFound` result](api#nosavedcredentialfound), as indicated in the code snippet above.
 
-Returns a `Promise` that resolves with [`OneTapResponse`](api#onetapresponse) or rejects in case of error.
-
 import CreateAccount from './screenshots/_createAccount.mdx';
 
 <CreateAccount />
 
 ```ts
-await GoogleOneTapSignIn.createAccount({
-  nonce: 'your_nonce', // nonce is supported on all platforms!
-});
+await GoogleOneTapSignIn.createAccount();
 ```
 
 ---
 
 ### `presentExplicitSignIn`
 
-✨since v14.2.0
-
 signature: (`params`?: [`OneTapExplicitSignInParams`](api#onetapexplicitsigninparams)) => `Promise`\<[`OneTapExplicitSignInResponse`](api#onetapexplicitsigninresponse)\>
 
-| Platform | Behavior                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
-| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Android  | Presents the sign in dialog explicitly. This is useful when the user has hit rate limiting ([`ONE_TAP_START_FAILED`](errors#universal-status-codes)) and the one-tap flow is thus not available, or if both `signIn` and `createAccount` resolve with [`NoSavedCredentialFound`](api#nosavedcredentialfound) object - which happens (in the unlikely case) when no Google account is present on the device. This will prompt the user to add a Google account. |
-| Apple    | Starts an interactive sign-in flow. Same as `createAccount`.                                                                                                                                                                                                                                                                                                                                                                                                   |
-| Web      | Presents a one-tap prompt. Same as `createAccount`.                                                                                                                                                                                                                                                                                                                                                                                                            |
+| Platform | Behavior                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Android  | Presents the sign in dialog explicitly. This is useful when the user has hit rate limiting ([`ONE_TAP_START_FAILED`](errors#universal-status-codes)) and the one-tap flow is thus not available, or if both `signIn` and `createAccount` resolve with [`NoSavedCredentialFound`](api#nosavedcredentialfound) object - which happens (in the unlikely case) when no Google account is present on the device. This prompts the user to add a Google account. |
+| Apple    | Starts an interactive sign-in flow. Same as `createAccount`.                                                                                                                                                                                                                                                                                                                                                                                               |
+| Web      | Presents a one-tap prompt. Same as `createAccount`.                                                                                                                                                                                                                                                                                                                                                                                                        |
 
-Preferably, call this method only as a reaction to when user taps a "sign in with Google" button.
+Preferably, call this method only as a reaction to when user taps a [sign in button](buttons/google-logo-button).
 
 import PresentExplicitSignIn from './screenshots/_presentExplicitSignIn.mdx';
 
 <PresentExplicitSignIn />
 
 ```ts
-await GoogleOneTapSignIn.presentExplicitSignIn({
-  nonce: 'your_nonce', // nonce is supported on all platforms!
-});
+await GoogleOneTapSignIn.presentExplicitSignIn();
 ```
 
 ---
 
 ### `checkPlayServices`
 
-✨since v17.3.0
-
 signature: (`showErrorResolutionDialog`?: `boolean`): `Promise`\<[`PlayServicesInfo`](api#playservicesinfo)\>
 
 The behavior of `checkPlayServices` varies across platforms:
 
 - Android: The function resolves if the device has Play Services installed and their version is >= the minimum required version. Otherwise, it rejects with `statusCodes.PLAY_SERVICES_NOT_AVAILABLE` error code, and more information in `userInfo` field (see [below](#example-code-snippet)).
 
-On Android, the presence of up-to-date Google Play Services is required to call any of the provided authentication and authorization methods. It is therefore necessary to call `checkPlayServices` any time prior to calling the authentication / authorization methods and only call those if `checkPlayServices` is successful.
-
 The `showErrorResolutionDialog` parameter (default `true`) controls whether a dialog that helps to resolve an error is shown (only in case the error is user-resolvable).
 
-Some errors are user-resolvable (e.g. when Play Services are outdated, or disabled) while other errors cannot be resolved (e.g. when the phone doesn't ship Play Services at all - which is the case with some device vendors).
+On Android, the presence of up-to-date Google Play Services is required to call any of the provided authentication and authorization methods. It is therefore necessary to call `checkPlayServices` any time prior to calling the authentication / authorization methods and only call those if `checkPlayServices` is successful.
+
+Some errors are user-resolvable (e.g. when Play Services are outdated or disabled) while other errors cannot be resolved (e.g. when the phone doesn't ship Play Services at all - which is the case with some device vendors).
 
 <details>
   <summary>Dialog screenshots</summary>
@@ -234,19 +222,11 @@ Some errors are user-resolvable (e.g. when Play Services are outdated, or disabl
 
 </details>
 
-- Apple: Play Services are an Android-only concept and are not needed on Apple. Hence, the method always resolves with:
-
-```ts
-{
-  minRequiredVersion: -1,
-  installedVersion: -1,
-}
-```
-
-- Web: resolves (with the same value as on Apple) when the Google Client Library [is loaded](setting-up/web), rejects otherwise.
+- Apple: Play Services are an Android-only concept and are not needed on Apple. Hence, the method always resolves.
+- Web: resolves when the Google Client Library [is loaded](setting-up/web), rejects otherwise.
 
-```ts title="Example of showPlayServicesUpdateDialog() method"
-await GoogleOneTapSignIn.showPlayServicesUpdateDialog();
+```ts title="Example of checkPlayServices() method"
+await GoogleOneTapSignIn.checkPlayServices();
 ```
 
 ---
@@ -269,7 +249,7 @@ await GoogleOneTapSignIn.signOut();
 
 signature: (`emailOrUniqueId`: `string`) => `Promise`\<`null`\>
 
-Revokes access given to the current application and signs the user out. Use when user deletes their account in your app. On the web, you need to provide the `id` or email of the user. On Android and Apple, the `emailOrUniqueId` parameter does not have any effect.
+Revokes access given to the current application and signs the user out. Use when a user deletes their account in your app. On the web, you need to provide the `id` or email of the user. On Android and Apple, the `emailOrUniqueId` parameter does not have any effect.
 
 Returns a `Promise` that resolves with `null` or rejects in case of error.
 
@@ -281,8 +261,6 @@ await GoogleOneTapSignIn.revokeAccess(user.id);
 
 ### `requestAuthorization`
 
-✨since v15.0.0
-
 signature: (`params`: [`RequestAuthorizationParams`](api#requestauthorizationparams)) => `Promise`\<[`AuthorizationResponse`](api#authorizationresponse)\>
 
 The underlying Android SDK separates authentication and authorization - that means that on Android you can request an access token and call Google APIs on behalf of the user without previously signing the user in.
@@ -295,16 +273,12 @@ This method is used to request extra authorization from the user. Use this on An
 | Apple    | Calls [`addScopes`](./original.mdx#addscopes). The resulting `accessToken` has access to the requested scopes. Use this if you want to read more user metadata than just the basic info.                                                   |
 | Web      | Not implemented at the moment.                                                                                                                                                                                                             |
 
-> There are minor differences between the Android and Apple implementations stemming from the underlying Google SDKs. For example, Apple returns all granted scopes, while Android may only return the scopes that were requested.
-
 import RequestAuthorization from './screenshots/_requestAuthorization.mdx';
 
 <RequestAuthorization />
 
 ## Automatic `webClientId` & `iosClientId` detection {#automatic-config}
 
-✨since v15.2.0 for `webClientId`, 18.2.0 for `iosClientId`
-
 If you use Expo (with the config plugin and prebuild), or if you're using Firebase, you don't need to provide the `iosClientId` parameter to the `configure` method.
 
 Additionally, this module can automatically detect the `webClientId` from Firebase's configuration file (does not work on web where you need to provide it explicitly).