diff --git a/pages/metadata-api/api-reference/overview.mdx b/pages/metadata-api/api-reference/overview.mdx
index 6d9ba2d..2c0912e 100644
--- a/pages/metadata-api/api-reference/overview.mdx
+++ b/pages/metadata-api/api-reference/overview.mdx
@@ -5,7 +5,7 @@ Learn more about the different endpoints of the Metadata API:
 Enso:
 
 - `GET /v1/tokens`: returns all of the tokens supported by the api
-- `GET /v1/protocols`: return the the protocols available to use in the bundle shortcut and in the API
+- `GET /v1/protocols`: return the protocols available to use in the bundle shortcut and in the API
 - `GET /v1/networks`: return the networks supported by the API
 - `GET /v1/actions`: returns all of the actions supported by the api, used to get the data needed to use the bundle api
 - `GET /v1/standards`: returns all of the protocols supported by the api
diff --git a/pages/router-api/api-reference/quote.mdx b/pages/router-api/api-reference/quote.mdx
index fc789b1..c34646e 100644
--- a/pages/router-api/api-reference/quote.mdx
+++ b/pages/router-api/api-reference/quote.mdx
@@ -26,7 +26,7 @@ It returns an object with the following parameters:
 | `amountOut` | Estimated amount out received                                                                               |
 | `route`     | The route of the transaction                                                                                |
 | `gas`       | An estimation on how much gas will be spent                                                                 |
-| `feeAmount` | An Array containting all the collected fee amounts for each amountIn input <br/>(Only if fee was provided). |
+| `feeAmount` | An Array containing all the collected fee amounts for each amountIn input <br/>(Only if fee was provided). |
 
 ### Examples
 
diff --git a/pages/router-api/api-reference/route.mdx b/pages/router-api/api-reference/route.mdx
index 7a03846..811a402 100644
--- a/pages/router-api/api-reference/route.mdx
+++ b/pages/router-api/api-reference/route.mdx
@@ -42,7 +42,7 @@ The tx objects gives you the transaction to use in ethers. The other fields are
 | `priceImpact` | Price impact in basis points, null if USD price not found                                                                                   |
 | `createdAt`   | Block number the transaction was created on                                                                                                 |
 | `tx`          | The tx object to use in ethers. Contains sub-parameters: <br/> -`data`<br/> -`to` <br/>-`from` <br/>-`value`                                |
-| `feeAmount`   | An Array containting all the collected fee amounts for each amountIn input <br/>(Only if fee was provided).                                 |
+| `feeAmount`   | An Array containing all the collected fee amounts for each amountIn input <br/>(Only if fee was provided).                                 |
 
 ### Examples
 
@@ -51,7 +51,7 @@ The tx objects gives you the transaction to use in ethers. The other fields are
 Spend Ether from the EOA and get stETH in return.
 
 Specify a tokenIn (ETH), tokenOut (stETH) and either a sellAmount to get a route of 1 ETH for WETH.
-The route endpoint will calculate the best route for you, choosing between all the avilable AMM's and protocols (E.g. depositing directly to Lido).
+The route endpoint will calculate the best route for you, choosing between all the available AMM's and protocols (E.g. depositing directly to Lido).
 
 If depositing directly to LIDO is the best route the tx object will contain the data to call the deposit function on the LIDO contract, otherwise it will contain the data to call the best AMM.