authCapture: keep multi-accepts hint in the assetTransferMethod cell

Two sentences in a cell is fine; lifting it out and back in was overkill.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Author: A1igator

specs/schemes/authCapture/scheme_authCapture_evm.md

@@ -57,9 +57,7 @@ AuthCapture-accepting servers advertise with scheme `authCapture`:
 | `minFeeBps`           | Yes      | `uint16`                 | Minimum fee in basis points (the fee floor the captureAuthorizer must take). `0` = no minimum.            |
 | `maxFeeBps`           | Yes      | `uint16`                 | Maximum fee in basis points (the cap on the captureAuthorizer's fee).                                     |
 | `autoCapture`         | No       | `bool`                   | `true` → facilitator calls `charge()` (atomic). `false` → `authorize()` (two-phase). Default: `false`.    |
-| `assetTransferMethod` | No       | `"eip3009" \| "permit2"` | Which token collector to use. Default: `"eip3009"`.                                                       |
-
-A server MAY list multiple `accepts[]` entries with different `assetTransferMethod` values so clients can pick the method matching their token approvals.
+| `assetTransferMethod` | No       | `"eip3009" \| "permit2"` | Which token collector to use. Default: `"eip3009"`. A server MAY list multiple `accepts[]` entries with different `assetTransferMethod` values so clients can pick the method matching their token approvals. |
 
 **Universal contract addresses** (same on every supported EVM chain via deterministic CREATE2):