From ce765612c4e7c67e6cbcb459738619f1a4f2c5e3 Mon Sep 17 00:00:00 2001
From: Daniel Norman <1992255+2color@users.noreply.github.com>
Date: Wed, 25 Sep 2024 13:07:18 +0200
Subject: [PATCH] Update src/ipips/ipip-0484.md

---
 src/ipips/ipip-0484.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ipips/ipip-0484.md b/src/ipips/ipip-0484.md
index a424a6e7..54db81f9 100644
--- a/src/ipips/ipip-0484.md
+++ b/src/ipips/ipip-0484.md
@@ -28,7 +28,7 @@ However, there are many cases where most of the results from the Delegated Routi
 
 For instance, web browsers are limited to a specific set of network transport protocols, namely HTTPS, Secure WebSockets, WebTransport (emerging), and WebRTC. Consequently, providing information about providers that exclusively support TCP and/or UDP is not beneficial for browser-based clients, as they are unable to utilize such connections.
 
-Moreover, [Helia](https://github.com/ipfs/helia/), the most actively maintained browser IPFS implementation, supports block retrieval by CID with Bitswap and Trustless Gateways, but does not support GraphSync.
+Moreover, [Helia](https://github.com/ipfs/helia/), the most actively maintained browser IPFS implementation, supports block retrieval by CID with Bitswap and Trustless Gateways, but does not support Graphsync.
 
 This means that returning providers that only support raw TCP, raw UDP/QUIC, or GraphSync from the Delegated Routing API is not useful for browser clients, and results in unnecessary network traffic for browser clients.