From f5852101f510cc6f8a2d8d94378651e27de53c6e Mon Sep 17 00:00:00 2001
From: Daniel N <2color@users.noreply.github.com>
Date: Wed, 25 Sep 2024 13:08:03 +0200
Subject: [PATCH] fix: name Graphsync consisently

---
 src/ipips/ipip-0484.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/ipips/ipip-0484.md b/src/ipips/ipip-0484.md
index 54db81f9..87d737c2 100644
--- a/src/ipips/ipip-0484.md
+++ b/src/ipips/ipip-0484.md
@@ -30,7 +30,7 @@ For instance, web browsers are limited to a specific set of network transport pr
 
 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.
+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.
 
 ## Note on terminology
 
@@ -38,7 +38,7 @@ The term **"transport"** is overloaded in the IPFS ecosystem.
 
 In the context of this IPIP, we refer to the network layer transport protocol, e.g. TCP, QUIC, WebTransport, as **"network transport protocol"** to avoid ambiguity.
 
-**"Transfer protocol"** refers to data transfer protocols, i.e. content-addressed block retrieval protocols, e.g. Bitswap, GraphSync, HTTP.
+**"Transfer protocol"** refers to data transfer protocols, i.e. content-addressed block retrieval protocols, e.g. Bitswap, Graphsync, HTTP.
 
 ## Detailed design