diff --git a/content/introduction/how-ipfs-works.md b/content/introduction/how-ipfs-works.md index 5e297c1..43f6b54 100644 --- a/content/introduction/how-ipfs-works.md +++ b/content/introduction/how-ipfs-works.md @@ -19,7 +19,7 @@ It’s the same on the internet and on your computer. Right now, content is foun - `/Users/Alice/Documents/term_paper.doc` - `C:\Users\Joe\My Documents\project_sprint_presentation.ppt` -By contast, every piece of content that uses the IPFS protocol has a [*content identifier*]({{}}), or CID, that is its *hash*. The hash is unique to the content that it came from, even though it may look short compared to the original content. _If hashes are new to you, check out [the concept guide on hashes]({{}}) for an introduction._ +By contrast, every piece of content that uses the IPFS protocol has a [*content identifier*]({{}}), or CID, that is its *hash*. The hash is unique to the content that it came from, even though it may look short compared to the original content. _If hashes are new to you, check out [the concept guide on hashes]({{}}) for an introduction._ Content addressing through hashes has become a widely-used means of connecting data in distributed systems, from the commits that back your code to the blockchains that run cryptocurrencies. However, the underlying data structures in these systems are not necessarily interoperable.