Update EIP-101: fix typo (#8016)

Update eip-101.md

EIPS/eip-101.md

@@ -56,7 +56,7 @@ This essentially implements signature and nonce checking, and if both checks pas
 Miners can follow the following algorithm upon receiving transactions:
 
 1.  Run the code for a maximum of 50000 gas, stopping if they see an operation or call that threatens to go over this limit
-2.  Upon seeing that operation, make sure that it leaves at last 50000 gas to spare (either by checking that the static gas consumption is small enough or by checking that it is a call with `msg.gas - 50000` as its gas limit parameter)
+2.  Upon seeing that operation, make sure that it leaves at least 50000 gas to spare (either by checking that the static gas consumption is small enough or by checking that it is a call with `msg.gas - 50000` as its gas limit parameter)
 3.  Pattern-match to make sure that gas payment code at the end is *exactly* the same as in the code above.
 
 This process ensures that miners *waste* at most 50000 gas before knowing whether or not it will be worth their while to include the transaction, and is also highly general so users can experiment with new cryptography (eg. ed25519, Lamport), ring signatures, quasi-native multisig, etc. Theoretically, one can even create an account for which the *valid signature* type is a valid Merkle branch of a receipt, creating a quasi-native alarm clock.