The Intercom source syncs all historic data (#4903)

* Update index.md

* Update index.md

Author: sneha-shashidhar

src/connections/sources/catalog/cloud-apps/intercom/index.md

@@ -35,7 +35,7 @@ Segment begins to sync your Intercom data into Segment, and writes it to your wa
 
 ### Sync
 
-The Intercom source has a sync component, which means Segment make requests to [their API](https://developers.intercom.io/docs/) on your behalf on a 3 hour interval to pull the latest data into Segment. In the initial sync, Segment grabs all the Intercom objects (and their corresponding properties) according to the collections table below. The objects will be written into a designated schema corresponding to the source instance's schema name you designated upon creation. For example, if you went with `intercom_prod`, the `users` collection will be accessible at `intercom_prod.users` in SQL.
+The Intercom source has a sync component, which means Segment make requests to [their API](https://developers.intercom.io/docs/) on your behalf on a 3 hour interval to pull all historical data into Segment. In the initial sync, Segment grabs all the Intercom objects (and their corresponding properties) according to the collections table below. The objects will be written into a designated schema corresponding to the source instance's schema name you designated upon creation. For example, if you went with `intercom_prod`, the `users` collection will be accessible at `intercom_prod.users` in SQL.
 
 The sync component uses an upsert API, so the data in your warehouse loaded using sync will reflect the latest state of the corresponding resource in Intercom.  For example, if the `users.last_seen_ip` will be the latest value upon each sync.