diff --git a/blog/gas-optimization.md b/blog/gas-optimization.md
index f40897b2db..48ef3445b3 100644
--- a/blog/gas-optimization.md
+++ b/blog/gas-optimization.md
@@ -99,7 +99,7 @@ When optimizing smart contracts, it’s important to identify areas of the code
 The most expensive operations on Ethereum (and most other L1 blockchains) typically involve storing and fetching data that must persist across transactions and blocks. The totality of this data is referred to as the blockchain’s *state*. If we zoom in to the subset of that state associated with a particular smart contract, we refer to it as the contract’s *storage*.
 
 :::note Disk vs Memory
-A quick aside: storing and retrieving state is so expensive because it must reside on [disk](https://en.wikipedia.org/wiki/Disk_storage), as it’s too large to fit in [memory](https://en.wikipedia.org/wiki/Random-access_memory). For more information on these types of tradeoffs in blockchain settings, see [The Limits to Blockchain Scalability](https://vitalik.ca/general/2021/05/23/scaling.html).
+A quick aside: storing and retrieving state is so expensive because it must reside on [disk](https://en.wikipedia.org/wiki/Disk_storage), as it’s too large to fit in [memory](https://en.wikipedia.org/wiki/Random-access_memory). For more information on these types of tradeoffs in blockchain settings, see [The Limits to Blockchain Scalability](https://vitalik.eth.limo/general/2021/05/23/scaling.html).
 :::
 
 So, returning to optimization, it’s clear that one of our primary goals should be to minimize our contract’s use of storage, as this can lead to massive savings for end-users.
diff --git a/docs/api/subgraph/guides/subgraph-example.md b/docs/api/subgraph/guides/subgraph-example.md
index d15acbea66..4c163aa333 100644
--- a/docs/api/subgraph/guides/subgraph-example.md
+++ b/docs/api/subgraph/guides/subgraph-example.md
@@ -79,7 +79,7 @@ The query below returns the feeTier, spot price, and liquidity for the ETH-USDC
 
 ### All Possible Pools
 
-The maxiumum items you can query at once is 1000. Thus to get all possible pools, you can interate using the skip variable. To get pools beyond the first 1000 you can also set the skip as shown below.
+The maximum items you can query at once is 1000. Thus to get all possible pools, you can iterate using the skip variable. To get pools beyond the first 1000 you can also set the skip as shown below.
 
 ### Skipping First 1000 Pools
 
@@ -280,7 +280,7 @@ query tokens($skip: Int!) {
 
 ### General Position Data
 
-To get data about a specific position, input the NFT tokenId. This queries the collected fees for token0 and token1 and current liquidity for the position with tokedId 3. Reference the full [position schema](https://github.com/Uniswap/v3-subgraph/blob/main/schema.graphql#L192) to see all fields.
+To get data about a specific position, input the NFT tokenId. This queries the collected fees for token0 and token1 and current liquidity for the position with tokenId 3. Reference the full [position schema](https://github.com/Uniswap/v3-subgraph/blob/main/schema.graphql#L192) to see all fields.
 
 ```
 {
diff --git a/docs/concepts/governance/01-overview.md b/docs/concepts/governance/01-overview.md
index 6cc8d1f222..5ea48a0f10 100644
--- a/docs/concepts/governance/01-overview.md
+++ b/docs/concepts/governance/01-overview.md
@@ -51,11 +51,11 @@ import GovernorAlpha from '@uniswap/governance/build/GovernorAlpha.json'
 
 ## GovernorAlpha v2 (Deprecated)
 
-`GovernerAlpha v2` is deployed at `0xC4e172459f1E7939D522503B81AFAaC1014CE6F6` on the Ethereum [mainnet](https://etherscan.io/address/0xC4e172459f1E7939D522503B81AFAaC1014CE6F6).
+`GovernorAlpha v2` is deployed at `0xC4e172459f1E7939D522503B81AFAaC1014CE6F6` on the Ethereum [mainnet](https://etherscan.io/address/0xC4e172459f1E7939D522503B81AFAaC1014CE6F6).
 
 ### ABI
 
-The `GovernerAlpha v2` ABI is viewable on [Etherscan](https://etherscan.io/address/0xC4e172459f1E7939D522503B81AFAaC1014CE6F6)
+The `GovernorAlpha v2` ABI is viewable on [Etherscan](https://etherscan.io/address/0xC4e172459f1E7939D522503B81AFAaC1014CE6F6)
 
 ## GovernorBravo (Current)
 
diff --git a/docs/contracts/v1/guides/01-connect-to-uniswap.md b/docs/contracts/v1/guides/01-connect-to-uniswap.md
index 98a19a67e9..2627b047c7 100644
--- a/docs/contracts/v1/guides/01-connect-to-uniswap.md
+++ b/docs/contracts/v1/guides/01-connect-to-uniswap.md
@@ -3,7 +3,7 @@ id: connect-to-uniswap
 title: Connect to Uniswap
 ---
 
-The Uniswap smart contracts exist on the Ethereum blockchain. Use [ethers.js](https://github.com/ethers-io/ethers.js/) or [web3.js](https://github.com/ethereum/web3.js) to connect your website to Ethereum. Users will need a web3-enabled browser. On desktop this means using the [MetaMask](https://metamask.io/) extension or something similar. On mobile, web3-compatible browsers include [Trust Wallet](https://trustwalletapp.com/) and [Coinbase Wallet](https://wallet.coinbase.com/). See [ethereum.org](https://ethereum.org/use/#_3-what-is-a-wallet-and-which-one-should-i-use) to learn more.
+The Uniswap smart contracts exist on the Ethereum blockchain. Use [ethers.js](https://github.com/ethers-io/ethers.js/) or [web3.js](https://github.com/ethereum/web3.js) to connect your website to Ethereum. Users will need a web3-enabled browser. On desktop this means using the [MetaMask](https://metamask.io/) extension or something similar. On mobile, web3-compatible browsers include [Trust Wallet](https://trustwallet.com/) and [Coinbase Wallet](https://wallet.coinbase.com/). See [ethereum.org](https://ethereum.org/use/#_3-what-is-a-wallet-and-which-one-should-i-use) to learn more.
 
 # Factory Contract