From fed08e96cd84d4037d993b69e7facda4688f75c4 Mon Sep 17 00:00:00 2001 From: Ikko Eltociear Ashimine Date: Sun, 4 Aug 2024 00:08:47 +0900 Subject: [PATCH] book: update event_graph.md recieved -> received --- doc/src/misc/event_graph/event_graph.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/misc/event_graph/event_graph.md b/doc/src/misc/event_graph/event_graph.md index 9830f70ab..d9a86a937 100644 --- a/doc/src/misc/event_graph/event_graph.md +++ b/doc/src/misc/event_graph/event_graph.md @@ -29,7 +29,7 @@ We always save the tree database so once we restart before next rotation we reload the tree and continue from where we left off (previous steps 1 through 4). -We stay in sync while connected by properly handling a new recieved +We stay in sync while connected by properly handling a new received event, we insert it into our dag and mark it as seen, this new event will be a new unreferenced event to be referenced by a newer event if we for some reason didn't receive the event, we will be requesting @@ -71,7 +71,7 @@ event. 2. Check if we already have the event. also check if we have all of its parents. 3. request missing parents if any and add them to the DAG. - 4. if all the checks pass we add the actual recieved event to the DAG. + 4. if all the checks pass we add the actual received event to the DAG. 5. Relay the event to other peers. ## Genesis Event