From 7c3ca362af59319375f95be22c6a74d432153e2c Mon Sep 17 00:00:00 2001 From: achilles schmelzer <100799178+killthebuddh4@users.noreply.github.com> Date: Sun, 11 Dec 2022 09:43:12 -0800 Subject: [PATCH] Fix typo in data-availability.md --- docs/learn/advanced/data-availability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/learn/advanced/data-availability.md b/docs/learn/advanced/data-availability.md index 83a5bb91b..9b9da976b 100644 --- a/docs/learn/advanced/data-availability.md +++ b/docs/learn/advanced/data-availability.md @@ -20,7 +20,7 @@ If the node happens to shut down or restart, the cache will be cleared. Without Pinning provides a more long-lived mechanism of data persistence for commits. Pinning is a process for instructing a Ceramic node to explicitly host (i.e. "pin") the commits for a specific stream. Since commits are stored in IPLD, Ceramic nodes already contain a bundled [IPFS](../glossary.md#ipfs) node which is where this pinning occurs. IPFS nodes can pin all commits for any stream which is accessible over the Ceramic network to which it is connected. Ceramic pinning can also work using an external IPFS node instead of the bundled internal version. -If developers want the easiest way to make their streams persistent beyond a single session and more resilient against data loss, then pinning is the right option. Ceramic nodes can pin an unlimited number of streams. However, note that if only one IPFS node is pinning a given stream and it disappears forever or gets corrupted, then that stream will be lost. Also, if only one node is pinning a stream (and no other Ceramic nodes have it in cache) and that node goes offline, then that stream will be unavailable to others. Therefore, for improved resilience and data availability it is best to have multiple IPFS nodes running in different envitonments pinning the same streams. +If developers want the easiest way to make their streams persistent beyond a single session and more resilient against data loss, then pinning is the right option. Ceramic nodes can pin an unlimited number of streams. However, note that if only one IPFS node is pinning a given stream and it disappears forever or gets corrupted, then that stream will be lost. Also, if only one node is pinning a stream (and no other Ceramic nodes have it in cache) and that node goes offline, then that stream will be unavailable to others. Therefore, for improved resilience and data availability it is best to have multiple IPFS nodes running in different environments pinning the same streams. > See the [Pinning](../../build/javascript/pinning.md) guide for instructions on how to pin streams on a Ceramic node.