Update Data-Marshaling-and-Transmission.md

docs/product/Data-Marshaling-and-Transmission.md

@@ -1,7 +1,7 @@
 ---
 title: Data Marshaling and Transmission
 sidebar_position: 11
-description: How Embrace sends data off device
+description: How about keeping it simple with something like "How Embrace SDKs Transfer Data from Devices to Our Servers
 ---
 
 # Overview
@@ -13,12 +13,12 @@ Embrace is designed to be a “good citizen” within your mobile application. W
 - **Data is batched and tranmitted to balance reliability with resource usage.**
   - On Android, requests are sent serially, i.e. only one payload is actively being sent at one time.
   - On iOS, payloads are enqueued with a low-priority.
-- **We do not send data if we detect there is no network connection** and use an exponential backoff scheme to handle retries so the queue wouldn't be overwhelmed by requests timing out if the network condition is poor.
+- **We do not send data if we detect there is no network connection** and use an exponential backoff scheme to handle retries so the queue won't be overwhelmed by requests timing out if the network condition is poor.
 - **We do not share any domain or session resources** with your primary application requests, so there is no direct contention with your core APIs.
 
 These design principles ensure that user-facing requests (such as booking flows, checkouts, or other high-priority transactions) will be impacted as little as possible by the overhead of transimitting telemetry.
 
-# FAQ’s
+# FAQs
 
 ---
 
@@ -32,7 +32,7 @@ We employ exponential backoff for retries when a connection fails and do not att
 
 ## **Can we configure the SDK to only send data when on Wi-Fi or in the background?**
 
-Currently, no. We prioritize quick, low-frequency uploads to avoid large backlogs and ensure timely observability. Restricting uploads to Wi-Fi or background-only would risk missing critical data if the app is not backgrounded for a long enough period or closed altogether.
+No. We prioritize quick, low-frequency uploads to avoid large backlogs and ensure timely observability. Restricting uploads to Wi-Fi or background-only would risk missing critical data if the app is not backgrounded for a long enough period or closed altogether.
 
 ## **Is it possible to disable data sending entirely during critical user flows?**