Merge pull request #7521 from braze-inc/develop

Leftover deploy - June 13, 2024

_docs/_developer_guide/platform_integration_guides/swift/content_cards/tvos.md

@@ -29,10 +29,10 @@ In your app settings, select your new tvOS app then take note of your app's API
 
 ![ALT_TEXT]({% image_buster /assets/img/tvos1.png %}){: style="width:70%"}
 
-### Step 3: Integrate the Braze Swift SDK
+### Step 3: Integrate BrazeKit
 
-Use your app's API key to integrate the [Braze Swift SDK](https://github.com/braze-inc/braze-swift-sdk) into your tvOS project in Xcode. When you're finished, you can [customize your Content Cards for tvOS](#customizing-your-in-app-messages).
+Use your app's API key to integrate the [Braze Swift SDK](https://github.com/braze-inc/braze-swift-sdk) into your tvOS project in Xcode. You only need to integrate BrazeKit from the Braze Swift SDK.
 
-## Customizing your content cards
+### Step 4: Create your custom UI
 
-Because Braze doesn't provide a default UI for Content Cards on tvOS, you'll need to customize them yourself. For a full walkthrough, see our step-by-step tutorial: [Customizing Content Cards for tvOS](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/content-cards-customization/). For a sample project, see [Braze Swift SDK samples](https://github.com/braze-inc/braze-swift-sdk/tree/main/Examples).
+Because Braze doesn't provide a default UI for content cards on tvOS, you'll need to customize it yourself. For a full walkthrough, see our step-by-step tutorial: [Customizing content cards for tvOS](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/content-cards-customization/). For a sample project, see [Braze Swift SDK samples](https://github.com/braze-inc/braze-swift-sdk/tree/main/Examples#contentcards-custom-ui).

_docs/_developer_guide/platform_integration_guides/swift/in-app_messaging/customization/tvos.md

@@ -29,10 +29,10 @@ In your app settings, select your new tvOS app then take note of your app's API
 
 ![ALT_TEXT]({% image_buster /assets/img/tvos1.png %}){: style="width:70%"}
 
-### Step 3: Integrate the Braze Swift SDK
+### Step 3: Integrate BrazeKit
 
-Use your app's API key to integrate the [Braze Swift SDK](https://github.com/braze-inc/braze-swift-sdk) into your tvOS project in Xcode. When you're finished, you can [customize your in-app messages for tvOS](#customizing-your-in-app-messages).
+Use your app's API key to integrate the [Braze Swift SDK](https://github.com/braze-inc/braze-swift-sdk) into your tvOS project in Xcode. You only need to integrate BrazeKit from the Braze Swift SDK.
 
-## Customizing your in-app messages
+### Step 4: Create your custom UI
 
-Because Braze doesn't provide a default UI for in-app messages on tvOS, you'll need to customize it yourself. For a full walkthrough, see our step-by-step tutorial: [Customizing in-app messages for tvOS](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/in-app-message-customization). For a sample project, see [Braze Swift SDK samples](https://github.com/braze-inc/braze-swift-sdk/tree/main/Examples).
+Because Braze doesn't provide a default UI for in-app messages on tvOS, you'll need to customize it yourself. For a full walkthrough, see our step-by-step tutorial: [Customizing in-app messages for tvOS](https://braze-inc.github.io/braze-swift-sdk/documentation/braze/in-app-message-customization). For a sample project, see [Braze Swift SDK samples](https://github.com/braze-inc/braze-swift-sdk/tree/main/Examples#inappmessages-custom-ui).

_docs/_hidden/private_betas/field_level_encryption.md

@@ -65,7 +65,7 @@ When updating email address in Braze, you should use the hashed email value wher
 - Adding or updating users via CSV
 
 {% alert note %}
-When creating a new user, you must add `encrypted_email` with the user's encrypted email value. Otherwise, the user will not be created.
+When creating a new user, you must add `email_encrypted` with the user's encrypted email value. Otherwise, the user will not be created.
 {% endalert %}
 
 ## Considerations

_docs/_partners/message_personalization/localization/crowdin.md

@@ -31,7 +31,7 @@ The Braze and Crowdin integration allows you to translate email templates and Co
 #### Crowdin
 To set up the Braze app in Crowdin, follow these steps:
 
-1. Go to the [Braze app in the marketplace](https://crowdin.com/resources#marketplace/braze).
+1. Go to the [Braze app in the marketplace](https://store.crowdin.com/braze-app).
 2. Click **Install** to add it to your account.
 3. Open the project you created for your Braze content localization.
 4. Go to **Settings > Integrations** tab.

_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md

@@ -77,7 +77,7 @@ Currents will never write empty files.
 
 ### Avro schema changes
 
-From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `<schema-id>` will be advanced to indicate the schema was updated.
+From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `<schema-id>` will be advanced to indicate the schema was updated. Currents events written to Azure Blob Storage, Google Cloud Storage, and Amazon S3 will write the `<schema-id>` in the path. For example `<your-bucket-name0>/<currents-integration-id>/<event-type>/<date-of-event>/<schema-id>/<environment>/<avro-file>`.
 
 #### Non-breaking changes
 

_docs/_user_guide/data_and_analytics/export_braze_data/message_archiving.md

@@ -20,7 +20,7 @@ When this feature is turned on, if you have connected a cloud storage bucket to
 
 This file will contain the fields defined under [File references](#file-references) and reflect the final templated messages sent to the user. Any templated values defined in your campaign (for example, {% raw %}`{{${first_name}}}`{% endraw %}) will show the final value that the user received based on their profile information. This will allow you to retain a copy of the message sent to satisfy compliance, audit, or customer support requirements.
 
-If you setup credentials for multiple cloud storage providers, Message Archiving will only export to the one explicitly marked as the default data export destination. If no explicit default is provided and an AWS S3 bucket is connected, Message Archiving will upload to that bucket.
+If you set up credentials for multiple cloud storage providers, message archiving will only export to the one explicitly marked as the default data export destination. If no explicit default is provided and an AWS S3 bucket is connected, message archiving will upload to that bucket.
 
 {% alert important %}
 Turning on this feature will impact the delivery speed of your messages, as the file upload is performed immediately before the message send to ensure accuracy. This introduces additional latency into the Braze sending pipeline, affecting sending speeds.

_docs/_user_guide/personalization_and_dynamic_content/promotion_codes.md

@@ -97,9 +97,9 @@ From there, you can paste this code into a message within the dashboard.
 
 Using [Liquid][11], you can insert one of the unique promotion codes from the uploaded CSV file into a message. That code will be marked as sent on the Braze backend to ensure no other message sends that same code. 
 
-When a code snippet is used in a multichannel campaign or Canvas step, each user always receives a unique code. For different steps in a Canvas, each user receives several promotion codes. If a particular user is eligible to receive a code through more than one channel, this user will receive the same code through each channel. 
+When a code snippet is used in a multichannel campaign or Canvas step, each user always receives a unique code. For different steps in a Canvas, each user receives several promotion codes. 
 
-If the user receives two messages through two channels, only one code will be shown and used in both messages. The same applies for reporting purposes: one code will be sent, and the user will receive this code through the two channels. For example, for a multichannel Canvas step, only one code would be used by the user.
+If a particular user is eligible to receive a code through more than one channel, this user will receive the same code through each channel. For example, if a user receives two messages through two channels, they will receive only one code. The same applies for reporting purposes: one code will be sent, and the user will receive this code through the two channels. For example, for a multichannel Canvas step, only one code would be used by the user.
 
 {% alert important %}
 If there are no remaining promotion codes available when sending test or live messages from a campaign that pulls in promo codes, the message will not send.

_docs/_user_guide/sage_ai/recommendations/ai_item_recommendations.md

@@ -100,7 +100,7 @@ There are some requirements for selecting your property:
 - Must map to the `id` field of your selected catalog.
 - **If you selected Purchase Object:** Must be the `product_id` or a field of your interaction event's `properties`.
 - **If you selected Custom Event:** Must be a field of your custom event's `properties`.
-- The field can't be nested.
+- Nested fields must be typed into the **Property Name** dropdown in dot notation with the format of `event_property.nested_property`. For example, if selecting the nested property `district_name` within the event property `location`, you would enter `location.district_name`.
 - The field can be in an array (of multiple catalog items within a single event). It will automatically be flattened.
 
 #### Example mappings