docs(review): apply Tristan's two must-fix items from the final review

api-reference/wallet-authentication.mdx

@@ -1,18 +1,18 @@
 ---
 title: "Wallet Authentication (SIWE)"
 description: "Sign-In with Ethereum and Tron wallet authentication for session-based API access"
 ---
 
 ## Overview
 
 Wallet authentication uses the [Sign-In with Ethereum (SIWE)](https://eips.ethereum.org/EIPS/eip-4361) standard to authenticate users via their wallet signature. After verification, the API sets an httpOnly session cookie for subsequent requests.
 
 This is the authentication method used by the [Request Dashboard](https://dashboard.request.network) and is required for managing [payee destinations](/api-features/payee-destinations) and [client IDs](/api-features/client-id-management).
 
 ## Supported Wallets
 
 - **EVM wallets** — MetaMask, WalletConnect, Coinbase Wallet, and any wallet supporting `personal_sign`
 - **Tron wallets** — TronLink, Guarda, Trust, WalletConnect-Tron (addresses starting with `T...`)
 
 The API auto-detects the wallet type from the address format. Both EVM and Tron wallets are first-class authentication methods for the Dashboard and the auth API.
 
@@ -32,7 +32,7 @@
     {
       "challengeId": "01HXEXAMPLE123",
       "nonce": "a1b2c3d4e5f6",
-      "message": "auth.request.network wants you to sign in with your Ethereum account:\n0x6923831ACf5c327260D7ac7C9DfF5b1c3cB3C7D7\n\nSign in to Request Network\n\nURI: https://auth.request.network\nVersion: 1\nChain ID: 1\nNonce: a1b2c3d4e5f6\nIssued At: 2026-03-15T10:00:00.000Z",
+      "message": "auth.request.network wants you to sign in with your Ethereum account:\n0x6923831ACf5c327260D7ac7C9DfF5b1c3cB3C7D7\n\nSign in to Request Network.\n\nURI: https://auth.request.network\nVersion: 1\nNonce: a1b2c3d4e5f6\nIssued At: 2026-03-15T10:00:00.000Z\nExpiration Time: 2026-03-15T10:05:00.000Z",
       "expiresAt": "2026-03-15T10:05:00.000Z"
     }
     ```
@@ -78,7 +78,7 @@
 
 ## Session Management
 
 - **Session type:** httpOnly, secure, sameSite=lax cookie
 - **Wallet session timeout:** 15 minutes idle timeout
 - **Logout:** `POST /v1/auth/logout` clears the session cookie
 

api-setup/getting-started.mdx

@@ -20,7 +20,7 @@
     Use the API to create a payment request
   </Step>
   <Step title="Process Payment">
     Get payment calldata and execute the transaction
   </Step>
 </Steps>
 
@@ -38,9 +38,10 @@
 ### Client ID Generation
 
 1. Log in to [Request Dashboard](https://dashboard.request.network)
-2. Open your payment destination's **Client IDs** section
-3. Click **Generate New Client ID**
-4. Copy and securely store the Client ID
+2. **Create a payment destination first** if you haven't — the Client IDs section is only available once a destination exists. From the Home page, click **Set up payment destination** and pick the chain + token you want to receive on.
+3. Open **Manage Destination → Client IDs**
+4. Click **Generate your first Client ID** (or **Generate New Client ID** if you already have one)
+5. Copy and securely store the Client ID
 
 <Warning>
 **Security Best Practices**
@@ -128,7 +129,7 @@
 The response will include:
 - `requestId` — Unique identifier for the request
 - `paymentReference` — Used to track the payment
 - `transactions` — Array of transaction calldata to execute
 - `metadata` — Additional info like `stepsRequired` and `needsApproval`
 
 ### Understanding the Response