Update ERC-5189: EIP-5189 Typos

Merged by EIP-Bot.

ERCS/erc-5189.md

@@ -80,7 +80,7 @@ interface Endorser {
     bool nonce;
     bool allSlots;
     bytes32[] slots;
-    Contraint[] constraints;
+    Constraint[] constraints;
   }
 
   function isOperationReady(
@@ -103,7 +103,7 @@ Endorsers SHOULD be registered in the `EndorserRegistry` with a minimum amount o
 
 When the `isOperationReady` method is called, the endorser must return this information:
 
-* **readiness:** when returning`true`, it means the transaction WILL be executed correctly and the bundler WILL be paid the offered gas fees (even if the underlying intent of the operation fails).
+* **readiness:** when returning `true`, it means the transaction WILL be executed correctly and the bundler WILL be paid the offered gas fees (even if the underlying intent of the operation fails).
 * **blockDependency:** maximum values for block values; once the block reaches these values, the `readiness` result MUST be re-evaluated.
 * **dependencies:** a comprehensive list of addresses and storage slots that must be monitored; any state change in these dependencies MUST trigger a re-evaluation of the operation's readiness.
 
@@ -112,6 +112,8 @@ The information provided by the endorser helps the mempool operator maintain a p
 For efficiency, additional information CAN be provided to the endorser with `_endorserCallData`.
 If used, the endorser MUST validate that the provided `_endorserCallData` is valid and relevant to the other values provided.
 
+While the `isOperationReady` call is not a view function, calls to the endorser MUST NOT be submitted on chain. Calls to `isOperationReady` MUST only be made off-chain by the bundler.
+
 ### Block Dependencies
 
 | Field        | Type    | Description                                                         |