Fix lists

docs/aptos-tooling.mdx

@@ -1,33 +1,26 @@
 ---
 title: "Aptos tooling"
 ---
 
 ## Martian wallet
 
 You can set your [Martian wallet](https://martianwallet.xyz/) to interact through your Aptos nodes deployed with Chainstack.
-<Steps>
-  <Step>
-    Open your Martian wallet and click the network selector.
-  </Step>
-  <Step>
-    In the network selector, click **ADD CUSTOM NETWORK**.
-  </Step>
-  <Step>
-    In the **Enter Node Url** field, enter the endpoint. See also [node access details](/docs/manage-your-node#view-node-access-and-credentials).
-  </Step>
-  <Step>
-    In the **Enter Faucet Url** field, enter the [Aptos testnet faucet](https://aptoslabs.com/testnet-faucet) URL.
-  </Step>
-  <Step>
-    Click **ADD NETWORK**.
-  </Step>
-</Steps>
+
+1. Open your Martian wallet and click the network selector.
+
+2. In the network selector, click **ADD CUSTOM NETWORK**.
+
+3. In the **Enter Node Url** field, enter the endpoint. See also [node access details](/docs/manage-your-node#view-node-access-and-credentials).
+
+4. In the **Enter Faucet Url** field, enter the [Aptos testnet faucet](https://aptoslabs.com/testnet-faucet) URL.
+
+5. Click **ADD NETWORK**.
 
 ## REST API
 
 Interact with your Aptos node using the [Aptos Node API](https://fullnode.devnet.aptoslabs.com/v1/spec#/).
 
 Use your Chainstack Aptos REST endpoint. Example to get block information by block height:
 
 <CodeGroup>
   ```bash cURL

docs/aptos-tutorial-publish-a-module-to-save-and-retrieve-a-message-on-aptos.mdx

@@ -1,74 +1,48 @@
 ---
 title: "Aptos: Publish a module to save & retrieve a message on-chain"
 ---
 
 **TLDR:**
 * Aptos uses the Move language and “published” modules in place of traditional smart contracts.
 * This tutorial shows you how to set up an Aptos node, initialize a Move project, and publish a simple module that stores a string on-chain.
 * You’ll run through the basics of module creation, compilation, testing, and then sending transactions to set and retrieve data.
 * Use the Aptos CLI for everything from local testing to publishing, and wrap up by querying the on-chain data with Aptos’ REST API.
 
 ## Main article
 
 Aptos uses its own terminology for widely-known Web3 entities. Smart contracts are called Modules and are written in the [Move language](https://move-language.github.io/move/). Modules are also not deployed but *published* on the Aptos chain.
 
 The objective of this tutorial is to familiarize you with the Aptos network, the Move language and modules written in it. In the end of this tutorial, you will be able to publish, test, and interact with Move modules in Aptos.
 
 Specifically, in this tutorial, you will:
 
 * Initialize an Aptos project using the Aptos CLI.
 * Publish a module on the Aptos testnet.
 * Interact with the module to save a message.
 * Use the Aptos REST API to retrieve the message.
 
 ## Prerequisites
 
 * [Chainstack account ](https://console.chainstack.com/)to deploy an Aptos node.
 * [Martian Aptos wallet](https://martianwallet.xyz/) to receive testnet Aptos token (APT).
 * [Aptos CLI](https://github.com/aptos-labs/aptos-core) to compile, publish, and interact with the Move module.
 
 ## Overview
 
 To get from zero to publishing your string via the module to Aptos testnet, do the following:
 
-<Steps>
-  <Step>
-  With Chainstack, create a <Tooltip tip="A public chain project- a project to join public networks">public chain project</Tooltip>.
-  </Step>
-  <Step>
-  With Chainstack, join Aptos testnet.
-  </Step>
-  <Step>
-  With Chainstack, access your Aptos node credentials.
-  </Step>
-  <Step>
-  Set up your Martian wallet to work through the Chainstack Aptos node.
-  </Step>
-  <Step>
-  Fund your account through the [Aptos testnet faucet](https://aptoslabs.com/testnet-faucet).
-  </Step>
-  <Step>
-  Install the [Aptos CLI](https://aptos.dev/tools/aptos-cli/install-cli/).
-  </Step>
-  <Step>
-  Create a Move project.
-  </Step>
-  <Step>
-  Create and configure your Aptos project.
-  </Step>
-  <Step>
-    Create a module in the Move language.
-  </Step>
-  <Step>
-  Compile and test the Move module.
-  </Step>
-  <Step>
-  Publish the Move module.
-  </Step>
-  <Step>
-  Save and retrieve a message on the Aptos chain.
-  </Step>
-</Steps>
+1. With Chainstack, create a <Tooltip tip="A public chain project- a project to join public networks">public chain project</Tooltip>.
+2. With Chainstack, join Aptos testnet.
+3. With Chainstack, access your Aptos node credentials.
+4. Set up your Martian wallet to work through the Chainstack Aptos node.
+5. Fund your account through the [Aptos testnet faucet](https://aptoslabs.com/testnet-faucet).
+6. Install the [Aptos CLI](https://aptos.dev/tools/aptos-cli/install-cli/).
+7. Create a Move project.
+8. Create and configure your Aptos project.
+9. Create a module in the Move language.
+10. Compile and test the Move module.
+11. Publish the Move module.
+12. Save and retrieve a message on the Aptos chain.
 
 ## Step-by-step
 
@@ -76,7 +50,7 @@
 
 See [Create a project](/docs/manage-your-project#create-a-project).
 
 ### Join the Aptos testnet
 
 See [Join a public network](/docs/manage-your-networks#join-a-public-network).
 
@@ -90,11 +64,11 @@
 
 ### Fund your account
 
 Your account needs to pay fees in testnet APT to publish the module and interact with it. Fund your account with the [Aptos testnet faucet](https://aptoslabs.com/testnet-faucet).
 
 ### Install the Aptos CLI
 
 You need the Aptos CLI to interact with your Move module. Set up the [Aptos CLI](https://aptos.dev/tools/aptos-cli/install-cli/).
 
 ### Create a Move project
 
@@ -102,7 +76,7 @@
 
    <CodeGroup>
      ```bash Shell
      aptos move init --name save-message
      ```
    </CodeGroup>
 
@@ -112,8 +86,8 @@
 
 2. Open your `Move.toml` file and edit it to add `[addresses]` and `[dev-addresses]`, where:
 
    * `dev = "_"` — your default Aptos account.
    * `dev = "0xC0FFEE"` — an alternative Aptos account for tests.
 
    Example:
 
@@ -132,7 +106,7 @@
      [dependencies.AptosFramework]
      git = 'https://github.com/aptos-labs/aptos-core.git'
      rev = 'main'
      subdir = 'aptos-move/framework/aptos-framework'
      ```
    </CodeGroup>
 
@@ -140,11 +114,11 @@
      Note that packages have one-time names. If you want to re-publish the package, you must change its name.
    </Warning>
 
 ### Create and configure an Aptos project
 
 1. In your project directory, run `aptos init > custom`. This will start a configuration process, during which you need to set up your Chainstack endpoint and Martian wallet private key. Adding the private key will retrieve your Aptos public address automatically.
 
 2. Add your [Aptos node endpoint](/docs/manage-your-node#view-node-access-and-credentials) deployed with Chainstack.
 
 3. At the faucet URL request, type `skip` since you have already funded your account on the previous step.
 
@@ -152,7 +126,7 @@
 
    <CodeGroup>
      ```bash Shell
      Aptos CLI is now set up for account ...4474 as profile default!  Run `aptos --help` for more information about commands
      {
        "Result": "Success"
      }
@@ -177,7 +151,7 @@
   //:!:>resource
       struct MessageHolder has key {
           message: string::String,
           message_change_events: event::EventHandle<MessageChangeEvent>,
       }
   //<:!:resource
 
@@ -322,13 +296,13 @@
 
 ## Conclusion
 
 This tutorial guided you through the basics of creating, publishing, and testing a simple module that saves a string on the Aptos chain.
 
 ### About the author
 
 <CardGroup>
   <Card title="Davide Zambiasi" img="/images/docs/profile_images/1533079085001363457/1VvXp1m0_400x400.jpg">
     <Icon icon="code"  iconType="solid"/>Developer Advocate @ Chainstack
 
     <Icon icon="screwdriver-wrench"  iconType="solid"/> BUIDLs on EVM, The Graph protocol, and Starknet
 

docs/arbitrum-tooling.mdx

@@ -1,5 +1,5 @@
 ---
 title: "Arbitrum tooling"
 ---
 
 ## MetaMask
@@ -8,14 +8,10 @@
 
 ## Hardhat
 
 Configure [Hardhat](https://hardhat.org/) to deploy contracts and interact through your Arbitrum nodes.
 
-<Steps>
-  <Step>
-    Install [Hardhat](https://hardhat.org/) and create a project.
-  </Step>
-  <Step>
-   Create a new environment in `hardhat.config.js`:
+1. Install [Hardhat](https://hardhat.org/) and create a project.
+2. Create a new environment in `hardhat.config.js`:
 
    <CodeGroup>
      ```javascript Javascript
@@ -24,7 +20,7 @@
      module.exports = {
        solidity: "0.7.3",
        networks: {
          chainstack: {
              url: "YOUR_CHAINSTACK_ENDPOINT",
              accounts: ["YOUR_PRIVATE_KEY"]
          },
@@ -37,41 +33,25 @@
 
    * YOUR\_CHAINSTACK\_ENDPOINT — your node HTTPS or WSS endpoint protected either with the key or password. See [node access details](/docs/manage-your-node#view-node-access-and-credentials).
    * YOUR\_PRIVATE\_KEY — the private key of the account that you use to deploy the contract
-  </Step>
-  <Step>
-    Run `npx hardhat run scripts/deploy.js --network chainstack` and Hardhat will deploy using Chainstack.
-  </Step>
-</Steps>
+3. Run `npx hardhat run scripts/deploy.js --network chainstack` and Hardhat will deploy using Chainstack.
 
 See also [Forking EVM-compatible mainnet with Hardhat](https://support.chainstack.com/hc/en-us/articles/900004242406).
 
 ## Remix IDE
 
 To make Remix IDE interact with the network through a Chainstack node:
 
-<Steps>
-  <Step>
-    Get [MetaMask](https://metamask.io/) and set it to interact through a Chainstack node. See [Interacting through MetaMask](/docs/arbitrum-tooling#metamask).
-  </Step>
-  <Step>
-    In Remix IDE, navigate to the **Deploy** tab. Select **Injected Provider - MetaMask** in **Environment**.
-  </Step>
-</Steps>
+1. Get [MetaMask](https://metamask.io/) and set it to interact through a Chainstack node. See [Interacting through MetaMask](/docs/arbitrum-tooling#metamask).
+2. In Remix IDE, navigate to the **Deploy** tab. Select **Injected Provider - MetaMask** in **Environment**.
 
 This will engage MetaMask and make Remix IDE interact with the network through a Chainstack node.
 
 ## web3.js
 
 Build DApps using [web3.js](https://github.com/ethereum/web3.js/) and Arbitrum nodes deployed with Chainstack.
 
-<Steps>
-  <Step>
-    Install [web3.js](https://web3js.readthedocs.io/).
-  </Step>
-  <Step>
-    Connect over HTTP or WebSocket.
-  </Step>
-</Steps>
+1. Install [web3.js](https://web3js.readthedocs.io/).
+2. Connect over HTTP or WebSocket.
 
 ### HTTP
 
@@ -107,16 +87,10 @@
 
 ## web3.py
 
 Build DApps using [web3.py](https://github.com/ethereum/web3.py) and Arbitrum nodes deployed with Chainstack.
 
-<Steps>
-  <Step>
-    Install [web3.py](https://web3py.readthedocs.io/).
-  </Step>
-  <Step>
-    Connect over HTTP or WebSocket. See also [EVM node connection: HTTP vs WebSocket](https://support.chainstack.com/hc/en-us/articles/900002187586-Ethereum-node-connection-HTTP-vs-WebSocket).
-  </Step>
-</Steps>
+1. Install [web3.py](https://web3py.readthedocs.io/).
+2. Connect over HTTP or WebSocket. See also [EVM node connection: HTTP vs WebSocket](https://support.chainstack.com/hc/en-us/articles/900002187586-Ethereum-node-connection-HTTP-vs-WebSocket).
 
 ### HTTP
 
@@ -141,7 +115,7 @@
 where
 
 * YOUR\_CHAINSTACK\_ENDPOINT — your node HTTPS endpoint protected either with the key or password
 * HOSTNAME — your node HTTPS endpoint hostname
 * USERNAME — your node access username (for password-protected endpoints)
 * PASSWORD — your node access password (for password-protected endpoints)
 
@@ -170,7 +144,7 @@
 where
 
 * YOUR\_CHAINSTACK\_ENDPOINT — your node WSS endpoint protected either with the key or password
 * HOSTNAME — your node WSS endpoint hostname
 * USERNAME — your node access username (for password-protected endpoints)
 * PASSWORD — your node access password (for password-protected endpoints)
 
@@ -178,14 +152,10 @@
 
 ## web3.php
 
 Build DApps using [web3.php](https://github.com/web3p/web3.php) and Arbitrum nodes deployed with Chainstack.
 
-<Steps>
-  <Step>
-    Install [web3.php](https://github.com/web3p/web3.php).
-  </Step>
-  <Step>
-    Connect over HTTP:
+1. Install [web3.php](https://github.com/web3p/web3.php).
+2. Connect over HTTP:
 
    <CodeGroup>
      ```php Php
@@ -203,9 +173,7 @@
    </CodeGroup>
 
    where YOUR\_CHAINSTACK\_ENDPOINT is your node HTTPS endpoint protected either with the key or password
-  </Step>
-  <Step>
-    Use [JSON-RPC methods](https://eth.wiki/json-rpc/API) to interact with the node.
+3. Use [JSON-RPC methods](https://eth.wiki/json-rpc/API) to interact with the node.
 
    Example to get the latest block number:
 
@@ -221,7 +189,7 @@
 
      $web3 = new Web3(new HttpProvider(new HttpRequestManager("YOUR_CHAINSTACK_ENDPOINT", 5)));
 
      $eth = $web3->eth;
 
      $eth->blockNumber(function ($err, $data) {
           print "$data \n";
@@ -229,12 +197,10 @@
      ?>
      ```
    </CodeGroup>
-  </Step>
-</Steps>
 
 ## web3j
 
 Build DApps using [web3j](https://github.com/web3j/web3j) and Arbitrum nodes deployed with Chainstack.
 
 
 Use the `HttpService` object to connect to your node endpoint.
@@ -308,14 +274,8 @@
 
 Build DApps using [ethers.js](https://github.com/ethers-io/ethers.js/) and Arbitrum nodes deployed with Chainstack.
 
-<Steps>
-  <Step>
-    Install [ethers.js](https://www.npmjs.com/package/ethers).
-  </Step>
-  <Step>
-    Connect over HTTP or WebSocket. See also [EVM node connection: HTTP vs WebSocket](https://support.chainstack.com/hc/en-us/articles/900002187586-Ethereum-node-connection-HTTP-vs-WebSocket).
-  </Step>
-</Steps>
+1. Install [ethers.js](https://www.npmjs.com/package/ethers).
+2. Connect over HTTP or WebSocket. See also [EVM node connection: HTTP vs WebSocket](https://support.chainstack.com/hc/en-us/articles/900002187586-Ethereum-node-connection-HTTP-vs-WebSocket).
 
 ### HTTP
 
@@ -355,10 +315,10 @@
 
 * PASSWORD — your node access password (for password-protected endpoints)
 
 * NETWORK\_ID — Arbitrum network ID:
 
   * Mainnet: `42161`
   * Testnet: `421613`
 
 See also [node access details](/docs/manage-your-node#view-node-access-and-credentials).
 
@@ -368,7 +328,7 @@
 
 <CodeGroup>
   ```javascript Javascript
   const { ethers } = require("ethers");
 
   const provider = new ethers.providers.WebSocketProvider('YOUR_CHAINSTACK_ENDPOINT', NETWORK_ID);
 
@@ -389,12 +349,8 @@
 
 ## Brownie
 
-<Steps>
-  <Step>
-    Install [Brownie](https://eth-brownie.readthedocs.io/en/stable/install.html).
-  </Step>
-  <Step>
-    Use the `brownie networks add` command with the node endpoint:
+1. Install [Brownie](https://eth-brownie.readthedocs.io/en/stable/install.html).
+2. Use the `brownie networks add` command with the node endpoint:
 
    <CodeGroup>
      ```shell Shell
@@ -414,8 +370,6 @@
 
      * Mainnet: `42161`
      * Testnet: `421613`
-  </Step>
-</Steps>
 
 Example to run the deployment script:
 
@@ -427,14 +381,8 @@
 
 ## Foundry
 
-<Steps>
-  <Step>
-    Install [Foundry](https://getfoundry.sh/).
-  </Step>
-  <Step>
-    Use `--rpc-url` to run the operation through your Chainstack node.
-  </Step>
-</Steps>
+1. Install [Foundry](https://getfoundry.sh/).
+2. Use `--rpc-url` to run the operation through your Chainstack node.
 
 ### Forge
 

docs/arbitrum-tutorial-l1-to-l2-messaging-smart-contract.mdx

@@ -1,48 +1,35 @@
 ---
 title: "Arbitrum: L1 to L2 messaging smart contract"
 ---
 
 <Warning>
   ### Deprecation notice
 
   As the Goerli testnet has been deprecated, this guide is for historical reference.
 </Warning>
 
 Sending a message from the Ethereum chain (L1) to the Arbitrum chain (L2) does not involve the state challenge period and is as fast as the block confirmation time on L1 and L2 combined.
 
 In this tutorial, you will:
 
 * Deploy greeter contracts on Ethereum and on Arbitrum.
 * Send a message from the greeter contract deployed on Ethereum (L1) to the greeter contract deployed on Arbitrum (L2).
 
 ## Prerequisites
 
 * [Chainstack account](https://console.chainstack.com/) to deploy an Ethereum node and an Arbitrum node.
 * [MetaMask](https://metamask.io/) to fund your account on L2 with GoerliETH.
 
 ## Overview
 
 To get from zero to your first L1 to L2 message, do the following:
-<Steps>
-  <Step>
-  With Chainstack, create a public chain project.
-  </Step>
-  <Step>
-    With Chainstack, join the Ethereum Goerli testnet.
-  </Step>
-  <Step>
-    With Chainstack, join the Arbitrum Goerli testnet.
-  </Step>
-  <Step>
-    Set up your MetaMask to work through the Chainstack Ethereum and Arbitrum nodes.
-  </Step>
-  <Step>
-    Fund your account through a faucet on the Ethereum Goerli testnet and on the Arbitrum Goerli testnet.
-  </Step>
-  <Step>
-    Run the tutorial script to deploy the contracts on L1 and L2 and send the message from L1 to L2.
-  </Step>
-</Steps>
+
+1. With Chainstack, create a public chain project.
+2. With Chainstack, join the Ethereum Goerli testnet.
+3. With Chainstack, join the Arbitrum Goerli testnet.
+4. Set up your MetaMask to work through the Chainstack Ethereum and Arbitrum nodes.
+5. Fund your account through a faucet on the Ethereum Goerli testnet and on the Arbitrum Goerli testnet.
+6. Run the tutorial script to deploy the contracts on L1 and L2 and send the message from L1 to L2.
 
 ## Step-by-step
 
@@ -50,9 +37,9 @@
 
 See [Create a project](/docs/manage-your-project#create-a-project).
 
 ### Join the Ethereum and Arbitrum Goerli testnets
 
 Deploy a node on the Ethereum Goerli testnet and a node on the Arbitrum Goerli testnet.
 
 See [Join a public network](/docs/manage-your-networks#join-a-public-network).
 
@@ -66,14 +53,14 @@
 
 ### Fund your account
 
 Your account will need Goerli ether on both the Ethereum Goerli testnet and the Arbitrum Goerli testnet as you will deploy a contract on each of the chains.
 
 * Ethereum Goerli faucet
 * Arbitrum Goerli faucet: see [Nitro Goerli Rollup](https://developer.offchainlabs.com/public-chains) in the Arbitrum documentation
 
 The default Arbitrum Goerli faucet may fund your account with 0.001 GoerliETH, which is not enough to deploy the greeter contract on L2.
 
 If you do not have enough GoerliETH on L2, you may bridge some more from the Ethereum Goerli testnet using the [Arbitrum bridge](https://bridge.arbitrum.io/).
 
 ### Clone and prepare the tutorials repository
 
@@ -101,9 +88,9 @@
 
 In the `.env` file, add your account key and the endpoints:
 
 * DEVNET\_PRIVKEY — the private key of your account that has GoerliETH both on the Ethereum Goerli testnet and the Arbitrum Goerli testnet.
 * L2RPC — the Chainstack HTTPS endpoint of your Arbitrum node deployed on the Arbitrum Goerli testnet.
 * L1RPC — the Chainstack HTTPS endpoint of your Ethereum node deployed on the Ethereum Goerli testnet.
 
 Example:
 
@@ -129,24 +116,24 @@
 
 The script will:
 
 * Deploy the L1 greeter contract on the Ethereum Goerli testnet. Example: [0x9B4F541D6A82Beb594Ee2A1EfF14d88f2898176c](https://goerli.etherscan.io/address/0x9B4F541D6A82Beb594Ee2A1EfF14d88f2898176c).
 * Deploy the L2 greeter contract on the Arbitrum Goerli testnet. Example: [0x890443aB733bd527F0036aEd3E249358a30Ff3ce](https://goerli-rollup-explorer.arbitrum.io/address/0x890443aB733bd527F0036aEd3E249358a30Ff3ce).
 * On the L1 contract, [set the L2 contract address](https://goerli.etherscan.io/tx/0xbd20609976a96ce791eae71dae0e87a254f542eab1ab400ce8b4681cc4f6b5aa).
 * On the L2 contract, [set the L1 contract address](https://goerli-rollup-explorer.arbitrum.io/tx/0x98dcfec500561985cdaf0f3933f1b361b3106edc055e0a2644c0f67396596d42/internal-transactions).
 * Retrieve the current gas costs for the transaction off the [ArbRetryableTx contract on L2](https://goerli-rollup-explorer.arbitrum.io/address/0x000000000000000000000000000000000000006E/read-contract#address-tabs). See also Arbitrum documentation: [Messaging Between Layers](https://developer.offchainlabs.com/arbos/l1-to-l2-messaging).
 * Using the retrieved gas cost values, [submit the message transaction on L1](https://goerli.etherscan.io/tx/0xa39ecbb53844d009dc121825c26b0608def2c4117d81a6ebeb6000fcf304ac9e). The transaction will send the message to the [inbox contract on L1](https://goerli.etherscan.io/address/0x6BEbC4925716945D46F0Ec336D5C2564F419682C#readProxyContract). See also Arbitrum documentation: [Contract addresses](https://developer.offchainlabs.com/useful-addresses).
 * The transaction will then be submitted as a retryable ticket by the [ArbRetryableTx contract on L2](https://goerli-rollup-explorer.arbitrum.io/address/0x000000000000000000000000000000000000006E/). [Example](https://goerli-rollup-explorer.arbitrum.io/tx/0xac1f89c9d449145aaa6a715bfb7a678009654191b379c03d20bd0a27b8f6968f).
 * Then the retryable ticket will be redeemed and change the state in the greeter contract on L2 with the message from the greeter contract on L1. [Example](https://goerli-rollup-explorer.arbitrum.io/tx/0x6c8dd56c1ef93064b7b219154327361c051588dfadf716cc23e9d5e3ed610814).
 
 ## Conclusion
 
 This tutorial guided you through the basics of creating and deploying a simple greeter contract that sends a message from the Ethereum chain to the Arbitrum chain. The tutorial also provided the examples and an explanation of the step-by-step state changes and the contracts involved in the L1 to L2 messaging.
 
 ### About the author
 
 <CardGroup>
   <Card title="Ake" img="/images/docs/profile_images/1719912994363326464/8_Bi4fdM_400x400.jpg">
     <Icon icon="code"  iconType="solid"/>Director of Developer Experience @ Chainstack
 
     <Icon icon="screwdriver-wrench"  iconType="solid"/>  Talk to me all things Web3