Update EIP-7523: fix typo (#8025)

Update eip-7523.md

EIPS/eip-7523.md

@@ -22,7 +22,7 @@ The possibility of empty accounts is a historical artifact of the early history
 
 Despite empty accounts no longer existing, they still impose a legacy of technical debt. [EIP-161](./eip-161.md) imposes complicated rules that require a client to delete an empty account when it is "touched". As the Ethereum specification continues to evolve new edgecases of the "touch" rules arise which must be debated, implemented, tested and documented. If a future client wishes to only support post-merge blocks it must implement unnecessary empty account support solely to pass the test suite.
 
-By prohibiting empty accounts on post-merge networks, this EIP frees designers and implementors of Ethereum and related blockchains from the burden of having to consider them going forward.
+By prohibiting empty accounts on post-merge networks, this EIP frees designers and implementers of Ethereum and related blockchains from the burden of having to consider them going forward.
 
 ## Specification
 
@@ -46,7 +46,7 @@ The Ethereum specification is declared to be undefined in the presence of an emp
 
 ## Rationale
 
-This EIP was drafted to be the simpliest possible way of eliminating the long term technical debt imposed by empty accounts. The Merge was chosen as a natural easily identifiable cutoff point.
+This EIP was drafted to be the simplest possible way of eliminating the long term technical debt imposed by empty accounts. The Merge was chosen as a natural easily identifiable cutoff point.
 
 Alternative approaches include: