fix: formatting for guide

Author: nhussein11

develop/interoperability/versions/v5/asset-claimer.md

@@ -1,25 +1,25 @@
 ---
 title: Asset claimer
-description: How the AssetClaimer hint improves trapped asset recovery in XCMv5.
+description: Learn how the AssetClaimer hint improves trapped asset recovery in XCM V5, enabling automated recovery and reducing the need for governance intervention.
 ---
 
-# Asset claimer
+# Asset Claimer (XCM V4 → XCM V5)
 
-XCMv5 introduces the `AssetClaimer` execution hint through `SetHints`, which significantly simplifies the process of recovering trapped assets when XCM execution fails.
+XCMv5 introduces the [`AssetClaimer`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.Hint.html#variant.AssetClaimer){target=\_blank} execution hint through [`SetHints`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.Instruction.html#variant.SetHints){target=\_blank}, which significantly simplifies the process of recovering trapped assets when XCM execution fails.
 
 ## The problem before v5
 
 When XCM execution failed and assets became trapped:
 
-- **Governance dependency**: Most trapped asset recovery required governance proposals
-- **Complex procedures**: Manual intervention through referendum processes
-- **Long delays**: Recovery could take weeks or months through governance
-- **Risk of loss**: Assets could remain permanently trapped if governance didn't act
-- **High barriers**: Small amounts often weren't worth the governance overhead
+- **Governance dependency**: Most trapped asset recovery required governance proposals.
+- **Complex procedures**: Manual intervention through referendum processes.
+- **Long delays**: Recovery could take weeks or months through governance.
+- **Risk of loss**: Assets could remain permanently trapped if governance didn't act.
+- **High barriers**: Small amounts often weren't worth the governance overhead.
 
-## The v5 solution: AssetClaimer hint
+## The V5 Solution: `AssetClaimer` Hint
 
-The new `AssetClaimer` hint allows XCM programs to preemptively designate who can claim trapped assets:
+The new [`AssetClaimer`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.Hint.html#variant.AssetClaimer){target=\_blank} hint allows XCM programs to preemptively designate who can claim trapped assets:
 
 ```typescript
 // Set asset claimer before risky operations
@@ -28,9 +28,10 @@ XcmV5Instruction.SetHints({
 })
 ```
 
-## How it improves the situation
+## How it Improves the Situation
+
+### Before XCM V5
 
-### Before XCMv5
 ```typescript
 // If this XCM fails, assets become trapped
 const riskyXcm = [
@@ -43,7 +44,8 @@ const riskyXcm = [
 // Recovery required governance intervention
 ```
 
-### With XCMv5
+### With XCM V5
+
 ```typescript
 // Proactive asset claimer setup
 const saferXcm = [
@@ -60,34 +62,40 @@ const saferXcm = [
 // Recovery can be done immediately by the claimer
 ```
 
-## Key improvements
+## Key Improvements
+
+### Immediate Recovery
+
+- **Before**: Wait for governance process (weeks/months).
+- **After**: Designated claimer can act immediately.
+
+### Reduced Governance Burden
 
-### 1. Immediate recovery
-- **Before**: Wait for governance process (weeks/months)
-- **After**: Designated claimer can act immediately
+- **Before**: Every trapped asset required a governance proposal.
+- **After**: Only complex cases need governance intervention.
 
-### 2. Reduced governance burden
-- **Before**: Every trapped asset required a governance proposal
-- **After**: Only complex cases need governance intervention
+### Predictable Recovery
 
-### 3. Predictable recovery
 - **Before**: Uncertain if governance would approve recovery
 - **After**: Predetermined claimer provides certainty
 
-### 4. Lower barriers
-- **Before**: Small amounts often not worth governance overhead
-- **After**: Any amount can be efficiently recovered
+### Lower Barriers
 
-## Best practices
+- **Before**: Small amounts often not worth governance overhead.
+- **After**: Any amount can be efficiently recovered.
+
+## Best Practices
+
+### Set Hint Early
 
-### 1. Set hint early
 ```typescript
 // Set claimer hint before any risky operations
 XcmV5Instruction.SetHints({ hints: [Enum('AssetClaimer', claimerLocation)] }),
 // ... other instructions that might fail
 ```
 
-### 2. Use for cross-chain transfers
+### Use for Cross-Chain Transfers
+
 Particularly useful for setting local accounts on destination chains:
 
 ```typescript
@@ -103,16 +111,17 @@ const remoteXcm = [
 ]
 ```
 
-### 3. Consider origin preservation
+### Consider Origin Preservation
+
 When origin preservation is available, trapped assets are automatically associated with the original origin, making claiming easier without additional hints.
 
-## Migration impact
+## Migration Impact
 
 This change makes XCM programs more resilient and user-friendly:
 
-- **Reduced risk**: Assets are less likely to be permanently lost
-- **Better UX**: Users can recover their own assets without waiting for governance
-- **Increased adoption**: Lower risk encourages more XCM usage
-- **Operational efficiency**: Reduces governance workload for routine recoveries
+- **Reduced risk**: Assets are less likely to be permanently lost.
+- **Better UX**: Users can recover their own assets without waiting for governance.
+- **Increased adoption**: Lower risk encourages more XCM usage.
+- **Operational efficiency**: Reduces governance workload for routine recoveries.
 
 The `AssetClaimer` hint represents a significant improvement in XCM's fault tolerance and user experience, making cross-chain operations safer and more predictable.

llms.txt

@@ -1790,26 +1790,26 @@ Doc-Content: https://docs.polkadot.com/develop/interoperability/versions/v5/asse
 --- BEGIN CONTENT ---
 ---
 title: Asset claimer
-description: How the AssetClaimer hint improves trapped asset recovery in XCMv5.
+description: Learn how the AssetClaimer hint improves trapped asset recovery in XCM V5, enabling automated recovery and reducing the need for governance intervention.
 ---
 
-# Asset claimer
+# Asset Claimer (XCM V4 → XCM V5)
 
-XCMv5 introduces the `AssetClaimer` execution hint through `SetHints`, which significantly simplifies the process of recovering trapped assets when XCM execution fails.
+XCMv5 introduces the [`AssetClaimer`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.Hint.html#variant.AssetClaimer){target=\_blank} execution hint through [`SetHints`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.Instruction.html#variant.SetHints){target=\_blank}, which significantly simplifies the process of recovering trapped assets when XCM execution fails.
 
 ## The problem before v5
 
 When XCM execution failed and assets became trapped:
 
-- **Governance dependency**: Most trapped asset recovery required governance proposals
-- **Complex procedures**: Manual intervention through referendum processes
-- **Long delays**: Recovery could take weeks or months through governance
-- **Risk of loss**: Assets could remain permanently trapped if governance didn't act
-- **High barriers**: Small amounts often weren't worth the governance overhead
+- **Governance dependency**: Most trapped asset recovery required governance proposals.
+- **Complex procedures**: Manual intervention through referendum processes.
+- **Long delays**: Recovery could take weeks or months through governance.
+- **Risk of loss**: Assets could remain permanently trapped if governance didn't act.
+- **High barriers**: Small amounts often weren't worth the governance overhead.
 
-## The v5 solution: AssetClaimer hint
+## The V5 Solution: `AssetClaimer` Hint
 
-The new `AssetClaimer` hint allows XCM programs to preemptively designate who can claim trapped assets:
+The new [`AssetClaimer`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.Hint.html#variant.AssetClaimer){target=\_blank} hint allows XCM programs to preemptively designate who can claim trapped assets:
 
 ```typescript
 // Set asset claimer before risky operations
@@ -1818,9 +1818,10 @@ XcmV5Instruction.SetHints({
 })
 ```
 
-## How it improves the situation
+## How it Improves the Situation
+
+### Before XCM V5
 
-### Before XCMv5
 ```typescript
 // If this XCM fails, assets become trapped
 const riskyXcm = [
@@ -1833,7 +1834,8 @@ const riskyXcm = [
 // Recovery required governance intervention
 ```
 
-### With XCMv5
+### With XCM V5
+
 ```typescript
 // Proactive asset claimer setup
 const saferXcm = [
@@ -1850,34 +1852,40 @@ const saferXcm = [
 // Recovery can be done immediately by the claimer
 ```
 
-## Key improvements
+## Key Improvements
+
+### Immediate Recovery
+
+- **Before**: Wait for governance process (weeks/months).
+- **After**: Designated claimer can act immediately.
+
+### Reduced Governance Burden
 
-### 1. Immediate recovery
-- **Before**: Wait for governance process (weeks/months)
-- **After**: Designated claimer can act immediately
+- **Before**: Every trapped asset required a governance proposal.
+- **After**: Only complex cases need governance intervention.
 
-### 2. Reduced governance burden
-- **Before**: Every trapped asset required a governance proposal
-- **After**: Only complex cases need governance intervention
+### Predictable Recovery
 
-### 3. Predictable recovery
 - **Before**: Uncertain if governance would approve recovery
 - **After**: Predetermined claimer provides certainty
 
-### 4. Lower barriers
-- **Before**: Small amounts often not worth governance overhead
-- **After**: Any amount can be efficiently recovered
+### Lower Barriers
 
-## Best practices
+- **Before**: Small amounts often not worth governance overhead.
+- **After**: Any amount can be efficiently recovered.
+
+## Best Practices
+
+### Set Hint Early
 
-### 1. Set hint early
 ```typescript
 // Set claimer hint before any risky operations
 XcmV5Instruction.SetHints({ hints: [Enum('AssetClaimer', claimerLocation)] }),
 // ... other instructions that might fail
 ```
 
-### 2. Use for cross-chain transfers
+### Use for Cross-Chain Transfers
+
 Particularly useful for setting local accounts on destination chains:
 
 ```typescript
@@ -1893,17 +1901,18 @@ const remoteXcm = [
 ]
 ```
 
-### 3. Consider origin preservation
+### Consider Origin Preservation
+
 When origin preservation is available, trapped assets are automatically associated with the original origin, making claiming easier without additional hints.
 
-## Migration impact
+## Migration Impact
 
 This change makes XCM programs more resilient and user-friendly:
 
-- **Reduced risk**: Assets are less likely to be permanently lost
-- **Better UX**: Users can recover their own assets without waiting for governance
-- **Increased adoption**: Lower risk encourages more XCM usage
-- **Operational efficiency**: Reduces governance workload for routine recoveries
+- **Reduced risk**: Assets are less likely to be permanently lost.
+- **Better UX**: Users can recover their own assets without waiting for governance.
+- **Increased adoption**: Lower risk encourages more XCM usage.
+- **Operational efficiency**: Reduces governance workload for routine recoveries.
 
 The `AssetClaimer` hint represents a significant improvement in XCM's fault tolerance and user experience, making cross-chain operations safer and more predictable.
 --- END CONTENT ---