From 28f3edf107d4d87079f40baac4d46a7b66557aee Mon Sep 17 00:00:00 2001 From: Sebastien Kempf <56154464+skmpf@users.noreply.github.com> Date: Sat, 8 Nov 2025 11:34:30 +0900 Subject: [PATCH] docs: typo --- docs/content/state/v3/sync/keel.mdx | 2 +- docs/content/state/v3/sync/supabase.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/state/v3/sync/keel.mdx b/docs/content/state/v3/sync/keel.mdx index 6b27be1..6c25b60 100644 --- a/docs/content/state/v3/sync/keel.mdx +++ b/docs/content/state/v3/sync/keel.mdx @@ -295,7 +295,7 @@ const profiles$ = observable({ ## Sync only diffs -An optional but very useful feature is the `changesSince: 'last-sync'` option. This can massively reduce badwidth usage when you're persisting list results since it only needs to list changes since the last query. The way this works internally is basically: +An optional but very useful feature is the `changesSince: 'last-sync'` option. This can massively reduce bandwidth usage when you're persisting list results since it only needs to list changes since the last query. The way this works internally is basically: 1. Save the maximum updatedAt to the local persistence 2. In subsequent syncs or after refresh it will list by `updatedAt: lastSync + 1` to get only recent changes diff --git a/docs/content/state/v3/sync/supabase.mdx b/docs/content/state/v3/sync/supabase.mdx index fe36dea..47e44a2 100644 --- a/docs/content/state/v3/sync/supabase.mdx +++ b/docs/content/state/v3/sync/supabase.mdx @@ -181,7 +181,7 @@ const messages$ = observable(syncedSupabase({ ## Sync only diffs -An optional but very useful feature is the `changesSince: 'last-sync'` option. This can massively reduce badwidth usage when you're persisting list results since it only needs to list changes since the last query. The way this works internally is basically: +An optional but very useful feature is the `changesSince: 'last-sync'` option. This can massively reduce bandwidth usage when you're persisting list results since it only needs to list changes since the last query. The way this works internally is basically: 1. Save the maximum updatedAt to the local persistence 2. In subsequent syncs or after refresh it will list by `updated_at: lastSync + 1` to get only recent changes