docs(deposit-addresses): clarify reindex section and link API ref to …

features/deposit-addresses.mdx

@@ -1249,7 +1249,7 @@ curl -X GET "https://api.relay.link/intents/status/v3?requestId=<REQUEST_ID>"
 
 ### Reindexing Stuck Deposits
 
-Relay runs a background monitor that checks for deposits of the originally quoted token. If a user sent a different supported (solver) token, the background monitor may not detect it automatically. Use the [Deposit Address Reindex](/references/api/deposit-address-reindex) endpoint to trigger on-demand re-detection. This checks all solver currency balances on the specified chain and triggers sweeps for any detected deposits.
+Relay's background monitor only checks the originally quoted input token. If a user sent a different supported (solver) token, the monitor may not detect it automatically. Use the [Deposit Address Reindex](/references/api/deposit-address-reindex) endpoint to trigger on-demand re-detection — it checks every solver-depositable currency on the chain and queues a sweep for any non-zero balances.
 
 ```bash
 curl -X POST 'https://api.relay.link/transactions/deposit-address/reindex' \
@@ -1260,25 +1260,21 @@ curl -X POST 'https://api.relay.link/transactions/deposit-address/reindex' \
   }'
 ```
 
-You can also pass `targetChainId` to reindex a deposit that landed on a different chain than originally quoted. This is useful for operational recovery when funds were sent to the right address but on the wrong chain.
+**`chainId` is the chain the deposit address was originally registered on.** Pass `targetChainId` to run the reindex on a different chain — useful when funds were sent to the right address but on the wrong chain (e.g. the address was registered for Arbitrum but funds landed on Ethereum). This is the chain being reindexed, not the destination chain of the original quote.
 
-Pass `currency` to scope the reindex to a single currency address rather than iterating every depositable currency on the chain. This accepts any currency registered with Relay on the target chain — including currencies that aren't on the standard solver-depositable list — and is useful when funds landed in a token outside that list (for example, a HyperCore-registered token when the deposit address was created for HyperEVM). Unknown currencies return `400`.
+Pass `currency` to scope the reindex to a single currency address instead of iterating every depositable currency. Any currency registered with Relay on the target chain is accepted — including currencies outside the standard solver-depositable list (e.g. a HyperCore-registered token when the deposit address was created for HyperEVM).
 
 ```bash
 curl -X POST 'https://api.relay.link/transactions/deposit-address/reindex' \
   -H 'Content-Type: application/json' \
   -d '{
-    "chainId": 999,
+    "chainId": 42161,
     "depositAddress": "0x1ba74e01d46372008260ec971f77eb6032b938a4",
-    "targetChainId": 1337,
-    "currency": "0x6d1e7cde53ba9467b783cb7c530ce054"
+    "targetChainId": 1,
+    "currency": "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48"
   }'
 ```
 
-<Info>
-The background monitor only checks the originally quoted input token. If a different supported token was sent, the monitor won't detect it. Reindex checks all solver-depositable currencies and is the fallback path for these cases.
-</Info>
-
 <Note>
 The deposit transaction hash cannot be used to look up the status of a deposit address bridge. Always use the deposit address itself or the `requestId` to track status.
 </Note>

references/api/deposit-address-reindex.mdx

@@ -3,3 +3,5 @@ title: "Deposit Address Reindex"
 description: "Reindex transactions for a deposit address"
 openapi: post /transactions/deposit-address/reindex
 ---
+
+[What are deposit addresses?](/features/deposit-addresses)