docs: updated react account kit hooks

Author: aashkrishnan

account-kit/react/src/hooks/useAccount.ts

@@ -32,8 +32,11 @@ export type UseAccountProps<TAccount extends SupportedAccountTypes> =
 
 /**
  * [Hook](https://github.com/alchemyplatform/aa-sdk/blob/main/account-kit/react/src/hooks/useAccount.ts) to subscribe to account state and interactions, including creation, connection, and status monitoring. It synchronizes with external store updates and provides status-dependent results.
- * The supported account types are: LightAccount, MultiOwnerLightAccount, and MultiOwnerModularAccount. Primarily used to get the smart account address before deployment. Dependent on the signer, if the signer has not been initialized and authenticated, address and isLoadingAccount return null.
- * If using a smart contract account, returns instance of a smart contract account that the user is connected to. Returns address of smart contract account, not address of the signer. If using an EOA, returns address of signer
+ * The supported account types are: LightAccount, MultiOwnerLightAccount, and MultiOwnerModularAccount. Primarily used to get the smart account address before deployment. Dependent on the signer: if the signer has not been initialized and authenticated, `address` and `isLoadingAccount` return null.
+ *
+ * If using a smart contract account, returns instance of a smart contract account that the user is connected to. Returns address of smart contract account, not address of the signer.
+ *
+ * If using an EOA, returns address of signer
  *
  * @example
  * ```ts

account-kit/react/src/hooks/useAuthenticate.ts

@@ -31,8 +31,6 @@ export type UseAuthenticateResult = {
  *
  * This can be complex for magic link or OTP flows: OPT calls authenticate twice, but this should be handled by the signer.
  *
- * An example flow, we kick off useAuthenticate with authenticateAsync: we fire off to an incognito window to get a session from a backend. We listen to the signer or smart contract account client state to make sure the address is defined. And onSuccess, we redirect to a new view, which might be gated on useSmartAccountClient and a defined address.
- *
  * @example
  * ```ts
  * import { useAuthenticate } from "@account-kit/react";

account-kit/react/src/hooks/useExportAccount.ts

@@ -39,6 +39,7 @@ export type UseExportAccountResult = {
 
 /**
  * A [hook](https://github.com/alchemyplatform/aa-sdk/blob/main/account-kit/react/src/hooks/useExportAccount.ts) use to export the private key for an account. It returns the mutation functions to kick off the export process, as well as a component to render the account recovery details in an iframe.
+ * What is returned is dependent on what you used most recently used to authenticate. If your session was initiated with a passkey, then a private key is returned. Otherwise, a seed phrase.
  *
  * @example
  * ```ts
@@ -58,7 +59,7 @@ export type UseExportAccountResult = {
  * ```
  *
  * @param {UseExportAccountMutationArgs} args Optional arguments for the mutation and export parameters. [ref](https://github.com/alchemyplatform/aa-sdk/blob/main/account-kit/react/src/hooks/useExportAccount.ts#L11)
- * @returns {UseExportAccountResult} An object containing the export state, possible error, and the export account function and component. [ref](https://github.com/alchemyplatform/aa-sdk/blob/main/account-kit/react/src/hooks/useExportAccount.ts#L32)
+ * @returns {UseExportAccountResult} An object containing the export state, possible error, and the export account function and component. [ref](https://github.com/alchemyplatform/aa-sdk/blob/main/account-kit/react/src/hooks/useExportAccount.ts#L32)*
  */
 export function useExportAccount(
   args?: UseExportAccountMutationArgs

account-kit/react/src/hooks/useSigner.ts

@@ -7,7 +7,7 @@ import { useAlchemyAccountContext } from "../context.js";
 
 /**
  * [Hook](https://github.com/alchemyplatform/aa-sdk/blob/main/account-kit/react/src/hooks/useSigner.ts) for accessing the current Alchemy signer within a React component. It uses a synchronous external store for updates.
- * This is a good use case if you want to use the signer as an EOA, giving you direct access to it.
+ * This is a good use case if you want to use the signer as an EOA, giving you direct access to it. The signer returned from `usSigner` just does a `personal_sign` or `eth_signTypedData` without any additional logic, but a smart contract account might have additional logic for creating signatures for 1271 validation so `useSignMessage` or `useSignTypeData` instead.
  *
  * @example
  * ```ts