Apply suggestions from code review

Co-authored-by: Bruno Galvao <[email protected]>

Author: nhussein11

develop/interoperability/.nav.yml

@@ -3,9 +3,9 @@ nav:
   - index.md
   - 'Introduction to XCM': intro-to-xcm.md
   - 'Channels': xcm-channels.md
-  - 'Runtime Configuration': xcm-config.md
+  - 'XCM Runtime Configuration': xcm-config.md
   - 'Send Messages': send-messages.md
-  - 'Runtime APIs': xcm-runtime-apis.md
+  - 'XCM Runtime APIs': xcm-runtime-apis.md
   - 'Test and Debug': test-and-debug.md
   - guides
   - versions

develop/interoperability/guides/from-apps/claiming-trapped-assets.md

@@ -1,13 +1,13 @@
 ---
 title: Claiming Trapped Assets
-description: How to claim digital assets that become trapped on-chain due to an XCM execution failure. This guide details the process and required steps.
+description: How to claim assets that become trapped on-chain due to an XCM execution failure. This guide details the process and required steps.
 ---
 
 # Claiming Trapped Assets
 
 ## Introduction
 
-When XCM execution fails or succeeds, leftover assets become "trapped" on the destination chain. These assets are held by the system but not accessible through normal means. XCM provides mechanisms to claim these trapped assets and recover them.
+When XCM execution fails or succeeds, leftover assets can become "trapped" on the destination chain. These assets are held by the system but not accessible through normal means. XCM provides mechanisms to claim these trapped assets and recover them.
 This guide details the process and required steps to claim trapped assets.
 
 ## Trapped Assets Causes

develop/interoperability/guides/from-apps/transfers.md

@@ -21,7 +21,7 @@ XcmV5Instruction.InitiateTransfer({
 
 ## Transfer Types
 
-The `remote_fees` parameter only takes one asset, `assets` takes a list of many. Both need to specify which transfer type they're using. The developer needs to specify whether or not those assets are transferred via a [`Teleport`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.AssetTransferFilter.html#variant.Teleport){target=\_blank}, a [`ReserveWithdraw`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.AssetTransferFilter.html#variant.ReserveWithdraw){target=\_blank} or a [`ReserveDeposit`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.AssetTransferFilter.html#variant.ReserveDeposit){target=\_blank}. These correspond to the types of cross-chain transfers.
+The `remote_fees` parameter only takes one asset. The `assets` parameter takes a list of many. Both need to specify which transfer type they're using. The developer needs to specify whether or not those assets are transferred via a [`Teleport`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.AssetTransferFilter.html#variant.Teleport){target=\_blank}, a [`ReserveWithdraw`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.AssetTransferFilter.html#variant.ReserveWithdraw){target=\_blank} or a [`ReserveDeposit`](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.AssetTransferFilter.html#variant.ReserveDeposit){target=\_blank}. These correspond to the types of cross-chain transfers.
 
 For example, to transfer 50 DOT via a teleport, the transfer type must be specified as a teleport. This also requires using an [Asset Filter](https://paritytech.github.io/polkadot-sdk/master/staging_xcm/v5/enum.AssetFilter.html){target=\_blank}.
 

develop/interoperability/versions/.nav.yml

@@ -1,4 +1,4 @@
-title: Versions
+title: XCM Versions
 nav:
   - index.md
   - 'Version 5': v5

develop/interoperability/versions/index.md

@@ -4,7 +4,7 @@ description: Explore the different versions of XCM, understand version-specific
 template: index-page.html
 ---
 
-# Versions
+# XCM Versions
 
 XCM is a versioned language that evolves to meet the growing needs of cross-chain communication in the Polkadot ecosystem. Understanding XCM versioning is essential for developers building interoperable applications to keep up with the latest improvements.