Update ERC-7540: Update ERC7540

Merged by EIP-Bot.
ethereum · Jun 3, 2024 · f532512 · f532512
1 parent 1d67a40
commit f532512
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/ERCS/erc-7540.md b/ERCS/erc-7540.md
@@ -187,7 +187,7 @@ MUST NOT revert unless due to integer overflow caused by an unreasonably large i
 
 Assumes control of `shares` from `owner` and submits a Request for asynchronous `redeem`. This places the Request in Pending state, with a corresponding increase in `pendingRedeemRequest` for the amount `shares`. 
 
-The output `requestId` is used to partially discriminate the request along with the `controller`. See [Request Ids](#request-ids) section for more info.
+The output `requestId` is used to discriminate the request along with the `controller`. See [Request Ids](#request-ids) section for more info.
 
 `shares` MAY be temporarily locked in the Vault until the Claimable or Claimed state for accounting purposes, or they MAY be burned immediately upon `requestRedeem`. 
 
@@ -490,7 +490,7 @@ It reduces code and implementation complexity at little to no cost to simply man
 
 ### Mandated Support for [ERC-165](./eip-165.md)
 
-Implementing support for [ERC-165](./eip-165.md) is mandated because of the [optionality of flows](#optionality-of-flows). Integrations can use the `supportsInterface` method to check whether a vault is fully asynchronous, partially asynchronous, or fully synchronous, and use a single contract to support all cases.
+Implementing support for [ERC-165](./eip-165.md) is mandated because of the [optionality of flows](#optionality-of-flows). Integrations can use the `supportsInterface` method to check whether a vault is fully asynchronous, partially asynchronous, or fully synchronous (for which it is just following the [ERC-4626](./eip-4626)), and use a single contract to support all cases.
 
 ### Not Allowing Pending Claims to be Fungible
 The async pending claims represent a sort of semi-fungible intermediate share class. Vaults can elect to wrap these claims in any token standard they like, for example, ERC-20, [ERC-1155](./eip-1155.md), or ERC-721 depending on the use case. This is intentionally left out of the spec to provide flexibility to implementers.