adam/ipfs-blog
1
0 Fork 0
mirror of https://github.com/ipfs/ipfs-blog.git synced 2026-10-31 02:11:57 +01:00
Code Issues 17 Packages Projects Releases Wiki Activity

fix: typo (#686)

Browse Source 
Co-authored-by: Daniel N <2color@users.noreply.github.com>
This commit is contained in:
Daniel NormanandDaniel N authored and GitHub committed 2024-04-23 12:39:23 +02:00
1 parent d7d6da8772
commit b92527d1d0
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
src/_blog/verified-fetch.md
+1 -1
View File
@@ -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.