moved timestamp mention from ios group call to timestamp section

Jessica-Kuo · Jessica-Kuo · commit a0e7dca1f20f · 2020-11-03T14:47:38.000-05:00
diff --git a/src/connections/sources/catalog/libraries/mobile/ios/index.md b/src/connections/sources/catalog/libraries/mobile/ios/index.md
@@ -438,7 +438,7 @@ The Group call has the following fields:
   </tr>
   <tr>
     <td>`options` _Options, optional_</td>
-    <td>An `Options` object lets you [enable or disable destinations](#selecting-destinations), or [send additional context](/docs/connections/spec/common/#context). A [timestamp](/docs/connections/spec/common/#timestamps) will be generated but cannot be manually set in order to import historical data to the Seegment API.</td>
+    <td>An `Options` object lets you [enable or disable destinations](#selecting-destinations), or [send additional context](/docs/connections/spec/common/#context).</td>
   </tr>
 </table>
 
diff --git a/src/connections/spec/common.md b/src/connections/spec/common.md
@@ -392,4 +392,4 @@ The `receivedAt` timestamp is most important as the sort key in our Warehouses p
 
 The `timestamp` timestamp specifies when the datapoint occurred, corrected for client-device clock skew. This is the timestamp that is passed to downstream destinations and used for historical replays. It is important to use this timestamp for importing historical data to the API.
 
-The `timestamp` field is settable from our server-side libs or if passing info directly to the HTTP endpoints.
+The `timestamp` field is settable from our server-side libs or if passing info directly to the HTTP endpoints.  From the client-side, a `timestamp` will be generated but cannot be manually set in order to import historical data to the Seegment API.

Original file line number	Diff line number	Diff line change
@@ -392,4 +392,4 @@ The `receivedAt` timestamp is most important as the sort key in our Warehouses p
`392`	`392`
`393`	`393`	The `timestamp` timestamp specifies when the datapoint occurred, corrected for client-device clock skew. This is the timestamp that is passed to downstream destinations and used for historical replays. It is important to use this timestamp for importing historical data to the API.
`394`	`394`
`395`		-The `timestamp` field is settable from our server-side libs or if passing info directly to the HTTP endpoints.
	`395`	+The `timestamp` field is settable from our server-side libs or if passing info directly to the HTTP endpoints. From the client-side, a `timestamp` will be generated but cannot be manually set in order to import historical data to the Seegment API.