From 33c7cfae7f941dae4fc0e2dc2b3839a0ed2dd88a Mon Sep 17 00:00:00 2001 From: Sreecharan Date: Thu, 28 Apr 2022 10:29:57 +0530 Subject: [PATCH] fix: spellings --- docs/architecture/distributed-data-sync.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/architecture/distributed-data-sync.md b/docs/architecture/distributed-data-sync.md index f70bca179..09ae6b9ff 100644 --- a/docs/architecture/distributed-data-sync.md +++ b/docs/architecture/distributed-data-sync.md @@ -167,7 +167,7 @@ For the sake of compatibility with local relations, some resource properties can In some cases we are able to create many shared data resources at once and resolve conflicts on the fly by merging where the oldest resource takes priority. -This is intended for the `files` resource. It requires Shared data behaviour as most other shared resources are related at a database level and user defined metadata can be assigned, however it is initially derived from `file_paths` which is Owned data. +This is intended for the `files` resource. It requires Shared data behavior as most other shared resources are related at a database level and user defined metadata can be assigned, however it is initially derived from `file_paths` which is Owned data. As `files` are created in abundance (hundreds of thousands at a time), it would be inefficient to record these changes in the `pending_operations` table. But we are also unable to sync in the same way as Owned data due to the possibility of conflicts. @@ -226,7 +226,7 @@ Then inside the `sync` function we send the event to the } ``` -Files also impempent `OperationalMerge` would use +Files also implement `OperationalMerge` would use # Resources