From fd9001ae54739d1831528b0c735c26f167b62dbf Mon Sep 17 00:00:00 2001
From: Cal Courtney <calthejuggler@gmail.com>
Date: Mon, 20 Apr 2026 11:13:30 +0100
Subject: [PATCH] fix(ft-1860): replace refreshInterval with refreshPeriod in
 README

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index be4a960..043607c 100644
--- a/README.md
+++ b/README.md
@@ -205,7 +205,7 @@ await context.finalize().then(() => {
 #### Refreshing the context with fresh experiment data
 For long-running single-page-applications (SPA), the context is usually created once when the application is first reached.
 However, any experiments being tracked in your production code, but started after the context was created, will not be triggered.
-To mitigate this, we can use the `refreshInterval` option when creating the context.
+To mitigate this, we can use the `refreshPeriod` option when creating the context.
 
 ```javascript
 const request = {
@@ -215,7 +215,7 @@ const request = {
 };
 
 const context = sdk.createContext(request, {
-    refreshInterval: 5 * 60 * 1000
+    refreshPeriod: 5 * 60 * 1000
 });
 ```
 
@@ -293,7 +293,7 @@ Here is an example of setting a timeout only for the createContext request.
 
 ```javascript
 const context = sdk.createContext(request, {
-    refreshInterval: 5 * 60 * 1000
+    refreshPeriod: 5 * 60 * 1000
 }, {
     timeout: 1500
 });
@@ -307,7 +307,7 @@ Here is an example of a cancellation scenario.
 ```javascript
 const controller = new absmartly.AbortController();
 const context = sdk.createContext(request, {
-    refreshInterval: 5 * 60 * 1000
+    refreshPeriod: 5 * 60 * 1000
 }, {
     signal: controller.signal
 });