Update EIP-4844: clarify blob coupling

Merged by EIP-Bot.

Author: ralexstokes

EIPS/eip-4844.md

@@ -405,7 +405,7 @@ The values for `TARGET_DATA_GAS_PER_BLOCK` and `MAX_DATA_GAS_PER_BLOCK` are chos
 
 This EIP introduces a transaction type that has a distinct mempool version and execution-payload version,
 with only one-way convertibility between the two. The blobs are in the network representation and not in the consensus representation;
-instead, they go into the `BeaconBlockBody`. This means that there is now a part of a transaction that will not be accessible from the web3 API.
+instead, they are coupled with the beacon block. This means that there is now a part of a transaction that will not be accessible from the web3 API.
 
 ### Mempool issues