Text updates

Author: patricijabrecko

fern/docs/pages/airdrop/data-extraction.mdx

@@ -282,7 +282,7 @@ This lets you simulate a soft timeout and validate that your worker shuts down.
 
 ## Time-scoped syncs
 
-Time-scoped syncs allow users to specify a custom timestamp to control the scope of data extraction. This capability enables more granular control over which data gets synchronized between external systems and DevRev.
+Time-scoped syncs allow using a custom timestamp to control the scope of data extraction. This capability enables more granular control over which data gets synchronized between external systems and DevRev.
 
 Enable time-scoped syncs by first adding the capability to your manifest:
 
@@ -295,20 +295,18 @@ imports:
 
 Your data extraction implementation must handle two optional parameters from the event's `EventContext`:
 
-- **`extract_from`**: Timestamp indicating extraction starting point (applies to both initial and incremental syncs)
+- **`extract_from`**: Timestamp (in format RFC3339) indicating extraction starting point (applies to both initial and incremental syncs)
 - **`reset_extract_from`**: Boolean flag for incremental syncs that determines whether data should be reextracted
 
-<Info>Both parameters are optional and only provided when users specify time-scoped sync parameters.</Info>
-
 The extraction logic depends on the sync type and parameter combination:
 
 **Initial syncs**: Use `extract_from` as the starting timestamp for data extraction.
 
 **Incremental syncs**: 
 - If `reset_extract_from` is `true`: Start from `extract_from` (if provided) or extract all data
-- If `reset_extract_from` is `false` or not provided: Use `lastSuccessfulSyncStarted` timestamp
+- If `reset_extract_from` is `false` or not provided: Use `adapter.state.lastSuccessfulSyncStarted` timestamp
 
-```typescript focus={1-2,6-8,12-16,20-22}
+```typescript
 const { reset_extract_from, extract_from } = adapter.event.payload.event_context;
 
 // The start of a new sync.

fern/docs/pages/airdrop/getting-started.mdx

@@ -104,6 +104,6 @@ A 2-way sync consists of the following phases:
 
 ### Time-scoped sync
 
-Normally, an initial sync extracts all available data, and an incremental sync only extracts changes since the last successful sync. A _time-scoped sync_, on the other hand, allows for the extraction of data beginning from a user-provided timestamp.
+Normally, an initial sync extracts all data from an organization, and an incremental sync only extracts changes since the last successful sync. A _time-scoped sync_, on the other hand, allows for the extraction of data beginning from a user-provided timestamp.
 
 This approach is useful for initially testing the integration with a smaller data set—such as data from the last month—before conducting a full import of all available data.