Update wording on manual SetTopic (#1002)

* Update wording for custom SetTopic

* Update wording for custom SetTopic

* Update wording for custom SetTopic

Author: raymondkfcheung

develop/interoperability/xcm-observability.md

@@ -48,7 +48,7 @@ Matching these IDs allows you to correlate an origin message with its destinatio
 
 - The runtime automatically appends a `SetTopic` instruction if one is missing at the end of an XCM.
 - When using high-level extrinsics such as `limited_reserve_transfer_assets`, you do not need to set a topic manually; the runtime handles it for you.
-- If you manually craft an XCM (e.g., via [`execute`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/struct.Pallet.html#method.execute){target=\_blank} or [`send`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/struct.Pallet.html#method.send){target=\_blank}), you can supply your own `SetTopic`, but it must be the final instruction to be respected.
+- When manually crafting an XCM via [`execute`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/struct.Pallet.html#method.execute){target=\_blank} or [`send`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/struct.Pallet.html#method.send){target=\_blank}), you can include a `SetTopic` as the final instruction; otherwise, `WithUniqueTopic` will append its own unique ID, overriding earlier `SetTopic` instructions.
 - In multi-hop XCM flows, manually setting the topic ensures consistent tracing across all hops. Any remote XCM calls embedded inside the XCM must also include a `SetTopic` at the end to preserve the same `message_id` throughout the cross-chain flow.
 
 ## Message Lifecycle
@@ -99,6 +99,8 @@ Tools and indexers tracing messages across mixed runtime versions should check b
 --8<-- 'code/develop/interoperability/xcm-observability/forward-id-for.ts'
 ```
 
+> Note: `@noble/hashes` and `polkadot-api` are required dependencies for this code to work.
+
 ## Failure Event Handling
 
 When an XCM fails, the transaction rolls back and no explicit failure event is emitted on-chain. The following are some ways to check for XCM failure:

llms-full.txt

@@ -3163,7 +3163,7 @@ Doc-Content: https://docs.polkadot.com/develop/interoperability/xcm-observabilit
 --- BEGIN CONTENT ---
 ---
 title: XCM Observability
-description: This conceptual overview of XCM observability in Polkadot covers message correlation, tracing, and debugging features in modern runtimes.
+description: A conceptual overview of XCM observability in Polkadot covers message correlation, tracing, and debugging features in modern runtimes.
 ---
 
 # XCM Observability
@@ -3211,7 +3211,7 @@ Matching these IDs allows you to correlate an origin message with its destinatio
 
 - The runtime automatically appends a `SetTopic` instruction if one is missing at the end of an XCM.
 - When using high-level extrinsics such as `limited_reserve_transfer_assets`, you do not need to set a topic manually; the runtime handles it for you.
-- If you manually craft an XCM (e.g., via [`execute`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/struct.Pallet.html#method.execute){target=\_blank} or [`send`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/struct.Pallet.html#method.send){target=\_blank}), you can supply your own `SetTopic`, but it must be the final instruction to be respected.
+- When manually crafting an XCM via [`execute`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/struct.Pallet.html#method.execute){target=\_blank} or [`send`](https://paritytech.github.io/polkadot-sdk/master/pallet_xcm/pallet/struct.Pallet.html#method.send){target=\_blank}), you can include a `SetTopic` as the final instruction; otherwise, `WithUniqueTopic` will append its own unique ID, overriding earlier `SetTopic` instructions.
 - In multi-hop XCM flows, manually setting the topic ensures consistent tracing across all hops. Any remote XCM calls embedded inside the XCM must also include a `SetTopic` at the end to preserve the same `message_id` throughout the cross-chain flow.
 
 ## Message Lifecycle
@@ -3293,6 +3293,8 @@ if (forwardedIdHex === expectedForwardedId) {
 }
 ```
 
+> Note: `@noble/hashes` and `polkadot-api` are required dependencies for this code to work.
+
 ## Failure Event Handling
 
 When an XCM fails, the transaction rolls back and no explicit failure event is emitted on-chain. The following are some ways to check for XCM failure:
@@ -31110,7 +31112,7 @@ Before you begin, ensure you have the following:
     wget https://github.com/polkadot-fellows/runtimes/releases/download/v1.6.0/asset-hub-polkadot_runtime-v1006000.compact.compressed.wasm -O wasms/asset-hub-polkadot_v1.6.0.wasm
     ```
 
-4. Download the config for Polkadot Hub:
+4. Download the config file for Polkadot Hub:
 
     ```bash
     mkdir -p configs
@@ -31148,7 +31150,7 @@ Before you begin, ensure you have the following:
 
     ```bash
     npm install --save-dev typescript @types/node tsx
-    npm install  polkadot-api @polkadot-labs/hdkd @polkadot-labs/hdkd-helpers
+    npm install polkadot-api @polkadot-labs/hdkd @polkadot-labs/hdkd-helpers
     npm install @noble/hashes
     ```
 

llms.txt

@@ -25,7 +25,7 @@
 - [Transact](https://raw.githubusercontent.com/polkadot-developers/polkadot-docs/refs/heads/master/develop/interoperability/xcm-guides/from-apps/transact.md): Learn how to execute arbitrary calls on remote chains using the Transact instruction, enabling cross-chain function execution and remote pallet interactions.
 - [Transfers](https://raw.githubusercontent.com/polkadot-developers/polkadot-docs/refs/heads/master/develop/interoperability/xcm-guides/from-apps/transfers.md): Learn how to perform cross-chain asset transfers using XCM, including teleport, reserve transfers, and handling different asset types across parachains.
 - [XCM Guides](https://raw.githubusercontent.com/polkadot-developers/polkadot-docs/refs/heads/master/develop/interoperability/xcm-guides/index.md): Comprehensive guides for implementing XCM functionality in applications and understanding cross-chain interactions.
-- [XCM Observability](https://raw.githubusercontent.com/polkadot-developers/polkadot-docs/refs/heads/master/develop/interoperability/xcm-observability.md): This conceptual overview of XCM observability in Polkadot covers message correlation, tracing, and debugging features in modern runtimes.
+- [XCM Observability](https://raw.githubusercontent.com/polkadot-developers/polkadot-docs/refs/heads/master/develop/interoperability/xcm-observability.md): A conceptual overview of XCM observability in Polkadot covers message correlation, tracing, and debugging features in modern runtimes.
 - [XCM Runtime APIs](https://raw.githubusercontent.com/polkadot-developers/polkadot-docs/refs/heads/master/develop/interoperability/xcm-runtime-apis.md): Learn about XCM Runtime APIs in Polkadot for cross-chain communication. Explore the APIs to simulate and test XCM messages before execution on the network.
 - [Networks](https://raw.githubusercontent.com/polkadot-developers/polkadot-docs/refs/heads/master/develop/networks.md): Explore the Polkadot ecosystem networks and learn the unique purposes of each, tailored for blockchain innovation, testing, and enterprise-grade solutions.
 - [Add a Pallet to the Runtime](https://raw.githubusercontent.com/polkadot-developers/polkadot-docs/refs/heads/master/develop/parachains/customize-parachain/add-existing-pallets.md): Learn how to include and configure pallets in a Polkadot SDK-based runtime, from adding dependencies to implementing necessary traits.

tutorials/interoperability/xcm-observability-in-action.md

@@ -85,7 +85,7 @@ Before you begin, ensure you have the following:
 
     ```bash
     npm install --save-dev typescript @types/node tsx
-    npm install  polkadot-api @polkadot-labs/hdkd @polkadot-labs/hdkd-helpers
+    npm install polkadot-api @polkadot-labs/hdkd @polkadot-labs/hdkd-helpers
     npm install @noble/hashes
     ```