Add Snowflake callout to Journeys steps page [netlify-build]

Author: pwseg

src/connections/storage/catalog/snowflake/index.md

@@ -264,7 +264,6 @@ For Engage writebacks, Segment starts a warehouse sync after each run completes
 
 Engage writebacks use Track events. The full event payload is stored in a single stringified JSON column in the target table. 
 
-
 ## Security
 
 ### Allowlisting IPs

src/engage/audiences/linked-audiences.md

@@ -17,7 +17,6 @@ With Linked Audiences, you can:
 
 To learn more about specific use cases you can set up with Linked Audiences, see [Linked Audiences Use Cases](/docs/engage/audiences/linked-audiences-use-cases/).
 
-
 See how you can [use Linked Audiences with Braze](/docs/engage/audiences/linked-audiences-braze/) and [Iterable](/docs/engage/audiences/linked-audiences-iterable/) to better understand how you can utilize Linked Audiences for your destinations.  
 
 ## Prerequisites
@@ -206,7 +205,6 @@ Click **Copy to use in Braze Cloud Mode (Actions)** to copy the personalization
 > info ""
 > This feature is in beta for customers using Braze. Some functionality may change before it becomes generally available. This feature is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank"}.
 
-
 #### Show/hide preview 
 
 As you're enriching your events in Linked Audiences, you should view a preview of the event payload schema based on the properties you select. It might look like the following:

src/engage/journeys/v2/event-triggered-journeys-steps.md

@@ -241,6 +241,9 @@ The **Send to Destination** step lets you send journey data to one of your [conf
 
 This step supports Actions Destinations (excluding list destinations) and destination functions. It doesn't support storage destinations or classic (non-Actions) destinations.
 
+> info "Send journey step events to Snowflake"
+> If your team analyzes journey performance in the warehouse, you can write step events from a journey to Snowflake. Connect Snowflake to your Engage space, then add a Snowflake Activation for the journey and choose the schema/table you want to write to. See the [Snowflake destination documentation](/docs/connections/storage/catalog/snowflake/) for connection steps and key-pair setup.
+
 ### How Send to Destination works
 
 When a journey reaches the Send to Destination step, the journey packages the relevant data and sends it to your chosen destination. This could be a third-party platform, like a marketing tool, or a custom destination built using [Destination Functions](/docs/connections/functions/destination-functions/). The data that Segment sends includes key attributes from the journey context, profile traits, and any mapped fields you’ve configured.
@@ -266,6 +269,8 @@ Here’s how to configure this step within a journey:
 
 Before activating the journey, **send a test event to verify that the payload matches your expectations** and that it reaches the destination successfully.
 
+For Snowflake writebacks (beta), Journeys sends Track events and stores the full event payload in a single stringified JSON column in the target table.
+
 ### Destination event payload schema
 
 The events that Segment sends to destinations from Event-Triggered Journeys include an object called `journey_context` within the event’s properties. The `journey_context` object contains: