Merge branch 'main' into docs/console-agent

Author: jborlase-snowplow

docs/destinations/forwarding-events/creating-forwarders/index.md

@@ -12,7 +12,7 @@ Follow the steps below to configure a new event forwarder. See [available integr
 
 A **connection** is a resource that stores the credentials and endpoint details needed to send events to your destination.
 
-To create a connection from [Snowplow Console](https://console.snowplowanalytics.com), first go to **Destinations** > **Connections**, then select **Set up connection**. From the dropdown, choose **Loader connection**, then select the destination you want to forward events to. Each destination will have specific authentication and endpoint details required.
+To create a connection from [Snowplow Console](https://console.snowplowanalytics.com), first go to **Settings** > **Connections**, then select **Set up connection**. From the dropdown, choose **Event forwarding**, then select the destination you want to forward events to. Each destination will have specific authentication and endpoint details required.
 
 ![Console interface for creating a new destination connection with authentication and endpoint configuration fields](images/event-forwarding-connection.png)
 
@@ -21,8 +21,8 @@ When finished, click **Deploy**. Once a connection is deployed, you can use it i
 
 ## Step 2: Create a new forwarder
 
-1. Go to **Destinations** > **Destination list**.
-2. Navigate to the **Available** tab and select **Configure** on the destination card from the list of available integrations to start setting up the forwarder.
+1. Go to **Destinations** > **Event forwarding**.
+2. Click **Add destination** and select the destination from the list of available integrations to start setting up the forwarder.
 3. Give the forwarder a **name**, select the **pipeline** you want the forwarder to read events from, and choose the **connection** you created in step 1.
 4. Optionally, you can choose to **Import configuration from** an existing forwarder. This is helpful when migrating a forwarder setup from development to production.
 5. Click **Continue** to configure event filters and data mapping.
@@ -70,7 +70,7 @@ Once you've defined your filter and mapping configuration, you can test it again
 
 ![Test transformation interface showing sample event input and JSON output preview with run test button](images/event-forwarding-test-transformations.png)
 
-Snowplow provides a few out-of-the-box sample events to test with, which you can edit as needed. You can also choose **Custom event** to paste in your own JSON-formatted Snowplow event. You can use [Snowplow Micro](/docs/testing/snowplow-micro/) with the `--output-json` flag to generate your own events to test with.
+Snowplow provides a few out-of-the-box sample events to test with, which you can edit as needed. You can also choose **Custom event** to paste in your own JSON-formatted Snowplow event. You can use [Snowplow Micro](/docs/testing/snowplow-micro/index.md) to collect some test events and copy their JSON payload for testing.
 
 Select **View generated code** to see the JavaScript function generated from your filters, field mappings, and custom functions. This is exactly what will run when transforming events for your destination, and can be used directly in a [Snowbridge JavaScript transformation](docs/api-reference/snowbridge/configuration/transformations/custom-scripts/javascript-configuration/index.md) for local testing.
 

docs/destinations/forwarding-events/event-forwarding-monitoring-and-troubleshooting/index.md

@@ -44,8 +44,8 @@ When any type of failure occurs, Snowplow can take one or more of the following
 
 Once a forwarder is deployed, you can configure one or more email addresses to send alerts when setup failures occur. Follow the steps below to configure the alerts.
 
-1. Navigate to **Destinations** > **Destinations list** from the navigation bar and click the **Details** button on a destination card to open the **Destination details** page.
-2. On the table of forwarders, click the three dots next to the forwarder you want to configure alerting for and select **Alerts**.
+1. Navigate to **Destinations** > **Event forwarding** from the sidebar.
+2. In the table of forwarders, click the three dots next to the forwarder you want to configure alerting for and select **Alerts**.
 3. You'll see a modal where you can enter the email addresses you want to be alerted in case of setup errors. Click **Save Changes** to confirm.
 
 ![Setup alerts modal dialog for configuring email addresses to receive forwarder error notifications](images/setup-alerting-screenshot.png)
@@ -62,7 +62,7 @@ You can monitor forwarders in a few ways:
 
 In Snowplow Console, you can see the number of filtered, failed, and successfully delivered events over the last seven days.
 
-To view these metrics, navigate to **Destinations** > **Destinations list** and select the destination you'd like to view. On the event forwarders overview table, you will see metrics for each forwarder configured for that destination.
+To view these metrics, navigate to **Destinations** > **Event forwarding**. In the event forwarders table, you will see metrics for each forwarder.
 
 ![Console metrics dashboard showing forwarder statistics including filtered, failed, and delivered event counts](images/event-forwarding-console-metrics.png)
 

docs/destinations/forwarding-events/managing-forwarders/index.md

@@ -6,7 +6,7 @@ description: "Edit, clone, and delete Snowplow event forwarders in Console to up
 keywords: ["manage forwarders", "edit forwarder", "delete forwarder", "clone forwarder", "forwarder configuration"]
 ---
 
-This page explains how to edit, clone, and delete event forwarders. To start, go to **Destinations** > **Destination list** in [Snowplow Console](https://console.snowplowanalytics.com).
+This page explains how to edit, clone, and delete event forwarders. To start, go to **Destinations** > **Event forwarding** in [Snowplow Console](https://console.snowplowanalytics.com).
 
 ## Edit a forwarder
 
@@ -30,7 +30,7 @@ When creating a new forwarder, you can import the configuration from an existing
 
 To clone a forwarder:
 
-1. Navigate to the **Available** tab and select **Configure** on the destination card from the list of available integrations to start setting up the forwarder.
+1. Click **Add destination** and select the destination from the list of available integrations to start setting up the forwarder.
 2. Give the forwarder a **name**, select the **pipeline** you want the forwarder to read events from, and choose a **connection**.
 3. From the **Import configuration from** dropdown, choose an existing forwarder.
 4. Click **Continue**. The filters, mappings, and custom functions will be pre-populated with those of the existing forwarder you imported from.
@@ -39,6 +39,5 @@ To clone a forwarder:
 
 To permanently delete a forwarder:
 
-1. Click **Details** under the destination you want to change to open the destination details page.
-2. On the event forwarders overview table, click the three dots next to the forwarder you want to change and select **Delete**.
-3. On the confirmation modal, select **Delete**. This will start the process of destroying the underlying forwarder infrastructure.
+1. In the event forwarders overview table, click the three dots next to the forwarder you want to change and select **Delete**.
+2. On the confirmation modal, select **Delete**. This will start the process of destroying the underlying forwarder infrastructure.

docs/destinations/warehouses-lakes/_setup-instructions.mdx

@@ -1,21 +1,21 @@
 ### Step 1: Create a connection
 
 <ol>
-<li>In Console, navigate to <strong>Destinations</strong>&nbsp;&gt;&nbsp;<strong>Connections</strong></li>
+<li>In Console, navigate to <strong>Settings</strong>&nbsp;&gt;&nbsp;<strong>Connections</strong></li>
 <li>Select <strong>Set up connection</strong></li>
-<li>Choose <strong>Loader connection</strong>, then <strong>{props.connectionType}</strong></li>
+<li>Choose <strong>Event loading</strong>, then <strong>{props.connectionType}</strong></li>
 <li>Follow the steps to provide all the necessary values</li>
 <li>Click <strong>Complete setup</strong> to create the connection</li>
 </ol>
 
 ### Step 2: Create a loader
 
 <ol>
-<li>In Console, navigate to <strong>Destinations</strong>&nbsp;&gt;&nbsp;<strong>Destination list</strong>. Switch to the <strong>Available</strong> tab and select <strong>{props.destinationName}</strong></li>
+<li>In Console, navigate to <strong>Destinations</strong>&nbsp;&gt;&nbsp;<strong>Warehouses and lakes</strong>. Click <strong>Add destination</strong> and select <strong>{props.destinationName}</strong></li>
 <li><strong>Select a pipeline</strong>: choose the pipeline where you want to deploy the loader.</li>
 <li><strong>Select your connection</strong>: choose the connection you configured in step 1.</li>
 {!props.noFailedEvents && <li><strong>Select the type of events</strong>: enriched events or failed events</li>}
 <li>Click <strong>Continue</strong> to deploy the loader</li>
 </ol>
 
-You can review active destinations and loaders by navigating to **Destinations**&nbsp;&gt;&nbsp;**Destination list**.
+You can review active destinations and loaders by navigating to **Destinations**&nbsp;&gt;&nbsp;**Warehouses and lakes**.

docs/destinations/warehouses-lakes/redshift/index.md

@@ -65,7 +65,7 @@ Snowplow data also includes customizable [self-describing events](/docs/fundamen
 For each type of self-describing event and entity, there are additional tables that can be joined with the main table:
 
 <details>
-<summary>unstruct_event_com_acme_button_press_1</summary>
+<summary>com_acme_button_press_1</summary>
 
 | root_id | root_tstamp | button_name | button_color | ... |
 | ------- | ----------- | ----------- | ------------ | --- |
@@ -74,7 +74,7 @@ For each type of self-describing event and entity, there are additional tables t
 </details>
 
 <details>
-<summary>contexts_com_acme_product_1</summary>
+<summary>com_acme_product_1</summary>
 
 | root_id | root_tstamp | name | price | ... |
 | ------- | ----------- | ---- |------ | --- |
@@ -83,9 +83,9 @@ For each type of self-describing event and entity, there are additional tables t
 
 </details>
 
-Note:
-* "unstruct\[ured\] event" and "context" are the legacy terms for self-describing events and entities, respectively
-* the `_1` suffix represents the major version of the schema (e.g. `1-x-y`)
+:::note
+The `_1` suffix represents the major version of the schema (e.g. `1-x-y`).
+:::
 
 You can learn more [in the API reference section](/docs/api-reference/loaders-storage-targets/schemas-in-warehouse/index.md).