update based on PR comments

ERCS/erc-7674.md

@@ -1,7 +1,7 @@
 ---
 eip: 7674
 title: Temporary Approval Extension for ERC-20
-description: An interface for ERC-20 approvals via transient storage
+description: An interface for ephemeral ERC-20 approvals
 author: Xenia Shape (@byshape), Mikhail Melnik (@ZumZoom), Hadrien Croubois (@Amxx)
 discussions-to: https://ethereum-magicians.org/t/add-erc-7674-transient-approval-extension-for-erc-20/19521
 status: Draft
@@ -13,11 +13,11 @@ requires: 20, 1153
 
 ## Abstract
 
-This specification defines the minimum interface required to temporarily approve `ERC-20` tokens for spending within a single transaction.
+This specification defines the minimum interface required to temporarily approve `ERC-20` tokens for spending within the same transaction.
 
 ## Motivation
 
-`EIP-1153` allows to use a cheaper way to temporarily store allowances.
+User are often require to set token approval that will only be used once. It is common to leave unexpected approvals after these interactions. [EIP-1153](./eip-1153.md) introduces a cheap way to handle temporarily allowances.
 
 ## Specification
 
@@ -27,15 +27,15 @@ Compliant contracts MUST implement 1 new function in addition to `ERC-20`:
 ```solidity
 function temporaryApprove(address spender, uint256 value) public returns (bool success)
 ```
-Call to `temporaryApprove(spender, value)` allows `spender` to withdraw within the same transaction from `msg.sender` multiple times, up to the `value` amount.
+Call to `temporaryApprove(spender, value)` allows `spender` to withdraw within the same transaction from `msg.sender` multiple times, up to the `value` amount.  This temporary allowance is to be considered in addition to the normal (persistent) ERC20 allowance, the total value than spender is able to spend during the transaction is thus capped by the sum of the temporary and the normal (persistent) allowances.
 
 The storage for the temporary allowances MUST be different to that of the regular allowance. Compliant contracts MAY use the transient storage `EIP-1153` to keep the temporary allowance. For each `owner` and `spender`, the slot MUST be uniquely selected to avoid slot collision. Each slot index SHOULD be derived from the base slot index for temporary allowances, `owner` and `spender` addresses. Slot MAY be derived as `keccak256(spender . keccak256(owner . p))` where `.` is concatenation and `p` is `keccak256` from the string uniquely defining temporary allowances in the namespace of the implementing contract.
 
 Compliant contracts MUST add a temporary allowance check to the `transferFrom` function. The permanent allowance SHOULD only be spent after the temporary allowance has been exhausted.
 
 Compliant contracts MUST add a temporary allowance to the permanent one when returning the allowed amount to spend in the `allowance` function. In case the sum of the temporary and permanent allowance overflow, `type(uint256).max` MUST be returned.
 
-No event is required when setting a temporary allowance, but compliant contracts MAY implement it.
+No event is required when setting a temporary allowance, but compliant contracts MAY emit a specific event.
 
 ## Rationale
 
@@ -47,7 +47,7 @@ All functionality of the `ERC-20` standard is backward compatible except for the
 
 ## Reference Implementation
 
-TBD
+TBD <!-- TODO -->
 
 ## Security Considerations