From b92527d1d045189813fe90970c2b4a9c6f1b7102 Mon Sep 17 00:00:00 2001
From: Daniel Norman <1992255+2color@users.noreply.github.com>
Date: Tue, 23 Apr 2024 12:39:23 +0200
Subject: [PATCH] fix: typo (#686)

Co-authored-by: Daniel N <2color@users.noreply.github.com>
---
 src/_blog/verified-fetch.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/_blog/verified-fetch.md b/src/_blog/verified-fetch.md
index f440270b1..97be9bc1a 100644
--- a/src/_blog/verified-fetch.md
+++ b/src/_blog/verified-fetch.md
@@ -45,7 +45,7 @@ For example, fetching an image with the CID: [`bafk...beom`](https://cid.ipfs.te
 
 Content addressing in IPFS frees you from the model of a single canonical source for data. This is a powerful concept and the root of IPFS' benefits: resilience, censorship resistance, and trustlessness. But, **fully reaping the benefits of IPFS requires verification**.
 
-### Verification facilitates resilience multi-source retrieval
+### Verification facilitates resilience and multi-source retrieval
 
 Verifying IPFS content as part of the retrieval process allows you to fetch it from multiple sources –either providers or gateways– without trusting them because verification ensures the integrity of the data.