Update EIP-7251: Update eip-7251.md

Merged by EIP-Bot.

EIPS/eip-7251.md

@@ -41,7 +41,6 @@ With the security model of the protocol no longer dependent on a low value for `
 | `MIN_CONSOLIDATION_REQUEST_FEE` | `1` | |
 | `CONSOLIDATION_REQUEST_FEE_UPDATE_FRACTION` | `17` | |
 | `EXCESS_INHIBITOR` | `2**256-1` | Excess value used to compute the fee before the first system call |
-| `FORK_TIMESTAMP` | *TBD* | Mainnet |
 
 #### Consensus layer
 
@@ -537,7 +536,7 @@ Address: 0x00431F263cE400f4455c2dCf564e53007Ca4bbBb
 
 #### Block processing
 
-At the end of processing any execution block where `block.timestamp >= FORK_TIMESTAMP` (i.e. after processing all transactions and after performing the block body requests validations) client software **MUST** take the following steps:
+At the end of processing any execution block where this EIP is active (i.e. after processing all transactions and after performing the block body requests validations) client software **MUST** take the following steps:
 
 1. Call the contract as `SYSTEM_ADDRESS` and empty input data to trigger the system subroutine execute.
 2. Check that consolidation requests in the [EIP-7685](./eip-7685.md) requests list matches the list returned from `dequeue_consolidation_requests()` function of the smart contract respecting the order of the returned requests. If this condition does not hold, the block **MUST** be deemed *invalid*.