Merge branch 'develop' of github.com:segmentio/segment-docs into develop

Author: markzegarelli

src/connections/destinations/catalog/optimizely-full-stack/index.md

@@ -15,10 +15,10 @@ Segment's **Optimizely Full Stack (previously Optimizely X)** destination suppor
 * [Optimizely Full Stack Android (Cloud-mode)](#android-cloud-mode-implementation)
 * [Optimizely Full Stack iOS (Cloud-mode)](#ios-cloud-mode-implementation)
 
-If you're interested in implementing Optimizely X Web or Optimizely Full Stack with the JavaScript SDK, see Segment's [**Optimizely Web** destination](/docs/connections/destinations/catalog/optimizely-web/), which supports:
+If you're interested in implementing Optimizely X Web or Optimizely Full Stack with the JavaScript SDK, see Segment's [**Optimizely Web Destination**](/docs/connections/destinations/catalog/optimizely-web/), or follow the links below:
 
 * [Optimizely X Web](/docs/connections/destinations/catalog/optimizely/#optimizely-x-web)
-* [Optimizely Full Stack (JavaScript)](/docs/connections/destinations/catalog/optimizely/#optimizely-full-stack-javascript-)
+* [Optimizely Full Stack (JavaScript SDK)](/docs/connections/destinations/catalog/optimizely-web/#optimizely-full-stack-javascript-sdk)
 
 ## Implementation Prerequisite
 

src/connections/sources/catalog/libraries/mobile/ios/index.md

@@ -221,6 +221,9 @@ configuration.trackDeepLinks = YES;
 {% endcodeexampletab %}
 {% endcodeexample %}
 
+> note ""
+> **Note:** You still need to call the `continueUserActivity` and `openURL` methods on the analytics client.
+
 ### Flushing
 
 You can set the number of events that should queue before flushing. Setting this to `1` will send events as they come in (i.e. not send batched events) and will use more battery. `20` by default.

src/privacy/user-deletion-and-suppression.md

@@ -42,7 +42,7 @@ When you create a `SUPPRESS_AND_DELETE` regulation, the user is actively suppres
 
 Segment deletes messages with this `userId` from connected raw data Destinations, including Redshift, BigQuery, Postgres, Snowflake, and Amazon S3. Warehouse deletions occur using a DML run against your cluster or instance, and Segment delete from S3 by "recopying" clean versions of any files in your bucket that included data about that `userId`.
 
-Segment forwards these deletion requests to a [growing list of supported partners](https://segment.com/docs/privacy/faq/#which-destinations-can-i-send-deletion-requests-to).
+Segment forwards these deletion requests to a [growing list of supported partners](/docs/privacy/faq/#which-destinations-can-i-send-deletion-requests-to).
 
 Note that Segment has a 30-day SLA for submitted deletion requests. Additionally, Segment's deletion manager can only accommodate 100,000 users within a 30-day period and cannot guarantee a 30-day SLA if there are more than 100,000 deletion requests submitted within those 30 days.