DevCycle SDK quality review

docs/sdk/client-side-sdks/android/android-usage.md

@@ -250,7 +250,7 @@ DevCycleEvent event = DevCycleEvent.builder()
 devcycleClient.track(event);
 ```
 
-The SDK will flush events every 10s or `flushEventsMS` specified in the options.
+The SDK will flush events every 10s or `flushEventsIntervalMs` specified in the options.
 
 **Manually Flushing Events**
 

docs/sdk/client-side-sdks/angular/angular-gettingstarted.md

@@ -26,7 +26,7 @@ const devCycleProvider = new DevCycleAngularProvider(
   { /* DevCycle Options */ }
 );
 
-// A `targetingKey` or `user_id` is required to initialize the DevCycle Provider.
+// Provide a `targetingKey` or `user_id` to avoid an anonymous user.
 OpenFeature.setContext({
   targetingKey: "user123"
 });
@@ -52,9 +52,10 @@ It's best to initialize DevCycle in your root module, so that it can be initiali
 
 :::
 
-### Required TargetingKey
+### TargetingKey or user_id
 
-For DevCycle SDK to work we require either a `targetingKey` or `user_id` to be set on the OpenFeature context. This is used to identify the user as the user_id for a DevCycleUser in DevCycle.
+DevCycle recommends setting a `targetingKey` or `user_id` on the OpenFeature context to identify the user.
+If neither is set, the provider initializes an anonymous user and evaluates flags for that anonymous user.
 
 
 ### Context properties to DevCycleUser

docs/sdk/client-side-sdks/flutter/flutter-usage.md

@@ -145,7 +145,7 @@ DevCycleEvent event = DevCycleEventBuilder()
 _devcycleClient.track(event);
 ```
 
-The SDK will flush events every 10s or `flushEventsMS` specified in the options. To manually flush events, call:
+The SDK will flush events every 10s or `flushEventsIntervalMs` specified in the options. To manually flush events, call:
 
 ```dart
 _devcycleClient.flushEvents();

docs/sdk/client-side-sdks/ios/ios-usage.md

@@ -245,7 +245,7 @@ if (err) {
 
 ### Manually Flush Events
 
-The SDK will flush events every 10s or `flushEventsMS` specified in the options. To manually flush events, call:
+The SDK will flush events every 10s or `eventFlushIntervalMS` specified in the options. To manually flush events, call:
 
 **Swift**
 

docs/sdk/client-side-sdks/javascript/javascript-openfeature.md

@@ -113,10 +113,10 @@ const devcycleProvider = new DevCycleProvider('<DEVCYCLE_CLIENT_SDK_KEY>', optio
 await OpenFeature.setProviderAndWait(devcycleProvider)
 ```
 
-### Required TargetingKey
+### TargetingKey or user_id
 
-For DevCycle SDK to work we require either a `targetingKey` or `user_id` to be set on the OpenFeature context.
-This is used to identify the user as the `user_id` for a `DevCycleUser` in DevCycle.
+DevCycle recommends setting a `targetingKey` or `user_id` on the OpenFeature context to identify the user.
+If neither is set, the provider initializes an anonymous user and evaluates flags for that anonymous user.
 
 ### Context properties to DevCycleUser
 

docs/sdk/client-side-sdks/javascript/javascript-usage.md

@@ -180,7 +180,7 @@ const event = {
 devcycleClient.track(event)
 ```
 
-The SDK will flush events every 10s or `flushEventsMS` specified in the options. To manually flush events, call:
+The SDK will flush events every 10s or `eventFlushIntervalMS` specified in the options. To manually flush events, call:
 
 ```javascript
 await devcycleClient.flushEvents()

docs/sdk/client-side-sdks/react-native/react-native-usage.md

@@ -160,7 +160,7 @@ const event = {
 devcycleClient.track(event)
 ```
 
-The SDK will flush events every 10s or `flushEventsMS` specified in the Provider options. To manually flush events, call:
+The SDK will flush events every 10s or `eventFlushIntervalMS` specified in the Provider options. To manually flush events, call:
 
 ```js
 await devcycleClient.flushEvents()

docs/sdk/client-side-sdks/react/react-openfeature.md

@@ -122,10 +122,10 @@ const devcycleProvider = new DevCycleReactProvider(
 await OpenFeature.setProviderAndWait(devcycleProvider)
 ```
 
-### Required TargetingKey
+### TargetingKey or user_id
 
-For DevCycle SDK to work we require either a `targetingKey` or `user_id` to be set on the OpenFeature context.
-This is used to identify the user as the `user_id` for a `DevCycleUser` in DevCycle.
+DevCycle recommends setting a `targetingKey` or `user_id` on the OpenFeature context to identify the user.
+If neither is set, the provider initializes an anonymous user and evaluates flags for that anonymous user.
 
 ### Context properties to DevCycleUser
 

docs/sdk/client-side-sdks/react/react-usage.md

@@ -171,7 +171,7 @@ const event = {
 devcycleClient.track(event)
 ```
 
-The SDK will flush events every 10s or `flushEventsMS` specified in the Provider options. To manually flush events, call:
+The SDK will flush events every 10s or `eventFlushIntervalMS` specified in the Provider options. To manually flush events, call:
 
 ```js
 await devcycleClient.flushEvents()

docs/sdk/client-side-sdks/roku/roku-install.md

@@ -22,7 +22,7 @@ import PromptContent from '!!raw-loader!@site/static/ai-prompts/roku.md'
 
 This version of the DevCycle Client SDK supports the following platforms:
 
-- **Roku OS 9.4+**
+- **Roku OS 9.1+**
 
 ## Installation
 

docs/sdk/client-side-sdks/roku/roku-usage.md

@@ -100,7 +100,7 @@ event = {
 m.devcycleClient.track(event)
 ```
 
-The SDK will flush events every 10s or `flushEventsMS` specified in the options. To manually flush events, call:
+The SDK will flush events every 10s or `flushEventsIntervalMs` specified in the options. To manually flush events, call:
 
 ```javascript
 m.devcycleClient.flushEvents()