Update EIP-4444: Update eip-4444.md

Merged by EIP-Bot.

Author: 0xbasar

EIPS/eip-4444.md

@@ -76,7 +76,7 @@ In the second phase, history is pruned by default and the command line option is
 
 ### JSON-RPC changes
 
-After this proposal is implemented, certain JSON-RPC endpoints (e.g. like `getBlockByHash`) won't be able to tell whether a given hash is invalid or just too old. Other endpoints like `getLogs` will simply no longer have the data the user is requesting. The way this regression should be handled by applications or clients is out-of-scope for this proposal.
+After this proposal is implemented, certain JSON-RPC endpoints (e.g. like `getBlockByHash`) won't be able to tell whether a given hash is invalid or just outdated. Other endpoints like `getLogs` will simply no longer have the data the user is requesting. The way this regression should be handled by applications or clients is out-of-scope for this proposal.
 
 ## Security Considerations
 
@@ -98,7 +98,7 @@ Furthermore, there is a risk that more dapps will rely on centralized services f
 
 ### Confusion with other proposals
 
-Because there are a number of alternative proposals for reducing the execution client's footprint on disk, we've decided to enforce a specific pronouncination of the EIP. When pronouncing the EIP number, it **MUST** be pronounced EIP "four fours". All other pronounciations are incorrect.
+Because there are a number of alternative proposals for reducing the execution client's footprint on disk, we've decided to enforce a specific pronunciation of the EIP. When pronouncing the EIP number, it **MUST** be pronounced EIP "four fours". All other pronounciations are incorrect.
 
 ## Copyright
 Copyright and related rights waived via [CC0](../LICENSE.md).