small fix

Author: fradamt

EIPS/eip-9999.md

@@ -59,11 +59,11 @@ Test cases should verify that:
 
 1. Slashed validators are not selected as proposers
 2. A complete `proposer_lookahead` is generated even in the presence of slashed validators
-3. Slashinigs do not affect the existing `proposer_lookahead`
+3. Slashings do not affect the existing `proposer_lookahead`
 
 ## Security considerations
 
-Slashed validators are already prevented from successfully proposing blocks through the state transition validation, for good reason, as they are considered to be unreliable participants (malicious or faulty). However, they have historically still been eligible to be selected as proposers in order to ensure stability of the proposer selection mechanism, because excluding them would have severely impacted the stability of the proposer selection mechanism. In fact, any slashing processed on chain would have caused the sequence of future proposers to completely change, even within the lookahead window. However, with [EIP-7970](./eip-7970.md), the proposer selection is fixed in advance by storing in the Beacon state, so it would not be affected by slashings processed after the fact.
+Slashed validators are already prevented from successfully proposing blocks through the state transition validation, for good reason, as they are considered to be unreliable participants (malicious or faulty). However, they have historically still been eligible to be selected as proposers in order to ensure stability of the proposer selection mechanism, because excluding them would have severely impacted the stability of the proposer selection mechanism. In fact, any slashing processed on chain would have caused the sequence of future proposers to completely change, even within the lookahead window. However, with [EIP-7917](./eip-7917.md), the proposer selection is fixed in advance by storing in the Beacon state, so it would not be affected by slashings processed after the fact.
 
 ### Impact on proposer selection distribution