Update the order

raymondkfcheung · raymondkfcheung · commit d25c27a1fe56 · 2025-08-07T15:54:50.000+01:00
diff --git a/llms.txt b/llms.txt
@@ -27833,9 +27833,9 @@ You will learn how to:
 
 - Use `SetTopic` and `message_id` to track XCMs across multiple chains
 - Match `PolkadotXcm.Sent` and `MessageQueue.Processed` events to understand message flow
-- Interpret and handle failed or incomplete messages
 - Apply manual topic tagging for reliable tracking across hops
 - Use the workaround for older runtimes that emit derived message identifiers
+- Interpret and handle failed or incomplete messages
 
 To demonstrate these techniques, the guide introduces a complete example scenario involving a multi-chain XCM transfer. This scenario will serve as the foundation for explaining message lifecycle, event tracking and failure debugging in context.
 
diff --git a/tutorials/interoperability/xcm-observability.md b/tutorials/interoperability/xcm-observability.md
@@ -13,9 +13,9 @@ You will learn how to:
 
 - Use `SetTopic` and `message_id` to track XCMs across multiple chains
 - Match `PolkadotXcm.Sent` and `MessageQueue.Processed` events to understand message flow
-- Interpret and handle failed or incomplete messages
 - Apply manual topic tagging for reliable tracking across hops
 - Use the workaround for older runtimes that emit derived message identifiers
+- Interpret and handle failed or incomplete messages
 
 To demonstrate these techniques, the guide introduces a complete example scenario involving a multi-chain XCM transfer. This scenario will serve as the foundation for explaining message lifecycle, event tracking and failure debugging in context.
 
