fix: Typos (#186)

* fix: Typos

* fix: Typo

---------

Co-authored-by: marktoda <toda.mark@gmail.com>

README.md

@@ -1,6 +1,6 @@
 # permit2
 
-Permit2 introduces a low-overhead, next generation token approval/meta-tx system to make token approvals easier, more secure, and more consistent across applications.
+Permit2 introduces a low-overhead, next-generation token approval/meta-tx system to make token approvals easier, more secure, and more consistent across applications.
 
 ## Features
 
@@ -11,7 +11,7 @@ Permit2 introduces a low-overhead, next generation token approval/meta-tx system
 - **Safe Arbitrary Data Verification**: Verify any extra data by passing through a witness hash and witness type. The type string must follow the [EIP-712](https://eips.ethereum.org/EIPS/eip-712) standard.
 - **Signature Verification for Contracts**: All signature verification supports [EIP-1271](https://eips.ethereum.org/EIPS/eip-1271) so contracts can approve tokens and transfer tokens through signatures.
 - **Non-monotonic Replay Protection**: Signature based transfers use unordered, non-monotonic nonces so that signed permits do not need to be transacted in any particular order.
-- **Expiring Approvals**: Approvals can be time-bound, removing security concerns around hanging approvals on a wallet’s entire token balance. This also means that revoking approvals do not necessarily have to be a new transaction since an approval that expiries will no longer be valid.
+- **Expiring Approvals**: Approvals can be time-bound, removing security concerns around hanging approvals on a wallet’s entire token balance. This also means that revoking approvals do not necessarily have to be a new transaction since an approval that expires will no longer be valid.
 - **Batch Revoke Allowances**: Remove allowances on any number of tokens and spenders in one transaction.
 
 ## Architecture
@@ -24,7 +24,7 @@ The `AllowanceTransfer` contract handles setting allowances on tokens, giving pe
 
 ## Integrating with Permit2
 
-Before integrating contracts can request users’ tokens through `Permit2`, users must approve the `Permit2` contract through the specific token contract. To see a detailed technical reference, visit the Uniswap [documentation site](https://docs.uniswap.org/contracts/permit2/overview).
+Before integrating, contracts can request users’ tokens through `Permit2`, users must approve the `Permit2` contract through the specific token contract. To see a detailed technical reference, visit the Uniswap [documentation site](https://docs.uniswap.org/contracts/permit2/overview).
 
 ### Note on viaIR compilation
 Permit2 uses viaIR compilation, so importing and deploying it in an integration for tests will require the integrating repository to also use viaIR compilation. This is often quite slow, so can be avoided using the precompiled `DeployPermit2` utility:

src/interfaces/IAllowanceTransfer.sol

@@ -53,7 +53,7 @@ interface IAllowanceTransfer is IEIP712 {
         uint48 nonce;
     }
 
-    /// @notice The permit message signed for a single token allownce
+    /// @notice The permit message signed for a single token allowance
     struct PermitSingle {
         // the permit data for a single token alownce
         PermitDetails details;