From 73255b6149a6f32faa6780c7bb48f657f590e295 Mon Sep 17 00:00:00 2001 From: Firtina Ozbalikchi <108406948+firtoz@users.noreply.github.com> Date: Thu, 7 Nov 2024 07:45:55 +0000 Subject: [PATCH] Update cloudflare.md - typo fix (#1952) --- website/docs/integrations/cloudflare.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/integrations/cloudflare.md b/website/docs/integrations/cloudflare.md index 1c2ecc5b74..e410aa8464 100644 --- a/website/docs/integrations/cloudflare.md +++ b/website/docs/integrations/cloudflare.md @@ -101,7 +101,7 @@ export default { You can implement a similar pattern to the [sync example above](#syncing-data-into-the-worker) to sync data into a Durable Object. -The key difference is that with a [Durable Object](https://developers.cloudflare.com/durable-objects/), the data can be persisted across requests. This allows you to sync a shape log into the Durable Object, materialise the shape into persistent storage and then re-sync the latest changes whenver the Durable Object is accessed. +The key difference is that with a [Durable Object](https://developers.cloudflare.com/durable-objects/), the data can be persisted across requests. This allows you to sync a shape log into the Durable Object, materialise the shape into persistent storage and then re-sync the latest changes whenever the Durable Object is accessed. You can see a demo of this pattern, using SQLite to persist the Shape data, at [KyleAMathews/electric-demo-cloudflare-sqlite](https://github.com/KyleAMathews/electric-demo-cloudflare-sqlite): @@ -116,4 +116,4 @@ You can see a demo of this pattern, using SQLite to persist the Shape data, at [ example apps using Cloudflare and/or wrap up the code samples above into a library. - \ No newline at end of file +