Grammatical updates and minor fixes. (#1194)

* grammatical updates and minor fixes

* Update parachains/launch-a-parachain/set-up-the-parachain-template.md

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

---------

Co-authored-by: Erin Shaben <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: 3 people

.ai/categories/basics.md

@@ -1,53 +1,59 @@
 ---
-title: Transfer Tokens Between Parachains
+title: Transfer Assets Between Parachains
 description: A step-by-step guide to using the ParaSpell XCM SDK to build, verify, and execute a transfer from one Parachain to another.
 url: https://docs.polkadot.com/chain-interactions/send-transactions/interoperability/transfer-assets-parachains/
 ---
 
-# Transfer Tokens Between Parachains
+# Transfer Assets Between Parachains
 
 ## Introduction
 
-This guide walks you through transferring tokens between two parachains using the [ParaSpell XCM SDK](https://paraspell.github.io/docs/){target=\_blank}. This example utilizes [Asset Hub](/polkadot-protocol/architecture/system-chains/asset-hub/){target=\_blank} and the [People Chain](/polkadot-protocol/architecture/system-chains/people/){target=\_blank}. However, the same approach can be applied to transfers between other parachains.
+This guide walks you through transferring tokens between two parachains using the [ParaSpell XCM SDK](/reference/tools/paraspell/){target=\_blank}. This example utilizes [Asset Hub](/polkadot-protocol/architecture/system-chains/asset-hub/){target=\_blank} and the [People Chain](/polkadot-protocol/architecture/system-chains/people/){target=\_blank}. However, the same approach can be applied to transfers between other parachains.
 
 For development purposes, this guide will use the [Polkadot TestNet](/develop/networks/#paseo){target=\_blank}, so the transferred token will be PAS.
 
 In this guide, you will:
 
 - Build an XCM transfer transaction using ParaSpell XCM SDK.
 - Perform a dry run to validate the transfer.
-- Verify the [Existential Deposit (ED)](/polkadot-protocol/glossary/#existential-deposit){target=\_blank} requirement on the destination chain.
+- Verify the [Existential Deposit (ED)](/reference/glossary/#existential-deposit){target=\_blank} requirement on the destination chain.
 - Retrieve information regarding the transfer, along with fee estimates.
 - Submit the transaction.
 
 ### Prerequisites
 
 Before you begin, ensure you have the following:
 
-- Knowledge of the [fundamentals of Polkadot](/polkadot-protocol/parachain-basics/){target=\_blank}.
-- Basic understanding of [XCM](/develop/interoperability/intro-to-xcm/){target=\_blank}.
+- Knowledge of the [fundamentals of Polkadot](/parachains/get-started/){target=\_blank}.
+- Basic understanding of [XCM](/parachains/interoperability/get-started/){target=\_blank}.
 - Basic familiarity with JavaScript or TypeScript.
-- Installed [bun](https://bun.com/docs/installation){target=\_blank}, a JavaScript and TypeScript package manager.
+- Installed [npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm){target=\_blank}, a JavaScript and TypeScript package manager.
 
 ## Initialize Your Project
 
 Create the project folder:
 
 ```bash
-mkdir paraspell-transfer
+mkdir paraspell-transfer && \
 cd paraspell-transfer
 ```
 
 Initialize the JavaScript project:
 
 ```bash
-bun init -y
+npm init -y
+```
+
+Install dev dependencies:
+
+```bash
+npm install --save-dev @types/node@^22.12.0 tsx@^4.20.6 typescript@^5.7.3
 ```
 
 Install the required dependencies:
 
 ```bash
-bun add @paraspell/sdk@11.3.2 polkadot-api@1.17.1 @polkadot-labs/[email protected].25 @polkadot-labs/[email protected].24
+npm install --save @paraspell/sdk@11.12.6 polkadot-api@1.20.0 @polkadot-labs/[email protected].26 @polkadot-labs/[email protected].25
 ```
 
 Now add the following setup code to `index.ts`:
@@ -154,13 +160,13 @@ dryRunTransfer();
 Run the script using the following command:
 
 ```bash
-bun run index.ts
+npx tsx index.ts
 ```
 
 The result of the dry run will look similar to the following example output:
 
 <div id="termynal" data-termynal>
-  <span data-ty="input"><span class="file-path"></span>bun run index.ts</span>
+  <span data-ty="input"><span class="file-path"></span>npx tsx index.ts</span>
   <span data-ty>{
   failureReason: undefined,
   failureChain: undefined,
@@ -313,13 +319,13 @@ verifyED();
 Comment out the `dryRunTransfer()` function so that it is not executed again. Then, execute the `verifyED()` by running the following command:
 
 ```bash
-bun run index.ts
+npx tsx index.ts
 ```
 
 After that, you will get output confirming the ED which will look similar to the following:
 
 <div id="termynal" data-termynal>
-  <span data-ty="input"><span class="file-path"></span>bun run index.ts</span>
+  <span data-ty="input"><span class="file-path"></span>npx tsx index.ts</span>
   <span data-ty>ED verification successful.</span>
 </div>
 ## Get Transfer Info and Fee Estimates
@@ -351,13 +357,13 @@ XcmTransferInfo();
 Comment out the `verifyED()` function so it doesn't execute again. Then, execute the `XcmTransferInfo()` function by running the following command:
 
 ```bash
-bun run index.ts
+npx tsx index.ts
 ```
 
 You will see all the information for your transfer similar to the following example:
 
 <div id="termynal" data-termynal>
-  <span data-ty="input"><span class="file-path"></span>bun run index.ts</span>
+  <span data-ty="input"><span class="file-path"></span>npx tsx index.ts</span>
   <span data-ty>Transfer Info: {
   chain: {
     origin: "AssetHubPaseo",
@@ -420,13 +426,13 @@ transfer();
 Comment out the `XcmTransferInfo()` function so it doesn't execute again. Then, execute the transfer by running the following command: 
 
 ```bash
-bun run index.ts
+npx tsx index.ts
 ```
 
 Your `transfer` function will submit the transaction, and you will get the following output:
 
 <div id="termynal" data-termynal>
-  <span data-ty="input"><span class="file-path"></span>bun run index.ts</span>
+  <span data-ty="input"><span class="file-path"></span>npx tsx index.ts</span>
   <span data-ty>...</span>
   <span data-ty>Built transaction: {
   getPaymentInfo: [AsyncFunction: getPaymentInfo],
@@ -873,4 +879,4 @@ You have now successfully created and sent a cross-chain transfer using the Para
 
 - Read the Docs: Dive deeper into the features of the [ParaSpell XCM SDK](https://paraspell.github.io/docs/sdk/getting-started.html){target=\_blank} documentation.
 
-- Learn about XCM: Understand the underlying protocol by visiting the [Introduction to XCM page](/develop/interoperability/intro-to-xcm/) in the Polkadot Docs.
+- Learn about XCM: Understand the underlying protocol by visiting the [Introduction to XCM page](/parachains/interoperability/get-started/) in the Polkadot Docs.

.ai/categories/dapps.md

@@ -50,9 +50,9 @@ Any language that can compile to PolkaVM bytecode and utilize `pallet-revive`'s
 
 ### Key Benefits
 
-- **Unified Platform**: Deploys both PolkaVM-optimized and EVM-compatible contracts using a single pallet.
+- **Unified platform**: Deploys both PolkaVM-optimized and EVM-compatible contracts using a single pallet.
 - **Performance**: PolkaVM execution provides improved performance compared to the traditional EVM, leveraging the [RISC-V](https://en.wikipedia.org/wiki/RISC-V){target=\_blank} architecture to map instructions to the CPU and requires little transpiling.
-- **Ethereum Compatibility**: Supports full integration with Ethereum tooling via RPC adapter.
+- **Ethereum compatibility**: Supports full integration with Ethereum tooling via RPC adapter.
 
 ### Implementation Examples
 
@@ -70,7 +70,7 @@ Frontier offers flexible integration depending on your compatibility needs:
 
 For basic EVM support using Polkadot SDK native APIs:
 
-- **[`pallet-evm`](https://github.com/polkadot-evm/frontier/tree/master/frame/evm){target=\_blank}**: Provides the core EVM execution environment
+- **[`pallet-evm`](https://github.com/polkadot-evm/frontier/tree/master/frame/evm){target=\_blank}**: Provides the core EVM execution environment.
 
 This configuration allows EVM contract execution but requires using Polkadot SDK-specific APIs for interaction.
 
@@ -84,20 +84,20 @@ For complete Ethereum ecosystem integration with Ethereum RPC support:
 
 ### Key Benefits
 
-- **Ethereum tooling compatibility**: Full compatibility with MetaMask, Hardhat, Remix, Truffle, and other Ethereum development tools
-- **Minimal-friction migration**: Deployment of existing Ethereum dApps with minimal or no modifications
-- **Native Ethereum formats**: Support for Ethereum transaction formats, signatures, and gas mechanics
-- **Block emulation**: Ethereum-style block structure within Substrate's block production
+- **Ethereum tooling compatibility**: Full compatibility with MetaMask, Hardhat, Remix, Foundry, and other Ethereum development tools.
+- **Minimal-friction migration**: Deployment of existing Ethereum dApps with minimal or no modifications.
+- **Native Ethereum formats**: Support for Ethereum transaction formats, signatures, and gas mechanics.
+- **Block emulation**: Ethereum-style block structure within Substrate's block production.
 
 ### Implementation Examples
 
 Production implementations demonstrate Frontier's capabilities:
 
-- **Moonbeam**: See their implementation of [`pallet-evm`](https://github.com/moonbeam-foundation/moonbeam/blob/9e2ddbc9ae8bf65f11701e7ccde50075e5fe2790/runtime/moonbeam/src/lib.rs#L532){target=\_blank} and [`pallet-ethereum`](https://github.com/moonbeam-foundation/moonbeam/blob/9e2ddbc9ae8bf65f11701e7ccde50075e5fe2790/runtime/moonbeam/src/lib.rs#L698){target=\_blank}
+- **Moonbeam**: See their implementation of [`pallet-evm`](https://github.com/moonbeam-foundation/moonbeam/blob/9e2ddbc9ae8bf65f11701e7ccde50075e5fe2790/runtime/moonbeam/src/lib.rs#L532){target=\_blank} and [`pallet-ethereum`](https://github.com/moonbeam-foundation/moonbeam/blob/9e2ddbc9ae8bf65f11701e7ccde50075e5fe2790/runtime/moonbeam/src/lib.rs#L698){target=\_blank}.
 
 ## pallet-contracts (Legacy)
 
-[`pallet-contracts`](https://docs.rs/pallet-contracts/latest/pallet_contracts/index.html#contracts-pallet){target=\_blank} is the original Wasm-based smart contract pallet for Polkadot SDK chains. While still functional, it's considered legacy as development efforts have shifted to pallet-revive.
+[`pallet-contracts`](https://docs.rs/pallet-contracts/latest/pallet_contracts/index.html#contracts-pallet){target=\_blank} is the original Wasm-based smart contract pallet for Polkadot SDK chains. While still functional, it's considered legacy as development efforts have shifted to `pallet-revive`.
 
 ### Implementation Example