From 10d07670b7900c972efaf66d64e1980069dd2399 Mon Sep 17 00:00:00 2001 From: SionoiS Date: Fri, 6 Sep 2024 11:15:18 -0400 Subject: [PATCH] typos --- standards/core/store-sync.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/standards/core/store-sync.md b/standards/core/store-sync.md index 6468890..3a1b1ac 100644 --- a/standards/core/store-sync.md +++ b/standards/core/store-sync.md @@ -1,13 +1,13 @@ --- title: WAKU-STORE-SYNC -name: Waku Store Syncronization +name: Waku Store Synchronization editor: Simon-Pierre Vivier contributors: --- ## Abstract -This document describe the strategy Waku store node will employ to stay synchronized. +This document describe the strategy Waku Store node will employ to stay synchronized. The goal being that all store nodes eventually archive the same set of messages. ## Background / Rationale / Motivation @@ -27,7 +27,7 @@ Various protocols and features that help with message consistency are described ### Store Resume -This feature allow a node to fill the gap in messages for the period it was offline. +This feature allow a node to fill the gap in messages for the period it was last offline. At startup, a node use the Store protocol to query a random node for the time interval since it was last online. It is RECOMMENDED” to limit the time interval to a maximum of 6 hours. @@ -35,7 +35,7 @@ It is RECOMMENDED” to limit the time interval to a maximum of 6 hours. ### Waku Sync Nodes that stay online can still miss messages. -Waku Sync is used to find those messages by periodically syncing with random node. +Waku Sync is used to find those messages by periodically syncing with random nodes. It is RECOMMENDED to trigger a sync every 5 minutes for the time range of the last hour. After both hash set are reconciled, the Store protocol is used to reciprocally query the other node with the hash differences found.