docs: typos

README.md

@@ -8,7 +8,7 @@ A plugin to send sponsored transactions utilizing account abstraction!
 
 ## What
 
-This plugin sponsors any transaction the user sends through the power of account abstraction. Through seemless integration after the configuration is set just submit any transaction, and you can see it get mined on the testnets without costing the signer any gas! 
+This plugin sponsors any transaction the user sends through the power of account abstraction. Through seamless integration after the configuration is set just submit any transaction, and you can see it get mined on the testnets without costing the signer any gas! 
 
 ## Installation
 
@@ -162,7 +162,7 @@ And more!
 
 ## Usage
 
-> **⚠ WARNING: Any non-zero msg.value call will not work as intended as paymaster's dont sponsor this value, in order to use native transfers or interact with payable functions you will need the native token of your chain in the smart account wallet beforehand**
+> **⚠ WARNING: Any non-zero msg.value call will not work as intended as paymaster's don't sponsor this value, in order to use native transfers or interact with payable functions you will need the native token of your chain in the smart account wallet beforehand**
 
 After you have setup the configuration for the `accountAbstraction` and you are using a network that has them enable you are good to go, you can right a simple script below and your transactions will be mined on the testnet that you have configured!
 
@@ -181,7 +181,7 @@ Deploying contracts works just as any other transaction would, however due to th
 
 - **Ownable contracts**
 
-    We do support ownable contracts and the default `owner` of your contract will be the smart account you deployed with, the only condition is you must have a `transferOwnership(address)` function to make this work, if you have a custom implementation of `Ownable` and dont instantiate `owner` as `msg.sender` in the constructor it will also work.
+    We do support ownable contracts and the default `owner` of your contract will be the smart account you deployed with, the only condition is you must have a `transferOwnership(address)` function to make this work, if you have a custom implementation of `Ownable` and don't instantiate `owner` as `msg.sender` in the constructor it will also work.
 
 - **Contract addresses in scripts**