update formatting

Author: eshaben

llms.txt

@@ -19,7 +19,7 @@ Before starting, ensure the following tools and dependencies are installed:
 
 - Node.js (version 18 or higher).
 - A package manager (npm or yarn).
-- [Polkadot.js browser extension (wallet)](https://polkadot.js.org/extension/){target=\_blank}
+- [Polkadot.js browser extension (wallet)](https://polkadot.js.org/extension/){target=\_blank}.
 - An account with [Westend tokens](https://faucet.polkadot.io/westend){target=\_blank}.
 
 ## Clone the Repository

tutorials/dapps/remark-tutorial.md

@@ -31,6 +31,7 @@ Before proceeding, ensure you meet the following requirements:
 This example will demonstrate how to open a channel between parachain 2500 and parachain 2600, using Rococo Local as the relay chain.
 
 ### Fund Sender Sovereign Account
+
 <!-- This content will be moved to a new page because it is used in multiple places -->
 The [sovereign account](https://github.com/polkadot-fellows/xcm-format/blob/10726875bd3016c5e528c85ed6e82415e4b847d7/README.md?plain=1#L50){target=_blank} for parachain 2500 on the relay chain must be funded so it can take care of any XCM transact fees.
 
@@ -43,16 +44,16 @@ Use [Polkadot.js Apps](https://polkadot.js.org/apps/#/explorer){target=\_blank}
     1. Determine if the parachain is an "up/down" chain (parent or child) or a "sibling" chain:
 
         - Up/down chains use the prefix `0x70617261` (which decodes to `b"para"`).
-
         - Sibling chains use the prefix `0x7369626c` (which decodes to `b"sibl"`).
 
     2. Calculate the u32 scale encoded value of the parachain ID:
+
         - Parachain 2500 would be encoded as `c4090000`.
 
     3. Combine the prefix and parachain ID encoding to form the full sovereign account address:
 
         The sovereign account of parachain 2500 in relay chain will be `0x70617261c4090000000000000000000000000000000000000000000000000000`
-        and the SS58 format of this address is `5Ec4AhPSY2GEE4VoHUVheqv5wwq2C1HMKa7c9fVJ1WKivX1Y`
+        and the SS58 format of this address is `5Ec4AhPSY2GEE4VoHUVheqv5wwq2C1HMKa7c9fVJ1WKivX1Y`.
 
     To perform this conversion, you can also use the **"Para ID" to Address** section in [Substrate Utilities](https://www.shawntabrizi.com/substrate-js-utilities/){target=_blank}.
 
@@ -62,7 +63,7 @@ Use [Polkadot.js Apps](https://polkadot.js.org/apps/#/explorer){target=\_blank}
 
     ![](/images/tutorials/interoperability/xcm-channels/para-to-para/hrmp-para-to-para-1.webp)
 
-2. Construct an `hrmpInitOpenChannel` extrinsic call.
+2. Construct an `hrmpInitOpenChannel` extrinsic call:
 
     1. Select the **`hrmp`** pallet.
     2. Choose the **`hrmpInitOpenChannel`** extrinsic.
@@ -71,7 +72,9 @@ Use [Polkadot.js Apps](https://polkadot.js.org/apps/#/explorer){target=\_blank}
         - **`proposedMaxCapacity`**: Max number of messages that can be pending in the channel at once.
         - **`proposedMaxMessageSize`**: Max message size that could be put into the channel.
     4. Copy the encoded call data.
+
     ![](/images/tutorials/interoperability/xcm-channels/para-to-para/hrmp-para-to-para-2.webp)
+
     The encoded call data for opening a channel with parachain 2600 is `0x3c00280a00000800000000001000`.
 
 ### Craft and Submit the XCM Message from the Sender
@@ -110,7 +113,8 @@ After submitting the XCM message to initiate the HRMP channel opening, you shoul
 
     ![](/images/tutorials/interoperability/xcm-channels/hrmp-channels-1.webp)
 
-2. Query the HRMP open channel requests.
+2. Query the HRMP open channel requests:
+
     1. Select **`hrmp`**.
     2. Choose the **`hrmpOpenChannelRequests`** call.
     3. Click the **+** button to execute the query.
@@ -142,14 +146,16 @@ To fund the account, follow the same process described in the previous section,
     3. Fill in the parameters:
         - **`sender`**: Parachain ID of the requesting chain (in this case, 2500).
     4. Copy the encoded call data.
+
     ![](/images/tutorials/interoperability/xcm-channels/para-to-para/hrmp-para-to-para-5.webp)
-    The encoded call data for accepting a channel with parachain 2500 should be `0x3c01c4090000`
+    
+    The encoded call data for accepting a channel with parachain 2500 should be `0x3c01c4090000`.
 
 ### Craft and Submit the XCM Message from the Receiver
 
 To accept the HRMP channel opening, you need to create and submit an XCM message that includes the encoded `hrmpAcceptOpenChannel` call data from the previous step. This process is similar to the one described in the previous section, [Craft and Submit the XCM Message](#craft-and-submit-the-xcm-message-from-the-sender), with a few key differences:
 
-- Use the encoded call data for `hrmpAcceptOpenChannel` obtained in Step 2 of this section.
+- Use the encoded call data for `hrmpAcceptOpenChannel` obtained in step 2 of this section.
 - In the last XCM instruction (DepositAsset), set the beneficiary to parachain 2600's sovereign account to receive any surplus funds.
 
 To send the XCM message to the relay chain, connect to parachain 2600 in Polkadot.js Apps. Fill in the required parameters as shown in the image below, ensuring that you:
@@ -167,6 +173,7 @@ After submitting the XCM message to accept the HRMP channel opening, verify that
     ![](/images/tutorials/interoperability/xcm-channels/hrmp-channels-1.webp)
 
 2. Query the HRMP channels:
+
     1. Select **`hrmp`**.
     2. Choose the **`hrmpChannels`** call.
     3. Click the **+** button to execute the query.

tutorials/interoperability/xcm-channels/para-to-para.md

@@ -19,9 +19,9 @@ Any parachain can establish a bidirectional channel with a system chain through
 To successfully complete this process, you'll need to have the following in place:
 
 - Access to a blockchain network consisting of:
-    - A relay chain.
-    - A parachain.
-    - An Asset Hub system chain.
+    - A relay chain
+    - A parachain
+    - An Asset Hub system chain
 - A wallet containing enough funds to cover transaction fees on each of the participating chains.
 
 ## Procedure to Establish an HRMP Channel
@@ -42,16 +42,16 @@ Use [Polkadot.js Apps](https://polkadot.js.org/apps/#/explorer){target=\_blank}
     1. Determine if the parachain is an "up/down" chain (parent or child) or a "sibling" chain:
 
         - Up/down chains use the prefix `0x70617261` (which decodes to `b"para"`).
-
         - Sibling chains use the prefix `0x7369626c` (which decodes to `b"sibl"`).
 
     2. Calculate the u32 scale encoded value of the parachain ID:
+
         - Parachain 2500 would be encoded as `c4090000`.
 
     3. Combine the prefix and parachain ID encoding to form the full sovereign account address:
 
         The sovereign account of parachain 2500 in relay chain will be `0x70617261c4090000000000000000000000000000000000000000000000000000`
-        and the SS58 format of this address is `5Ec4AhPSY2GEE4VoHUVheqv5wwq2C1HMKa7c9fVJ1WKivX1Y`
+        and the SS58 format of this address is `5Ec4AhPSY2GEE4VoHUVheqv5wwq2C1HMKa7c9fVJ1WKivX1Y`.
 
     To perform this conversion, you can also use the **"Para ID" to Address** section in [Substrate Utilities](https://www.shawntabrizi.com/substrate-js-utilities/){target=\_blank}.
 
@@ -69,7 +69,8 @@ Use [Polkadot.js Apps](https://polkadot.js.org/apps/#/explorer){target=\_blank}
         - **`target_system_chain`**: Parachain ID of the target system chain (in this case, 1000).
     4. Copy the encoded call data.
     ![](/images/tutorials/interoperability/xcm-channels/para-to-system/hrmp-para-to-system-1.webp)
-    The encoded call data for establishing a channel with system parachain 1000 should be `0x3c0ae8030000`
+
+    The encoded call data for establishing a channel with system parachain 1000 should be `0x3c0ae8030000`.
 
 ### Craft and Submit the XCM Message
 
@@ -78,6 +79,7 @@ Connect to parachain 2500 using Polkadot.js Apps to send the XCM message to the
 1. Insert your previously encoded `establish_channel_with_system` call data into the **`call`** field.
 2. Provide beneficiary details.
 3. Dispatch the XCM message to the relay chain by clicking the **Submit Transaction** button.
+
 ![](/images/tutorials/interoperability/xcm-channels/para-to-system/hrmp-para-to-system-2.webp)
 
 !!! note
@@ -86,15 +88,19 @@ Connect to parachain 2500 using Polkadot.js Apps to send the XCM message to the
 After successfully submitting the XCM message to the relay chain, two HRMP channels should be created, establishing bidirectional communication between parachain 2500 and system chain 1000. To verify this, follow these steps:
 
 1. Using Polkadot.js Apps, connect to the relay chain and navigate to the **Developer** dropdown, then select **Chain state**.
+
     ![](/images/tutorials/interoperability/xcm-channels/hrmp-channels-1.webp)
 
 2. Query the HRMP channels:
+
     1. Select **`hrmp`** from the options.
     2. Choose the **`hrmpChannels`** call.
     3. Click the **+** button to execute the query.
+
     ![](/images/tutorials/interoperability/xcm-channels/para-to-system/hrmp-para-to-system-3.webp)
 
 3. Examine the query results. You should see output similar to the following:
+
     ```json
     --8<-- 'code/tutorials/interoperability/xcm-channels/para-to-system/hrmp-query-output.json'
     ```

tutorials/interoperability/xcm-channels/para-to-system.md

@@ -54,6 +54,7 @@ The following steps outline how to execute a reserve-backed transfer from the Po
 ### From the Relay Chain Perspective
 
 1. Navigate to the Extrinsics page:
+
     1. Click on the **Developer** tab from the top navigation bar.
     2. Select **Extrinsics** from the dropdown.
 
@@ -68,14 +69,14 @@ The following steps outline how to execute a reserve-backed transfer from the Po
     ![](/images/tutorials/interoperability/xcm-transfers/from-relaychain-to-parachain/from-relaychain-to-parachain-04.webp)
 
 4. Fill out the required fields:
-    1. **dest**: Specifies the destination context for the assets. Commonly set to `[Parent, Parachain(..)]` for parachain-to-parachain transfers or `[Parachain(..)]` for relay chain-to-parachain transfers. In this case, since the transfer is from a relay chain to a parachain, the destination ([`Location`](https://paritytech.github.io/xcm-docs/fundamentals/multilocation/index.html){target=\_blank}) is the following.
+
+    1. **dest**: Specifies the destination context for the assets. Commonly set to `[Parent, Parachain(..)]` for parachain-to-parachain transfers or `[Parachain(..)]` for relay chain-to-parachain transfers. In this case, since the transfer is from a relay chain to a parachain, the destination ([`Location`](https://paritytech.github.io/xcm-docs/fundamentals/multilocation/index.html){target=\_blank}) is the following:
 
         ```bash
         { parents: 0, interior: { X1: [{ Parachain: 2006 }] } }
         ```
 
-    2. **beneficiary**: Defines the recipient of the assets within the destination context, typically represented as an `AccountId32` value. This example uses the following account present in the destination chain.
-
+    2. **beneficiary**: Defines the recipient of the assets within the destination context, typically represented as an `AccountId32` value. This example uses the following account present in the destination chain:
 
         ```bash
         X2mE9hCGX771c3zzV6tPa8U2cDz4U4zkqUdmBrQn83M3cm7
@@ -127,7 +128,7 @@ To programmatically execute the reserve-backed asset transfer between the relay
         - `dot` and `astar` are arbitrary names you assign to the chains, allowing you to access their metadata information.
         - The first command uses the well-known Polkadot chain, while the second connects to the Astar chain using its WebSocket endpoint.
 
-4. Create a `index.js` file and insert the following code to configure the clients and handle the asset transfer.
+4. Create a `index.js` file and insert the following code to configure the clients and handle the asset transfer:
 
     ```js
     --8<-- 'code/tutorials/interoperability/xcm-transfers/from-relaychain-to-parachain/reserve-backed-transfer.js'
@@ -136,7 +137,7 @@ To programmatically execute the reserve-backed asset transfer between the relay
     !!! note
         To use this script with real-world blockchains, you'll need to update the WebSocket endpoint to the appropriate one, replace the Alice account with a valid account, and ensure the account has sufficient funds to cover transaction fees.
 
-4. Execute the script.
+4. Execute the script:
 
     ```bash 
     node index.js

tutorials/interoperability/xcm-transfers/from-relaychain-to-parachain.md

@@ -132,7 +132,7 @@ Create a `generateProposal` function that will be responsible for preparing and
 
 Now, you need to implement the following logic:
 
-1. Set up the keyring and use the Alice development account.
+1. Set up the keyring and use the Alice development account:
 
     ```typescript
     --8<-- 'code/tutorials/onchain-governance/fast-track-gov-proposal/test-proposal.ts:40:44'
@@ -141,13 +141,14 @@ Now, you need to implement the following logic:
     !!!note
         When using Chopsticks, this development account is pre-funded to execute all necessary actions.
 
-2. Retrieve the proposal index.
+2. Retrieve the proposal index:
 
     ```typescript
     --8<-- 'code/tutorials/onchain-governance/fast-track-gov-proposal/test-proposal.ts:46:49'
     ```
 
 3. Execute a batch transaction that comprises the following three operations:
+
     1. **`preimage.notePreimage`**: Registers a [preimage](/polkadot-protocol/glossary#preimage){target=\_blank} using the selected call.
 
         !!!note

tutorials/onchain-governance/fast-track-gov-proposal.md

@@ -99,6 +99,7 @@ Launch your parachain locally and start producing blocks:
     ```
 
 3. Verify you can interact with the new pallets using the [Polkadot.js Apps](https://polkadot.js.org/apps/?rpc=ws%3A%2F%2F127.0.0.1%3A9944#/extrinsics){target=\_blank} interface. Navigate to the **Extrinsics** tab and check that you can see both pallets:
+
     - Utility pallet
 
         ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/add-pallets-to-runtime/add-pallets-to-runtime-1.webp)

tutorials/polkadot-sdk/parachains/zero-to-hero/add-pallets-to-runtime.md

@@ -28,6 +28,7 @@ To prepare an account, follow these steps:
     ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet/deploy-to-testnet-1.webp)
 
 2. Navigate to the **Accounts** section:
+
     1. Click on the **Accounts** tab in the top menu.
     2. Select the **Accounts** option from the dropdown menu.
 
@@ -50,12 +51,14 @@ You must reserve a parachain identifier (ID) before registering your parachain o
 To reserve a parachain identifier, follow these steps:
 
 1. Navigate to the **Parachains** section:
+
     1. Click on the **Network** tab in the top menu.
     2. Select the **Parachains** option from the dropdown menu.
 
     ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet/deploy-to-testnet-5.webp)
 
 2. Register a ParaId:
+
     1. Select the **Parathreads** tab.
     2. Click on the **+ ParaId** button.
 
@@ -181,11 +184,11 @@ Once you have the genesis state and runtime, you can now register these with you
 
 1. Go to the [Parachains > Parathreads](https://polkadot.js.org/apps/#/parachains/parathreads){target=\_blank} tab, and select **+ Parathread**.
 
-2. You should see fields to place your runtime Wasm and genesis state respectively, along with the parachain ID. Select your parachain ID, and upload `para-wasm` in the **code** field and `para-state` in the **initial state** field:
+2. You should see fields to place your runtime Wasm and genesis state respectively, along with the parachain ID. Select your parachain ID, and upload `para-wasm` in the **code** field and `para-state` in the **initial state** field.
 
     ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet/deploy-to-testnet-9.webp)
 
-3. Confirm your details and **+ Submit** button, where there should be a new Parathread with your parachain ID and an active **Deregister** button:
+3. Confirm your details and **+ Submit** button, where there should be a new Parathread with your parachain ID and an active **Deregister** button.
 
     ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet/deploy-to-testnet-10.webp)
 

tutorials/polkadot-sdk/parachains/zero-to-hero/deploy-to-testnet.md

@@ -31,28 +31,35 @@ Follow these steps to prepare your environment for pallet benchmarking:
     ```
 
 2. Update your pallet's `Cargo.toml` file in the `pallets/custom-pallet` directory by adding the `runtime-benchmarks` feature flag:
+
     ```toml hl_lines="4" title="Cargo.toml"
     --8<-- 'code/tutorials/polkadot-sdk/parachains/zero-to-hero/pallets/custom-pallet/Cargo.toml:15'
     ```
 
 3. Add your pallet to the runtime's benchmark configuration:
+
     1.  Register your pallet in `runtime/src/benchmarks.rs`:
+
         ```rust hl_lines="11" title="benchmarks.rs"
         --8<-- 'code/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime/src/benchmarks.rs:26:37'
         ```
 
     2. Enable runtime benchmarking for your pallet in `runtime/Cargo.toml`:
+
         ```toml hl_lines="6" title="Cargo.toml"
         --8<-- 'code/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime/Cargo.toml:78:84'
         ```
 
 4. Set up the benchmarking module in your pallet:
+
     1. Create a new `benchmarking.rs` file in your pallet directory:
+    
         ```bash
         touch benchmarking.rs
         ```
 
     2. Add the benchmarking module to your pallet. In the pallet `lib.rs` file add the following:
+
         ```rust hl_lines="9-10" title="lib.rs"
         --8<-- 'code/tutorials/polkadot-sdk/parachains/zero-to-hero/pallets/custom-pallet/src/lib.rs:21:32'
         ```

tutorials/polkadot-sdk/parachains/zero-to-hero/pallet-benchmarking.md

@@ -149,23 +149,23 @@ For more information about runtime versioning, check the [Runtime Upgrades](/dev
 
 ### Build the New Runtime
 
-Navigate to your project root:
+1. Navigate to your project root:
 
-```bash
-cd /path/to/your/parachain-template
-```
+    ```bash
+    cd /path/to/your/parachain-template
+    ```
 
-Build the new runtime:
+2. Build the new runtime:
 
-```bash
-cargo build --release
-```
+    ```bash
+    cargo build --release
+    ```
 
-Verify that you have the proper WASM builds by executing:
+3. Verify that you have the proper WASM builds by executing:
 
-```
-ls -la target/release/wbuild/parachain-template-runtime/
-```
+    ```
+    ls -la target/release/wbuild/parachain-template-runtime/
+    ```
 
 If you can see the following elements, it means that you are ready to submit the runtime upgrade to your running chain:
 
@@ -181,18 +181,21 @@ You can submit a runtime upgrade using the [Sudo pallet](https://paritytech.gith
     ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime-upgrade/runtime-upgrade-02.webp) 
 
 3. Prepare the **sudo** call:
+
     1. Select the **sudo** pallet.
     2. Select the **sudo(call)** extrinsic from the list.
 
         ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime-upgrade/runtime-upgrade-03.webp) 
 
 4. In the **sudo** call:
+
     1. Select the **system** call.
     2. Select **setCode** extrinsic from the list.
 
         ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime-upgrade/runtime-upgrade-04.webp) 
 
 5. For the `code` parameter, click **file upload** and select your WASM runtime file:
+
     - Use `parachain_template_runtime.compact.compressed.wasm` if available (smaller file).
     - Otherwise, use `parachain_template_runtime.wasm`.
 
@@ -212,12 +215,14 @@ After the runtime upgrade extrinsic is included in a block, verify that the upgr
 ### Check Runtime Version
 
 1. In Polkadot.js Apps, navigate to the **Chain State** section:
+
     1. Click the **Developer** dropdown.
     2. Click the **Chain State** option.
 
         ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime-upgrade/runtime-upgrade-07.webp) 
 
 2. Query runtime spec version:
+
     1. Select the **System** pallet.
     2. Select the **lastRuntimeUpgrade()** query.
 
@@ -237,7 +242,7 @@ After the runtime upgrade extrinsic is included in a block, verify that the upgr
 2. Select your custom pallet from the dropdown.
 3. You should now see the new `resetCounter` function available.
 
-    ![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime-upgrade/runtime-upgrade-11.webp) 
+![](/images/tutorials/polkadot-sdk/parachains/zero-to-hero/runtime-upgrade/runtime-upgrade-11.webp) 
 
 Now, you can test the new functionality: