fix: name Graphsync consisently

ipfs · Sep 25, 2024 · f585210 · f585210
1 parent ce76561
commit f585210
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/src/ipips/ipip-0484.md b/src/ipips/ipip-0484.md
@@ -30,15 +30,15 @@ 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
 
 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