From bfca25f0f33a6fe1530721ee8e0930fdcddd7cad Mon Sep 17 00:00:00 2001
From: leopardracer <136604165+leopardracer@users.noreply.github.com>
Date: Mon, 9 Dec 2024 22:55:09 +0200
Subject: [PATCH] fix: typos in documentation files (#829)

---
 .../v2/concepts/01-protocol-overview/03-smart-contracts.md      | 2 +-
 .../02-trading-from-a-smart-contract.md                         | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/contracts/v2/concepts/01-protocol-overview/03-smart-contracts.md b/docs/contracts/v2/concepts/01-protocol-overview/03-smart-contracts.md
index de4a255ad6..a7ae456da7 100644
--- a/docs/contracts/v2/concepts/01-protocol-overview/03-smart-contracts.md
+++ b/docs/contracts/v2/concepts/01-protocol-overview/03-smart-contracts.md
@@ -53,7 +53,7 @@ Typically, smart contracts which need tokens to perform some functionality requi
 
 ## WETH
 
-Unlike Uniswap V1 pools, V2 pairs do not support ETH directly, so ETH⇄ERC-20 pairs must be emulated with WETH. The motivation behind this choice was to remove ETH-specific code in the core, resulting in a leaner codebase. End users can be kept fully ignorant of this implementation detail, however, by simply wrapping/unwrapping ETH in the periphery.
+Unlike Uniswap V1 pools, V2 pairs do not support ETH directly, so ETH⇄ERC-20 pairs must be emulated with WETH. The motivation behind this choice was to remove ETH-specific code in the core, resulting in a cleaner codebase. End users can be kept fully ignorant of this implementation detail, however, by simply wrapping/unwrapping ETH in the periphery.
 
 The router fully supports interacting with any WETH pair via ETH.
 
diff --git a/docs/contracts/v2/guides/smart-contract-integration/02-trading-from-a-smart-contract.md b/docs/contracts/v2/guides/smart-contract-integration/02-trading-from-a-smart-contract.md
index 6170aa4c23..5fa27f4fb8 100644
--- a/docs/contracts/v2/guides/smart-contract-integration/02-trading-from-a-smart-contract.md
+++ b/docs/contracts/v2/guides/smart-contract-integration/02-trading-from-a-smart-contract.md
@@ -56,4 +56,4 @@ Because Ethereum transactions occur in an adversarial environment, smart contrac
 
 The best way to protect against these attacks is to use an external price feed or "price oracle". The best "oracle" is simply _traders' off-chain observation of the current price_, which can be passed into the trade as a safety check. This strategy is best for situations _where users initiate trades on their own behalf_.
 
-However, when an off-chain price can't be used, an on-chain oracle should be used instead. Determining the best oracle for a given situation is a not part of this guide, but for more details on the Uniswap V2 approach to oracles, see [Oracles](../../concepts/core-concepts/oracles).
+However, when an off-chain price can't be used, an on-chain oracle should be used instead. Determining the best oracle for a given situation is not a part of this guide, but for more details on the Uniswap V2 approach to oracles, see [Oracles](../../concepts/core-concepts/oracles).