diff --git a/data-catalog/stellar/evm_v_stellar.mdx b/data-catalog/stellar/evm_v_stellar.mdx
index db52e65d..da994be9 100644
--- a/data-catalog/stellar/evm_v_stellar.mdx
+++ b/data-catalog/stellar/evm_v_stellar.mdx
@@ -17,7 +17,7 @@ This document provides a generalized overview of the differences between Ethereu
 ### Stellar
 The Stellar Network is designed to create digital asset products and services that improve access to the global financial system. With a focus on **simplicity, speed, and cost-effectiveness** in transferring assets, Stellar connects financial institutions, payment systems, and individuals.
 
-Due to its financial-centric design, Stellar includes built-in primitives for asset management, making it more secure and efficient for financial applications. However, Stellar's original design was less flexible and had limited the types of financial applications buit on Stellar. Since February 2024, Stellar has supported **smart contracts** written in Rust and compiled as WebAssembly (wasm).
+Due to its financial-centric design, Stellar includes built-in primitives for asset management, making it more secure and efficient for financial applications. However, Stellar's original design was less flexible and had limited the types of financial applications built on Stellar. Since February 2024, Stellar has supported **smart contracts** written in Rust and compiled as WebAssembly (wasm).
 
 ### EVM
 EVM blockchains such as Ethereum allow developers to build decentralized applications (dApps) and deploy **smart contracts**. Unlike Stellar, EVM chains emphasize flexible programming at the cost of speed, leading to the need for layer-2 (L2) solutions to improve transaction throughput and cost efficiency. Smart contracts on EVM are written in Solidity.
diff --git a/data-catalog/stellar/history_effects.mdx b/data-catalog/stellar/history_effects.mdx
index f8a86728..38b7835a 100644
--- a/data-catalog/stellar/history_effects.mdx
+++ b/data-catalog/stellar/history_effects.mdx
@@ -5,7 +5,7 @@ description: Description of the history_effects table on Dune
 ---
 
 ## Table description
-Records specific changes that occur in the ledger as a result of success operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are.
+Records specific changes that occur in the ledger as a result of successful operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are.
 
 Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction. Each of Stellar’s operations have a unique operation object.
 
@@ -90,4 +90,4 @@ Operations are objects that represent a desired change to the ledger: payments,
 
 import { TableSample } from "/snippets/table-sample.mdx";
 
-<TableSample tableSchema="stellar" tableName="history_effects" />
\ No newline at end of file
+<TableSample tableSchema="stellar" tableName="history_effects" />
diff --git a/data-catalog/stellar/liquidity_pools.mdx b/data-catalog/stellar/liquidity_pools.mdx
index c7b1307b..e382509f 100644
--- a/data-catalog/stellar/liquidity_pools.mdx
+++ b/data-catalog/stellar/liquidity_pools.mdx
@@ -1,6 +1,6 @@
 ---
 title: stellar.liquidity_pools
-sidebarTitle: "Liquidty Pools"
+sidebarTitle: "Liquidity Pools"
 description: Description of the liquidity_pools table on Dune
 ---