From 3b3db33bcbc9d15dd6eb1522beea4074437c0f68 Mon Sep 17 00:00:00 2001
From: Daniel Norman <1992255+2color@users.noreply.github.com>
Date: Mon, 6 Jun 2022 22:09:21 +0200
Subject: [PATCH] Update src/_blog/break-on-through-gateways-part-1.md

Co-authored-by: Mosh <1306020+mishmosh@users.noreply.github.com>
---
 src/_blog/break-on-through-gateways-part-1.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/_blog/break-on-through-gateways-part-1.md b/src/_blog/break-on-through-gateways-part-1.md
index 9857073f..7a83ff9c 100644
--- a/src/_blog/break-on-through-gateways-part-1.md
+++ b/src/_blog/break-on-through-gateways-part-1.md
@@ -112,7 +112,7 @@ It's worth noting that IPFS is a set of open-source protocols, specifications, a
 
 So how do you use IPFS to access files in real-world applications?
 
-There are two prominent ways to fetch files stored in the IPFS network:
+There are two primary ways to fetch files stored in the IPFS network:
 
 - Running an IPFS node by installing one of the IPFS implementations as a daemon (long-running process) on your computer or a server in the cloud. The node becomes a member of the IPFS peer-to-peer network and announces what data it’s holding and responds to requests for data.
 - Using an **IPFS Gateway** which allows fetching CIDs using the HTTP protocol.