diff --git a/docs/ERRORS.md b/docs/ERRORS.md
index 52449c7d3e..024063f1b6 100644
--- a/docs/ERRORS.md
+++ b/docs/ERRORS.md
@@ -242,7 +242,7 @@ Useful links for troubleshooting:
 
 - More detailed graph-node [docs](https://github.com/graphprotocol/graph-node/blob/master/docs/getting-started.md)
 - [How to change postgres user password](https://chartio.com/resources/tutorials/how-to-set-the-default-user-password-in-postgresql/)
-- [Install and start](https://linuxhint.com/postgresql_installation_guide_ubuntu_20-04/) postgres in Ubunutu
+- [Install and start](https://linuxhint.com/postgresql_installation_guide_ubuntu_20-04/) postgres in Ubuntu
 - [See port number](https://stackoverflow.com/a/38011366) postgres is on
 - [WSL download](https://docs.microsoft.com/en-us/windows/wsl/install-manual#step-4---download-the-linux-kernel-update-package) instructions
 
diff --git a/subgraphs/aave-forks/src/helpers.ts b/subgraphs/aave-forks/src/helpers.ts
index 2031cea7cf..3973d55939 100644
--- a/subgraphs/aave-forks/src/helpers.ts
+++ b/subgraphs/aave-forks/src/helpers.ts
@@ -337,7 +337,7 @@ export function getInterestRateType(
       }
 
       log.info(
-        "[getInterestRateType]event at logIndex {} signature {} not match the exepected Transfer signature {}. tx {}-{} ",
+        "[getInterestRateType]event at logIndex {} signature {} not match the expected Transfer signature {}. tx {}-{} ",
         [
           thisLog.logIndex.toString(),
           logSignature.toHexString(),
diff --git a/subgraphs/gmx-forks/protocols/mummy-finance/README.md b/subgraphs/gmx-forks/protocols/mummy-finance/README.md
index 8aea012d40..0e4283c196 100644
--- a/subgraphs/gmx-forks/protocols/mummy-finance/README.md
+++ b/subgraphs/gmx-forks/protocols/mummy-finance/README.md
@@ -91,7 +91,7 @@ The usage metrics for MMY take the following user activities into accout.
 
 > TVL of the Protocol = ∑ TVL of the multi-asset pool
 
-_Note: The collateral of traders are also reserved in the MLP pool. Hence, there are two types of transactions to deposit tokens to the pool, which are the users who provide liquidity and another one for the traders who provide collaterals before trading. The subgraph only counts the tokens to be provided as liqiudity into TVL and does not add positions' collaterals to the pool's TVL, in order to be consistent with MMY official measurement._
+_Note: The collateral of traders are also reserved in the MLP pool. Hence, there are two types of transactions to deposit tokens to the pool, which are the users who provide liquidity and another one for the traders who provide collaterals before trading. The subgraph only counts the tokens to be provided as liquidity into TVL and does not add positions' collaterals to the pool's TVL, in order to be consistent with MMY official measurement._
 
 ### Volume
 
diff --git a/subgraphs/orbit/src/sdk/README.md b/subgraphs/orbit/src/sdk/README.md
index cb7d3f8403..4b8b1b8594 100644
--- a/subgraphs/orbit/src/sdk/README.md
+++ b/subgraphs/orbit/src/sdk/README.md
@@ -1,6 +1,6 @@
 ## Wat dis?
 
-This folder contains a library which abstracts the developer from most of the _schema related_ functionality. Ideally, building a subgraph should only consist on understading a protocol and translating certain events into actions and metrics. But the particularities of how this metrics are stored and how they relate to each other inside the schema can and should be abstracted away. Things like taking snapshots of entities every X amount of time, updating TVL every time there is a deposit/withdrawal, updating fees at _swap & pool & protocol & snapshot levels_, etc ... This library aims to do that.
+This folder contains a library which abstracts the developer from most of the _schema related_ functionality. Ideally, building a subgraph should only consist on understanding a protocol and translating certain events into actions and metrics. But the particularities of how this metrics are stored and how they relate to each other inside the schema can and should be abstracted away. Things like taking snapshots of entities every X amount of time, updating TVL every time there is a deposit/withdrawal, updating fees at _swap & pool & protocol & snapshot levels_, etc ... This library aims to do that.
 
 When using this library, entities should not be updated directly, but always through the library unless absolutely needed. An exception to this is if you create your own auxiliary entity to aid on the handling of some events.