Merge pull request #4050 from braze-inc/develop

Leftover Deploy Pt. 3  - September 9, 2022

_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/customer_behavior_events.md

@@ -286,33 +286,6 @@ We do track other News Feed events; these are located in [Message Engagement Eve
 ```
 
 {% endapi %}
-{% api %}
-## Uninstall events
-
-{% apitags %}
-Uninstall
-{% endapitags %}
-
-This event occurs when a user uninstalls an app. Use this data to track when users uninstall an app.
-
-{% alert important %}
-Note that this is not fired when the user actually uninstalls the app - that's impossible to track exactly. Braze sends a daily silent push to determine if the app still exists on your user's device, and if we get an error on that silent push, it is assumed the app has been uninstalled.
-{% endalert %}
-
-```json
-// Uninstall Event: users.behaviors.Uninstall
-{
-  "id": (string) unique id of this event,
-  "user_id": (string) Braze user id of the user,
-  "external_user_id": (string) External ID of the user,
-  "time": (int) 10-digit UTC time of the event in seconds since the epoch,
-  "app_id": (string) id for the app on which the user action occurred,
-  "device_id": (string) id of the device on which the session occurred
-}
-```
-
-{% endapi %}
-
 {% api %}
 
 ## Attribution events

_docs/_user_guide/data_and_analytics/braze_currents/event_glossary/message_engagement_events.md

@@ -1296,3 +1296,29 @@ This event occurs when a user is enrolled in a control variant set on a multi-va
 
 {% endapi %}
 
+{% api %}
+## Uninstall events
+
+{% apitags %}
+Uninstall
+{% endapitags %}
+
+This event occurs when a user uninstalls an app. Use this data to track when users uninstall an app. While this is currently a message engagement event, this will be changed to a user behavior event in the future.
+
+{% alert important %}
+This event is not fired when the user actually uninstalls the app, as that's impossible to track exactly. Braze sends a daily silent push to determine if the app still exists on your user's device, and if we get an error on that silent push, it is assumed the app has been uninstalled.
+{% endalert %}
+
+```json
+// Uninstall Event: users.behaviors.Uninstall
+{
+  "id": (string) unique id of this event,
+  "user_id": (string) Braze user id of the user,
+  "external_user_id": (string) External ID of the user,
+  "time": (int) 10-digit UTC time of the event in seconds since the epoch,
+  "app_id": (string) id for the app on which the user action occurred,
+  "device_id": (string) id of the device on which the session occurred
+}
+```
+
+{% endapi %}

_docs/_user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out.md

@@ -6,6 +6,7 @@ page_type: reference
 channel:
   - SMS
 page_order: 1.1
+hidden: true
 ---
 
 # Fuzzy opt-out
@@ -28,9 +29,9 @@ For example, "Stpo" or "Please stopppp" will be deemed fuzzy and a fuzzy opt-out
 
 ## Configure fuzzy opt-out
 
-To configure fuzzy opt-out, navigate to the **Subscription Group Keyword Management** page. 
+To configure fuzzy opt-out, navigate to the subscription group keyword management page. 
 1. Under **Subscription Groups**, open the **SMS** section.
-2. In **SMS Global Keywords**, select the **opt-out** category by selecting the pencil icon.
+2. In **SMS Global Keywords**, find the **opt-out** category and select the pencil icon.
 3. Enable **Fuzzy Opt-Out** by toggling it on.
 4. Modify the fuzzy opt-out response as desired. 
 

_docs/_user_guide/message_building_by_channel/sms/keywords/optin_optout.md

@@ -30,8 +30,10 @@ Only the **exact, single-word message** will be processed (case _insensitive_).
 
 If a recipient uses the keywords `HELP` or `INFO`, a response will be triggered automatically. The SMS template for these automatic response messages will be set during your [onboarding][oblink] and phone number procurement period. Note that you may continue to update these responses after the initial onboarding period.
 
+<!---
 {% alert tip %}
 Interested in expanding your opt-out processing? Try [fuzzy opt-out]({{site.baseurl}}/user_guide/message_building_by_channel/sms/keywords/fuzzy_opt_out/), a feature that attempts to recognize when an inbound message does not match an opt-out keyword, but indicates opt-out intent.
 {% endalert %}
+--->
 
 [oblink]: {{site.baseurl}}/user_guide/message_building_by_channel/sms/sms_subscription_group/#setup-process

_docs/_user_guide/onboarding_with_braze/email_setup/ssl/ssl_clicktracking.md

@@ -47,7 +47,7 @@ Braze will be unable to help you troubleshoot your CDN configuration. You must r
 
 | Sendgrid Step-By-Step Guides | Sparkpost Step-By-Step Guides |
 | -------- | --------- |
-| [AWS Cloudfront](https://sendgrid.com/docs/ui/sending-email/universal-links/#setting-up-universal-links-using-cloudfront)<br>[CloudFlare](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-cloudflare)<br>[Fastly](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-fastly)<br>[KeyCDN](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-keycdn) | [AWS Cloudfront](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#aws-create)<br>[CloudFlare](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-cloudflare)<br>[Cloudfront](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/)<br>[Fastly](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-fastly)<br>[Google Cloud Platform](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#gcp-create)<br>[Microsoft Azure](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#azure-create) |
+| [AWS Cloudfront](https://support.sendgrid.com/hc/en-us/articles/4412701748891-How-to-configure-SSL-for-click-tracking-using-CloudFront)<br>[CloudFlare](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-cloudflare)<br>[Fastly](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-fastly)<br>[KeyCDN](https://sendgrid.com/docs/ui/sending-email/content-delivery-networks/#using-keycdn) | [AWS Cloudfront](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#aws-create)<br>[CloudFlare](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-cloudflare)<br>[Cloudfront](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/)<br>[Fastly](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#step-by-step-guide-with-fastly)<br>[Google Cloud Platform](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#gcp-create)<br>[Microsoft Azure](https://www.sparkpost.com/docs/tech-resources/enabling-https-engagement-tracking-on-sparkpost/#azure-create) |
 
 ### CDN troubleshooting