diff --git a/client/introduction.mdx b/client/introduction.mdx
index 9c08bfaf0..8e894ae62 100644
--- a/client/introduction.mdx
+++ b/client/introduction.mdx
@@ -79,7 +79,7 @@ If you have critical fields which define a user uniquely and are not in the `use
 
 -	The client SDK's `logEvent` call takes a custom event that you want to record to analyze the impact of the experiment on your end-user experience
 
-- The client SDK automatically flushes all accumulated logged custom events to the Statsig servers every 10 seconds
+- The client SDK automatically flushes all accumulated logged custom events to the Statsig servers every 60 seconds. [More Details] (https://docs.statsig.com/messages/clientEventLogger)
 
 -	Statsig uses these custom events to compute metrics as part of your experiment **Results**; Statsig automatically updates the **Metrics Lift** panel in the experiment **Results** tab daily around 9am PST
 
diff --git a/sdks/client-vs-server.mdx b/sdks/client-vs-server.mdx
index 8a3e21c70..e009421f8 100644
--- a/sdks/client-vs-server.mdx
+++ b/sdks/client-vs-server.mdx
@@ -42,7 +42,7 @@ After initialization, both Client and Server SDKs evaluate experiments/gates *wi
 |Checking an Experiment| Requires a user object which is evaluated locally (without a network request) against a ruleset persisted in memory | Does not require a user object, uses a dictionary lookup for values fetched during initialize() |
 |User Identifiers| Pass any and all useful user identifiers | Pass any useful identifiers, the SDK also generates a "StableID", Statsig's anonymous ID you can use to experiment on a user per-device|
 |Logging Events| Requires a user object | Does not require a user object. Note, there is some risk of adblocking log events on client SDKs, which can be minimized by setting up a [Custom Proxy](../custom_proxy)|
-|Flushing Events| Batched and flushed by the SDK every 60 seconds | Batched and flushed by the SDK every 10 seconds|
+|Flushing Events| Batched and flushed by the SDK every 60 seconds | Batched and flushed by the SDK every 60 seconds [More Details] (https://docs.statsig.com/messages/clientEventLogger)|
 |Updating Configurations| Poll Statsig servers for updates every 10 seconds by default (configurable), Streaming possible with some Server SDKs and the [Statsig Forward Proxy](/server/concepts/forward_proxy) | Configuration persists until next `initialize` or `updateUser` call, recommended to call `initialize` at the start of each user session|
 
 ## Difference in initialize/update logic: