Update from SAP DITA CMS (squashed):

commit 1a0cb380b1f812259f749d2e6eb1f2fedda3e417
Author: REDACTED
Date:   Mon Jul 15 07:24:49 2024 +0000

    Update from SAP DITA CMS 2024-07-15 07:24:49
    Project: dita-all/rqs1627049557344
    Project map: eeb0d7e6335f4e73b4158bf8f2d82b8c.ditamap
    Output: loio2fb418ef35ea47f9ad0d99b3ed84b370
    Language: en-US
    Builddable map: 11b78b7d7def4d739976a99060a8b676.ditamap

commit ef91fbe7b6ba173f446c2d02e0b3c7a951d31416
Author: REDACTED
Date:   Wed Jul 10 12:51:40 2024 +0000

    Update from SAP DITA CMS 2024-07-10 12:51:40
    Project: dita-all/rqs1627049557344
    Project map: eeb0d7e6335f4e73b4158bf8f2d82b8c.ditamap
    Output: loio2fb418ef35ea47f9ad0d99b3ed84b370
    Language: en-US
    Builddable map: 11b78b7d7def4d739976a99060a8b676.ditamap

commit c92008848f8a244d3d390622e5b3497f43446bce
Author: REDACTED
Date:   Wed Jul 10 08:58:09 2024 +0000

    Update from SAP DITA CMS 2024-07-10 08:58:09
    Project: dita-all/rqs1627049557344
    Project map: eeb0d7e6335f4e73b4158bf8f2d82b8c.ditamap
    Output: loio2fb418ef35ea47f9ad0d99b3ed84b370
    Language: en-US
    Builddable map: 11b78b7d7def4d739976a99060a8b676.ditamap

##################################################
[Remaining squash message was removed before commit...]

docs/70-interface-migration/pipeline-steps-f8e69f4.md

@@ -12,11 +12,11 @@ The following fixed sequence of integration flows makes up the pipeline steps:
 
 2.  [Inbound Processing \(Generic\)](pipeline-steps-f8e69f4.md#loiof8e69f43059a44cdb891892f4ff083d8__section_ryf_vyk_31c): Dispatches the messages to the inbound conversion and handles the retry of messages with inbound conversion errors.
 
-3.  [Conversion at Inbound \(Scenario-Specific\)](pipeline-steps-f8e69f4.md#loiof8e69f43059a44cdb891892f4ff083d8__section_q1q_vyk_31c): Runs conversion at the Cloud Integration inbound such as JSON to XML conversion.
+3.  [Conversion at Inbound \(Scenario-Specific\)](pipeline-steps-f8e69f4.md#loiof8e69f43059a44cdb891892f4ff083d8__section_q1q_vyk_31c)
 
-4.  [Receiver Determination \(Generic\)](pipeline-steps-f8e69f4.md#loiof8e69f43059a44cdb891892f4ff083d8__section_qbb_wyk_31c): Determines the receivers in a content-based router or recipient list pattern scenario.
+4.  [Receiver Determination \(Generic\)](pipeline-steps-f8e69f4.md#loiof8e69f43059a44cdb891892f4ff083d8__section_qbb_wyk_31c): Determines the receivers in a content-based router or recipient list pattern scenario.: Runs conversion at the Cloud Integration inbound such as JSON to XML conversion.
 
-5.  [Interface Determination \(Generic\)](pipeline-steps-f8e69f4.md#loiof8e69f43059a44cdb891892f4ff083d8__section_drs_wyk_31c): Determines the receiver interfaces in an interface split scenario.
+5.  [Interface Determination \(Generic\)](pipeline-steps-f8e69f4.md#loiof8e69f43059a44cdb891892f4ff083d8__section_drs_wyk_31c):: Determines the receiver interfaces in an interface split scenario.
 
 6.  [Outbound Processing \(Generic\)](pipeline-steps-f8e69f4.md#loiof8e69f43059a44cdb891892f4ff083d8__section_yqj_xyk_31c): Dispatches the messages to the message outbound and handles the retry of failed messages.
 

docs/70-interface-migration/testing-the-pipeline-e373569.md

@@ -8,7 +8,7 @@ The following partner offerings support the pipeline concept in their migration
 
 -   Learn about **Int4**'s offerings in the blog [SAP Pipeline Concept and B2B TPM Testing](https://community.sap.com/t5/technology-blogs-by-members/sap-pipeline-concept-and-b2b-tpm-testing/ba-p/13691706).
 
--   Learn about **Figaf**'s offerings in the blog [First Run of SAP's Pipelines for Integration Suite](https://community.sap.com/t5/technology-blogs-by-members/first-run-of-saps-pipelines-for-integration-suite/ba-p/13655583).
+-   Learn about **Figaf**'s offerings in the blog [Testing SAP Pipeline Concept Flows with Figaf](https://community.sap.com/t5/technology-blogs-by-members/testing-sap-pipeline-concept-flows-with-figaf/ba-p/13754121).
 
 
 Furthermore, the new header **`testMode`** is passed between the sequence of integration flows. Use this `testMode` header to define the processing behavior for scenario tests, for example, when sending the message to a mocked receiver instead of to the actual receiver. See [Custom Exception Handling](monitoring-and-error-handling-in-the-pipeline-concept-ed9b82c.md#loioed9b82cb928049e6990a4d784aa6aac7__section_pm1_ggs_5bc) and [IDoc Sender Adapter](special-cases-1606af9.md#loio1606af9b55bf4391bea01d2f7ee112af__section_tjw_z3f_j1c).