From 07785d784ee28b198bd19ab45168e5b4190375a5 Mon Sep 17 00:00:00 2001
From: saucepoint <98790946+saucepoint@users.noreply.github.com>
Date: Fri, 11 Oct 2024 12:25:46 -0400
Subject: [PATCH] Update
 docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx

Co-authored-by: Alice <34962750+hensha256@users.noreply.github.com>
---
 docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx b/docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx
index ad180d6ae..4bad9e4f5 100644
--- a/docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx
+++ b/docs/contracts/v4/concepts/08-integrated-routing-uniswap-x.mdx
@@ -6,7 +6,7 @@ The [Uniswap Interface](https://app.uniswap.org) will be ramping up support for
 
 At a high level, hook builders' filler implementations will need to do the following: 
 
-1. (On Mainnet) Subscribe to the UniswapX RFQ system on mainnet and submit fillable bids from orders they receive 
+1. (On Mainnet) Subscribe to the UniswapX RFQ system and submit fillable bids from orders they receive 
 2. Listen to the public feed for orders they won or that are open to be filled publicly
 3. Execute those orders against pools that use their hooks