Update packages/thirdweb/src/bridge/Sell.ts

gregfromstl · graphite-app[bot] · web-flow · commit 06358c6335fd · 2025-05-20T10:38:14.000-07:00
Co-authored-by: graphite-app[bot] &lt;96075541+graphite-app[bot]@users.noreply.github.com&gt;
Signed-off-by: greg &lt;gregfromstl@gmail.com&gt;
diff --git a/packages/thirdweb/src/bridge/Sell.ts b/packages/thirdweb/src/bridge/Sell.ts
@@ -251,7 +251,7 @@ export declare namespace quote {
  * ```
  *
  * ## Sending the transactions
- * The `transactions` array is a series of transactions ready to be executed (with `sendTransaction`) must be executed one after the other in order to fulfill the complete route. There are a few things to keep in mind when executing these transactions:
++ * The `transactions` array is a series of transactions ready to be executed (with `sendTransaction`) one after the other in order to fulfill the complete route. There are a few things to keep in mind when executing these transactions:
  *  - Approvals will have the `approval` action specified. You can perform approvals with `sendAndConfirmTransaction`, then proceed to the next transaction.
  *  - All transactions are assumed to be executed by the `sender` address, regardless of which chain they are on. The final transaction will use the `receiver` as the recipient address.
  *  - If an `expiration` timestamp is provided, all transactions must be executed before that time to guarantee successful execution at the specified price.

Original file line number	Diff line number	Diff line change
`@@ -251,7 +251,7 @@ export declare namespace quote {`
`251`	`251`	* ```
`252`	`252`	`*`
`253`	`253`	`* ## Sending the transactions`
`254`		- * The `transactions` array is a series of transactions ready to be executed (with `sendTransaction`) must be executed one after the other in order to fulfill the complete route. There are a few things to keep in mind when executing these transactions:
	`254`	++ * The `transactions` array is a series of transactions ready to be executed (with `sendTransaction`) one after the other in order to fulfill the complete route. There are a few things to keep in mind when executing these transactions:
`255`	`255`	* - Approvals will have the `approval` action specified. You can perform approvals with `sendAndConfirmTransaction`, then proceed to the next transaction.
`256`	`256`	* - All transactions are assumed to be executed by the `sender` address, regardless of which chain they are on. The final transaction will use the `receiver` as the recipient address.
`257`	`257`	* - If an `expiration` timestamp is provided, all transactions must be executed before that time to guarantee successful execution at the specified price.