add Polkadot Rust Docs references; formatting

Author: brunopgalvao

develop/toolkit/integrations/transaction-construction.md

@@ -17,55 +17,38 @@ For further reading, refer to [blocks, transactions, and fees](/polkadot-protoco
 
 Polkadot has some basic transaction information that is common to all transactions.
 
-- Address: The [SS58-encoded address](/polkadot-protocol/glossary/#ss58-address-format){target=\_blank} of the sending account.
-- Block Hash: The hash of the [checkpoint](/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/#transaction-mortality){target=\_blank} block.
-- Block Number: The number of the checkpoint block.
-- Genesis Hash: The genesis hash of the chain.
-- Metadata: The [SCALE-encoded metadata](polkadot-protocol/parachain-basics/data-encoding/){target=\_blank} for the runtime when submitted.
-- Nonce: The nonce for this transaction.
-- Spec Version: The current spec version for the runtime.
-- Transaction Version: The current version for transaction format.
-- Tip: Optional, the [tip](https://docs.polkadot.com/polkadot-protocol/parachain-basics/blocks-transactions-fees/fees/#how-fees-are-calculated){target=\_blank} to increase transaction priority.
-- Mode: The flag indicating whether to verify the metadata hash or not.
-- Era Period: Optional, the number of blocks after the checkpoint for which a transaction is valid.
-  If zero, the transaction is [immortal](/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/#transaction-mortality){target=\_blank}
-- MetadataHash: Optional, the metadata hash which should match the RUNTIME_METADATA_HASH environment
-  variable.
+- **Address**: The [SS58-encoded address](/polkadot-protocol/glossary/#ss58-address-format){target=\_blank} of the sending account.
+- **Block Hash**: The hash of the [checkpoint](/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/#transaction-mortality){target=\_blank} block.
+- **Block Number**: The number of the checkpoint block.
+- **Genesis Hash**: The genesis hash of the chain.
+- **Metadata**: The [SCALE-encoded metadata](polkadot-protocol/parachain-basics/data-encoding/){target=\_blank} for the runtime when submitted.
+- **Nonce**: The nonce for this transaction.
+- **Spec Version**: The current spec version for the runtime.
+- **Transaction Version**: The current version for transaction format.
+- **Tip**: Optional, the [tip](https://docs.polkadot.com/polkadot-protocol/parachain-basics/blocks-transactions-fees/fees/#how-fees-are-calculated){target=\_blank} to increase transaction priority.
+- **Mode**: The flag indicating whether to verify the metadata hash or not.
+- **Era Period**: Optional, the number of blocks after the checkpoint for which a transaction is valid. If zero, the transaction is [immortal](/polkadot-protocol/parachain-basics/blocks-transactions-fees/transactions/#transaction-mortality){target=\_blank}
+- **MetadataHash**: Optional, the metadata hash which should match the [`RUNTIME_METADATA_HASH`](https://paritytech.github.io/polkadot-sdk/master/frame_metadata_hash_extension/struct.CheckMetadataHash.html){target=\_blank} environment variable.
 
 !!!warning
-    There are risks to making a transaction immortal. If an account is reaped and a user re-funds the 
-    account, then they could replay an immortal transaction. Always default to using a mortal extrinsic.
+    There are risks to making a transaction immortal. If an account is reaped and a user re-funds the account, then they could replay an immortal transaction. Always default to using a mortal extrinsic.
 
-The nonce queried from the System module does not account for pending transactions. You must track 
-and increment the nonce manually if you want to submit multiple valid transactions at the same time.
+The nonce queried from the System module does not account for pending transactions. You must track and increment the nonce manually if you want to submit multiple valid transactions at the same time.
 
-Each transaction will have its own (or no) parameters to add. For example, the [`transferKeepAlive`](https://paritytech.github.io/polkadot-sdk/master/pallet_balances/pallet/enum.Call.html#variant.transfer_keep_alive){target=\_blank} 
-function from the Balances pallet will take:
+Each transaction will have its own (or no) parameters to add. For example, the [`transferKeepAlive`](https://paritytech.github.io/polkadot-sdk/master/pallet_balances/pallet/enum.Call.html#variant.transfer_keep_alive){target=\_blank}  function from the [Balances pallet](https://paritytech.github.io/polkadot-sdk/master/pallet_balances/index.html){target=\_blank} will take:
 
 - `dest`: Destination address
 - `#[compact] value`: Number of tokens (compact encoding)
 
-Refer to [the protocol specifications](https://spec.polkadot.network/id-extrinsics){target=\_blank}, for the
-concrete specifications and types to build a transaction.
+Refer to [the protocol specifications](https://spec.polkadot.network/id-extrinsics){target=\_blank}, for the concrete specifications and types to build a transaction.
 
 **Mode and MetadataHash**
 
-The mode and metadataHash fields were introduced in transaction construction to support the optional
-[`CheckMetadataHash` Signed Extension](https://github.com/polkadot-fellows/RFCs/blob/main/text/0078-merkleized-metadata.md){target=\_blank}.
-This enables trustless metadata verification by allowing the chain to verify the correctness of the
-metadata used without the need of a trusted party. This functionality was included in
-[v1.2.5](https://github.com/polkadot-fellows/runtimes/releases/tag/v1.2.5){target=\_blank} runtime release by the
-Fellowship. A user may opt out of this functionality by setting the mode to `0`. When the mode is 00,
-the `metadataHash` field is empty/None.
+The [`mode`](https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/guides/enable_metadata_hash/index.html){target=\_blank} and [`metadataHash`](https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/guides/enable_metadata_hash/index.html){target=\_blank} fields were introduced in transaction construction to support the optional [`CheckMetadataHash` Signed Extension](https://github.com/polkadot-fellows/RFCs/blob/main/text/0078-merkleized-metadata.md){target=\_blank}. This enables trustless metadata verification by allowing the chain to verify the correctness of the metadata used without the need of a trusted party. This functionality was included in [v1.2.5](https://github.com/polkadot-fellows/runtimes/releases/tag/v1.2.5){target=\_blank} runtime release by the [Fellowship](https://github.com/polkadot-fellows/manifesto){target=\_blank}. A user may opt out of this functionality by setting the `mode` to `0`. When the mode is 00, the [`metadataHash`](https://paritytech.github.io/polkadot-sdk/master/polkadot_sdk_docs/guides/enable_metadata_hash/index.html){target=\_blank} field is empty/`None`.
 
 **Serialized transactions and metadata**
 
-Before being submitted, transactions are serialized. Serialized transactions are hex encoded
-SCALE-encoded bytes. The relay chain runtimes are upgradable and therefore any interfaces are
-subject to change, the metadata allows developers to structure any extrinsics or storage entries
-accordingly. The metadata provides you with all of the information required to know how to construct
-the serialized call data specific to your transaction. You can read more about the metadata, its
-format and how to get it in the [Subxt documentation](/polkadot-protocol/parachain-basics/chain-data/#use-subxt){target=\_blank}.
+Before being submitted, transactions are serialized. Serialized transactions are hex encoded SCALE-encoded bytes. The relay chain runtimes are upgradable and therefore any interfaces are subject to change, the metadata allows developers to structure any extrinsics or storage entries accordingly. The metadata provides you with all of the information required to know how to construct the serialized call data specific to your transaction. You can read more about the metadata, its format and how to get it in the [Subxt documentation](/polkadot-protocol/parachain-basics/chain-data/#use-subxt){target=\_blank}.
 
 **Transaction Flow**
 
@@ -81,23 +64,18 @@ Parity provides several tools to help perform these steps.
 
 ## Polkadot-JS Tools
 
-[Polkadot-JS Tools](https://github.com/polkadot-js/tools){target=\_blank} contains a set of command line tools for
-interacting with a Polkadot SDK client, including one called "Signer CLI" to create, sign, and
-broadcast transactions.
+[Polkadot-JS Tools](https://github.com/polkadot-js/tools){target=\_blank} contains a set of command line tools for interacting with a Polkadot SDK client, including one called "Signer CLI" to create, sign, and broadcast transactions.
 
-This example will use the `signer submit` command, which will create and submit the transaction. The
-`signer sendOffline` command has the exact same API, but will not broadcast the transaction.
-`submit` and `sendOffline` must be connected to a node to fetch the current metadata and construct a
-valid transaction.
+This example will use the `signer submit` command, which will create and submit the transaction. The `signer sendOffline` command has the exact same API, but will not broadcast the transaction. `submit` and `sendOffline` must be connected to a node to fetch the current metadata and construct a valid transaction.
 
-Start by installing the Signer CLI:
+Start by installing the Signer CLI.
 
 ```bash
 npm install -g @polkadot/signer-cli
 ```
 
 To create a transaction, you need to connect to a chain, enabling the creation of a transaction using the chain's metadata. 
-Here is the format for `submit` or `sendOffline`:
+Here is the format for `submit` or `sendOffline`.
 
 ```bash
 polkadot-js-signer <submit|sendOffline> --account <from-account-ss58> --ws <endpoint> <module.method> [param1] [...] [paramX]
@@ -138,26 +116,26 @@ Let's say you want to send 1 WND from `5F4c8mNz6schf2WMXQZiz1eyR1GGxrMf2coXpAn8m
 First fund the sending account. You can use the [Westend Faucet](https://faucet.polkadot.io/westend) for that.
 Request some tokens for `5F4c8mNz6schf2WMXQZiz1eyR1GGxrMf2coXpAn8mNjxyzp2`.
 
-Next call submit to create the transaction and which will give you the payload to sign:
+Next call submit to create the transaction and which will give you the payload to sign.
 
 ```bash
 polkadot-js-signer submit --account 5F4c8mNz6schf2WMXQZiz1eyR1GGxrMf2coXpAn8mNjxyzp2 --ws wss://asset-hub-westend-rpc.n.dwellir.com balances.transferKeepAlive 5FnudgwK8xJvmujsXXP35pF2xwskhHQzBSRM8KZhXjnEz5gD 1000000000000
 ```
 
-This will return a payload to sign and an input waiting for a signature. Something like this:
+This will return a payload to sign and an input waiting for a signature.
 
 ```
 Payload: 0x040300ff4a83f1...a8239139ff3ff7c3f6
 Signature>
 ```
 
-Take this payload and use your normal signing environment (e.g. air gapped machine, VM, etc.). In a separate tab in your terminal, sign the payload:
+Take this payload and use your normal signing environment (e.g. air gapped machine, VM, etc.). In a separate tab in your terminal, sign the payload.
 
 ```bash
 polkadot-js-signer sign --account 5F4c8mNz6schf2WMXQZiz1eyR1GGxrMf2coXpAn8mNjxyzp2 --seed "south ladder exile ... grape rival settle coil" --type sr25519 0x040300ff4a83f1...a8239139ff3ff7c3f6
 ```
 
-This will output the signature of the transaction:
+This will output the signature of the transaction.
 ```
 Signature: 0xe6facf194a8e...413ce3155c2d1240b
 ```
@@ -350,14 +328,9 @@ You will get useful output in the terminal with details like the events that wer
     polkadot-js-signer submit --tx <signedTransaction> --ws <endpoint>
     ```
 
-## TxWrapper
+## Txwrapper
 
-If you do not want to use the CLI for signing operations, Parity provides an SDK called
-[TxWrapper Core](https://github.com/paritytech/txwrapper-core){target=\_blank} to generate and sign transactions
-offline. For Polkadot, Kusama, and select parachains, use the `txwrapper-polkadot` package. Other
-Substrate-based chains will have their own `txwrapper-{chain}` implementations. See the
-[examples](https://github.com/paritytech/txwrapper-core/blob/main/packages/txwrapper-examples/README.md){target=\_blank}
-for a guide.
+If you do not want to use the CLI for signing operations, Parity provides an SDK called [txwrapper-core](https://github.com/paritytech/txwrapper-core){target=\_blank} to generate and sign transactions offline. For Polkadot, Kusama, and select parachains, use the `txwrapper-polkadot` package. Other Substrate-based chains will have their own `txwrapper-{chain}` implementations. See the [examples](https://github.com/paritytech/txwrapper-core/blob/main/packages/txwrapper-examples/README.md){target=\_blank} for a guide.
 
 ### Creating a Transaction, Signing, and Submitting
 
@@ -369,9 +342,9 @@ npx @acala-network/chopsticks --config=polkadot -p 9944
 ```
 You should get a Polkadot network running on port 9944.
 
-Next we will use the [`TxWrapper example script`](https://github.com/paritytech/txwrapper-core/blob/main/packages/txwrapper-examples/polkadot/src/polkadot.ts){target=\_blank} to create and sign transactions.
+Next we will use the [`txwrapper example script`](https://github.com/paritytech/txwrapper-core/blob/main/packages/txwrapper-examples/polkadot/src/polkadot.ts){target=\_blank} to create and sign transactions.
 
-For this you will need the [`TxWrapper`](https://github.com/paritytech/txwrapper-core){target=\_blank} library. Let's clone [`TxWrapper`](https://github.com/paritytech/txwrapper-core){target=\_blank}:
+For this you will need the [`txwrapper`](https://github.com/paritytech/txwrapper-core){target=\_blank} library. Let's clone [`txwrapper`](https://github.com/paritytech/txwrapper-core){target=\_blank}:
 
 ```
 git clone https://github.com/paritytech/txwrapper-core
@@ -380,7 +353,7 @@ yarn install && yarn build
 cd packages/txwrapper-examples
 ```
 
-Build and run the [`TxWrapper Polkadot example script`](https://github.com/paritytech/txwrapper-core/blob/main/packages/txwrapper-examples/polkadot/src/polkadot.ts){target=\_blank}:
+Build and run the [`txwrapper Polkadot example script`](https://github.com/paritytech/txwrapper-core/blob/main/packages/txwrapper-examples/polkadot/src/polkadot.ts){target=\_blank}:
 ```
 yarn run build
 yarn run polkadot
@@ -412,8 +385,8 @@ Decoded Transaction
   Amount: "10000000000"
 ```
 
-The [`TxWrapper example script`](https://github.com/paritytech/txwrapper-core/blob/main/packages/txwrapper-examples/polkadot/src/polkadot.ts){target=\_blank} includes several reference examples.
+The [`txwrapper example script`](https://github.com/paritytech/txwrapper-core/blob/main/packages/txwrapper-examples/polkadot/src/polkadot.ts){target=\_blank} includes several reference examples.
 
 ## Additional Libraries for Submitting a Transaction
 
-Other than Polkadot JS Tools and TXWrapper, there are several other libraries that can also be used to submit a signed payload such as the [Sidecar API](/develop/toolkit/api-libraries/sidecar/#sidecar-api){target=\_blank} or using RPC calls with `author_submitExtrinsic` or `author_submitAndWatchExtrinsic`, the latter of which will subscribe you to events to be notified as a transaction gets validated and included in the chain. You can see all the available libraries in the [API Libraries](/develop/toolkit/api-libraries/) section of the Polkadot Docs.
+Other than Polkadot JS Tools and txwrapper, there are several other libraries that can also be used to submit a signed payload such as the [Sidecar API](/develop/toolkit/api-libraries/sidecar/#sidecar-api){target=\_blank} or using RPC calls with [`author_submitExtrinsic`](https://paritytech.github.io/polkadot-sdk/master/sc_rpc/author/trait.AuthorApiServer.html#tymethod.submit_extrinsic){target=\_blank} or [`author_submitAndWatchExtrinsic`](https://github.com/paritytech/polkadot-sdk/blob/0ae5c5bbd96a600aed81358339be2f16bade4a81/substrate/client/rpc-api/src/author/mod.rs#L69-L78){target=\_blank}, the latter of which will subscribe you to events to be notified as a transaction gets validated and included in the chain. You can see all the available libraries in the [API Libraries](/develop/toolkit/api-libraries/) section of the Polkadot Docs.