diff --git a/docs/Introduction.md b/docs/Introduction.md
index 1d5830e9..d5b82f03 100644
--- a/docs/Introduction.md
+++ b/docs/Introduction.md
@@ -42,5 +42,5 @@ RedStone was designed with a modular architecture making it easy to incorporate
 - RedStone supports leading projects like [Morpho](https://morpho.org/), [Venus](https://venus.io/), and [Pendle Finance](https://www.pendle.finance/).
 
 <a target="_blank" href="https://raw.githubusercontent.com/redstone-finance/redstone-docs/main/static/img/redstone-architecture-simple.png">
-  <img alt="RedStone Architecure" src="/img/redstone-architecture-simple.png"/>
+  <img alt="RedStone Architecture" src="/img/redstone-architecture-simple.png"/>
 </a>
diff --git a/docs/data-providers/deploy.md b/docs/data-providers/deploy.md
index 24a5d452..53173ad5 100644
--- a/docs/data-providers/deploy.md
+++ b/docs/data-providers/deploy.md
@@ -8,7 +8,7 @@ sidebar_label: "Deploy"
 In this section you will see how to run a RedStone node using Docker Compose.
 
 :::caution
-For production deployments consider using more sofisticated tools, e.g. Kubernetes.
+For production deployments consider using more sophisticated tools, e.g. Kubernetes.
 :::
 
 ### Requirements
diff --git a/docs/get-started/models/redstone-push.md b/docs/get-started/models/redstone-push.md
index 8bcdf1df..cb5ac4e9 100644
--- a/docs/get-started/models/redstone-push.md
+++ b/docs/get-started/models/redstone-push.md
@@ -23,7 +23,7 @@ This approach is built on top of the [RedStone Pull](./redstone-pull.mdx) model
 
 The model consists of two main parts. The first one is the off-chain [relayer](#relayer) responsible for pushing data on-chain in a customized way using [environment variables](#environment-variables). The second part is the on-chain [contracts](#contracts) which enable storing prices and getting them through a familiar interface (e.g. the [Chainlink Aggregator](https://github.com/smartcontractkit/chainlink/blob/develop/contracts/src/v0.7/interfaces/AggregatorV3Interface.sol) ). RedStone Push can be used on all EVM-compatible L1s & L2s + Starknet + Fuel Network.
 
-<!-- TODO: maybe we shold update the text in the diagram (it has old "Classic" word)  -->
+<!-- TODO: maybe we should, hold, sold update the text in the diagram (it has old "Classic" word)  -->
 
 ![RedStone push diagram](/img/redstone-push.png)
 
diff --git a/docs/get-started/models/redstone-x.md b/docs/get-started/models/redstone-x.md
index eb24abec..b5269bed 100644
--- a/docs/get-started/models/redstone-x.md
+++ b/docs/get-started/models/redstone-x.md
@@ -31,7 +31,7 @@ TLDR; You need to do 2 things:
 
 When a user wants to execute a price-sensitive transaction we need to collect some collateral, record request parameters, and ask keepers to provide price data.
 
-To clarify the steps, let's look at them in the context of a more concrete example. There is a simple protocol that allows swaping a native currency (like ETH) to a stable coin (like USDC). The sample code to record the transaction may look as follows:
+To clarify the steps, let's look at them in the context of a more concrete example. There is a simple protocol that allows swapping a native currency (like ETH) to a stable coin (like USDC). The sample code to record the transaction may look as follows:
 
 ```sol
 function changeEthToUsdc() external payable {
@@ -58,7 +58,7 @@ In the function above we:
 
    We do not need to store all the data on-chain. It's sufficient to record a hash of the values mentioned above.
 
-3. Notify the keepers' network about the new request to receive price data by emiting the `NewOracleDataRequest` event.
+3. Notify the keepers' network about the new request to receive price data by emitting the `NewOracleDataRequest` event.
 
 ### Phase 2 - execution
 
diff --git a/docs/get-started/price-feeds/types-of-feeds/types-of-feeds.md b/docs/get-started/price-feeds/types-of-feeds/types-of-feeds.md
index 870f0cda..1ede7a12 100644
--- a/docs/get-started/price-feeds/types-of-feeds/types-of-feeds.md
+++ b/docs/get-started/price-feeds/types-of-feeds/types-of-feeds.md
@@ -16,7 +16,7 @@ Oracles deliver data feeds directly to dApps or blockchains for the correct exec
 
 4. **Proof of Reserve Feed**
 
-   Also known as Net Asset Value (NAV) feed. A data feed based on API or another source that informs about the value of assets backing tokens issued against it, i.e., Blackrock BUIDL. Technically a subsection of Real World Feed.
+   Also known as Net Asset Value (NAV) feed. A data feed based on API or another source that informs about the value of assets backing tokens issued against it, i.e., Blackrock BUILD. Technically a subsection of Real World Feed.
 
 5. **Protocol Native Oracle**