reduce diff

EIPS/eip-7742.md

@@ -48,7 +48,9 @@ The blob maximum is verified in the CL node and the EL inherits this verificatio
 versioned hashes corresponding to each blob as specified by the Engine API. Because of this, the strict check specified
 by EIP-4844 is unnecessary.
 
-For optimistically synced blocks from peer nodes, EL may further assume that the entire ancestor EL peer synced chain blocks correctly obeys this condition by the canonicality and correctness of the block they backfilling from as instructed by the CL. Hence we entirely deprecated the `MAX_BLOB_GAS_PER_BLOCK` checks from [EIP-4844](./eip-4844.md) in the EL.
+For optimistically synced blocks from peer nodes, EL may further assume that the entire ancestor EL peer synced chain
+blocks correctly obeys this condition by the canonicality and correctness of the block they backfilling from as instructed
+by the CL. Hence we entirely deprecated the `MAX_BLOB_GAS_PER_BLOCK` checks from [EIP-4844](./eip-4844.md) in the EL.
 
 #### Target blobs per block
 
@@ -58,13 +60,18 @@ the blob max is desirable to reduce rigidity in this protocol parameter.
 
 Even if the EL keeps a fixed target value based on the max, removing the max implies the EL would not know what the target
 value should be. To address this lack of information, this EIP proposes the CL sends the current target value to the EL
-with each provided payload over the Engine API. The EL block header will also need to be extended with this target value (`target_blobs_per_block`) to preserve the security of optimistic sync.
+with each provided payload over the Engine API. The EL block header will also need to be extended with this target value
+(`target_blobs_per_block`) to preserve the security of optimistic sync.
 
 #### Normalized `excess_gas`
 
-With the changing target, we also need to scale the `BLOB_BASE_FEE_UPDATE_FRACTION` from [EIP-4844](./eip-4844.md) accordingly to bound the price jumps by +-12.5%. But this introduces some irregularity whenever target gets updated because excess blob gas (accumulated via old target) is now effectively scaled down by this changed fraction in the fee calculations.
+With the changing target, we also need to scale the `BLOB_BASE_FEE_UPDATE_FRACTION` from [EIP-4844](./eip-4844.md)
+accordingly to bound the price jumps by +-12.5%. But this introduces some irregularity whenever target gets updated because
+excess blob gas (accumulated via old target) is now effectively scaled down by this changed fraction in the fee calculations.
 
-To mitigate this irregularity, we now save a _normalized_ excess gas with respect to a fixed `EXCESS_BLOB_GAS_NORMALIZATION_TARGET` and use a corresponding `BLOB_BASE_FEE_UPDATE_FRACTION_NORMALIZED` in the base fee calculations.
+To mitigate this irregularity, we now save a _normalized_ excess gas with respect to a fixed
+`EXCESS_BLOB_GAS_NORMALIZATION_TARGET` and use a corresponding `BLOB_BASE_FEE_UPDATE_FRACTION_NORMALIZED` in the base fee
+calculations.
 
 ## Specification