mulesoft · dmerlob · Jul 18, 2024 · Jul 18, 2024
@@ -12,7 +12,7 @@ An app can consist of a single flow, or it can break up processing into
 discrete flows and subflows that you add to the app and connect together. Mule
 apps in production environments typically use multiple flows and subflows
 to divide the app into functional modules or for
-<<error_handling, error-handling>> purposes. For example, one flow might
+<<error_handling, error handling>> purposes. For example, one flow might
 receive a record and transform data into a given format that another
 flow processes in some special way.
 
@@ -51,6 +51,7 @@ Because the contents of a subflow replace each Flow Reference component that ref
 
 For example, configuring a batch job inside a subflow causes the application to fail during deployment if the subflow is referenced from more than one Flow Reference component. The application fails to deploy because multiple instances of a batch job with the same job instance ID exist, which is not allowed.
 
+[[error_handling]]
 == Error Handling
 
 Each flow (but not subflow) can have its own error handling. One reason for

@@ -40,5 +40,5 @@ This practice makes analysis and debugging easier and more intuitive at runtime.
 
 * xref:about-mule-event.adoc[Mule Events]
 * xref:transaction-management.adoc[Transaction Management]
-* xref:business-events-in-components[Configure Default Events Tracking]
+* xref:business-events-in-components.adoc[Configure Default Events Tracking]
 * xref:business-events-custom.adoc[Custom Business Event Component]
@@ -79,7 +79,7 @@ POST, PUT, and DELETE requests almost always require headers.
 * URI and Query Parameters
 * Error handling
 
-See xref:connectors::http-connector[HTTP Connector documentation] for more information about how to configure the request operation.
+See xref:http-connector::index.adoc#input-sources[HTTP Connector documentation] for more information about how to configure the request operation.
 
 
 === Consume REST API Example

@@ -238,7 +238,6 @@ In Mule 4, you can add child elements for these settings under the database conn
 * <<column_types>>
 * <<pooling_profile>>
 * <<reconnection_strategies>>
-* <<expiration_policies>>
 
 [[db_transactions]]
 ==== Database Transactions
@@ -369,7 +368,7 @@ The examples below show changes to the XML for these settings:
 [[database_operations_overview]]
 == Database Connector Operations
 
-* Query for SQL query text and input parameters (as shown here in <<database_operation_select>>).
+* Query for SQL query text and input parameters
 * Streaming strategy settings (as shown here in <<database_streaming>>)
 * <<tx_actions>>
 * Query settings

@@ -58,4 +58,4 @@ The following examples compare MUnit tests in 1.x to 2.x.
 
 == See Also
 
-* xref:https://docs.mulesoft.com/munit/2.2/munit-test-concept[MUnit 2 Test structure]
+* xref:2.2@munit::munit-test-concept.adoc[MUnit 2 Test structure]
@@ -100,6 +100,6 @@ requests.
 
 xref:migration-connectors.adoc[Migrating Connectors and Modules to Mule 4]
 
-xref:intro-java-integration[Java Integration]
+xref:intro-java-integration.adoc[Java Integration]
 
 xref:1.1@mule-sdk::index.adoc[Mule SDK]
@@ -240,4 +240,4 @@ output application/json
 
 * xref:mule-error-concept.adoc[Mule Errors]
 * xref:try-scope-concept.adoc[Try Scope]
-* xref:mule-server-notifications[Mule Runtime Engine Notifications]
+* xref:mule-server-notifications.adoc[Mule Runtime Engine Notifications]
@@ -38,7 +38,7 @@ The `<ee:transform>` element is the top-level XML tag for the Transform componen
 
 == Adding DataWeave Scripts to the Transform Component
 
-You can either type your DataWeave code into your XML using `CDATA` within a <<transformation, Transformation>> element, or you can reference an external `.dwl` file.
+You can either type your DataWeave code into your XML using `CDATA` within a <<transformations, Transformations>> element, or you can reference an external `.dwl` file.
 
 This example that writes a DataWeave script inline within a `<dw:set-payload>` transformation element: