greater context about steps [netlify-build]

Author: forstisabella

src/connections/delivery-overview.md

@@ -23,7 +23,7 @@ The pipeline view shows the following steps:
 - **Successfully received**: Events that Segment ingested from your source
 - **Failed on ingest**: Events that Segment received, but were dropped due to internal data validation rules
 - **Filtered at source**: Events that were discarded due to schema settings or [Protocols](/docs/protocols/) Tracking Plans
-- ***(Actions destinations only)*** **Mappings**: Select a [mapping](/docs/connections/destinations/actions/#customize-mappings) from the dropdown to view metrics for mapped events in the destination steps
+- ***(Actions destinations only)*** **Mappings**: Select a [mapping](/docs/connections/destinations/actions/#customize-mappings) from the dropdown to view metrics for mapped events in the Filtered at destination, Failed delivery and Successful delivery steps
 - **Filtered at destination**: Events that were discarded due to [Destination Filters](/docs/guides/filtering-data/#destination-filters), [filtering in the Integrations object](/docs/guides/filtering-data/#filtering-with-the-integrations-object), or [per source schema integration filters](/docs/guides/filtering-data/#per-source-schema-integrations-filters). [Actions destinations](/docs/connections/destinations/actions/) also have a filtering capability: for example, if your Action is set to only send Identify events, all other event types will be filtered out. Actions destinations with incomplete triggers or disabled mappings are filtered out at this step. <!--- Beta users of [Consent Management](/docs/privacy/consent-management/) also see events discarded due to consent preferences.--->
 - **Failed delivery**: Events that have been discarded due to errors or unmet destination requirements
 - **Successful delivery**: Events that were successfully delivered to the destination