Md mdx conversion batch 31

arbitrum-docs/partials/_optional-orbit-compatible-cli-flags-partial.md

@@ -15,7 +15,7 @@
 | `--execution.rpc.tx-fee-cap`             | Default: `1`. Transaction fee cap (in ether) for RPC APIs. (0 = no cap).                                                                                                                                                                                                                        |
 | `--ipc.path`                             | Filename for IPC socket/pipe within datadir. 🔉 Not supported on macOS. Note the path is within the Docker container.                                                                                                                                                                           |
 | `--init.prune`                           | Prunes database before starting the node. Can be "full" or "validator".                                                                                                                                                                                                                         |
-| `--init.url="<snapshot file>"`           | (Non-Orbit Nitro nodes only) URL to download the genesis database from. Required only for the first startup of an Arbitrum One node. Reference to [snapshots](https://snapshot.arbitrum.foundation/index.html) and [archive node guide](/run-arbitrum-node/more-types/01-run-archive-node.md).  |
+| `--init.url="<snapshot file>"`           | (Non-Orbit Nitro nodes only) URL to download the genesis database from. Required only for the first startup of an Arbitrum One node. Reference to [snapshots](https://snapshot.arbitrum.foundation/index.html) and [archive node guide](/run-arbitrum-node/more-types/01-run-archive-node.mdx).  |
 | `--init.download-path="/path/to/dir"`    | (Non-Orbit Nitro nodes only) Temporarily saves the downloaded database snapshot. Defaults to `/tmp/`. Used with `--init.url`.                                                                                                                                                                   |
 | `--node.batch-poster.post-4844-blobs`    | Boolean. Default: `false`. Used to enable or disable the posting of transaction data using Blobs to L1 Ethereum. If using calldata is more expensive and if the parent chain supports EIP4844 blobs, the batch poster will use blobs when this flag is set to `true`. Can be `true` or `false`. |
 | `--node.batch-poster.ignore-blob-price`  | Boolean. Default: `false`. If the parent chain supports EIP4844 blobs and `ignore-blob-price` is set to `true`, the batch poster will use EIP4844 blobs even if using calldata is cheaper. Can be `true` or `false`.                                                                            |

arbitrum-docs/run-arbitrum-node/01-overview.md

@@ -11,7 +11,7 @@ In order to be able to _interact with_ or _build applications on_ any of the Arb
 
 Here, you can find resources that help you run different types of Arbitrum nodes:
 
-- Step-by-step instructions for running different Arbitrum nodes, including [full Nitro node](/run-arbitrum-node/03-run-full-node.md), [full Classic node](/run-arbitrum-node/more-types/03-run-classic-node.md), [local dev node](/run-arbitrum-node/04-run-local-dev-node.md), [feed relay](/run-arbitrum-node/sequencer/01-run-feed-relay.md), and [validator](/run-arbitrum-node/more-types/02-run-validator-node.md)
+- Step-by-step instructions for running different Arbitrum nodes, including [full Nitro node](/run-arbitrum-node/03-run-full-node.md), [full Classic node](/run-arbitrum-node/more-types/03-run-classic-node.mdx), [local dev node](/run-arbitrum-node/04-run-local-dev-node.md), [feed relay](/run-arbitrum-node/sequencer/01-run-feed-relay.md), and [validator](/run-arbitrum-node/more-types/02-run-validator-node.mdx)
 - Step-by-step instructions for how to [read the sequencer feed](/run-arbitrum-node/sequencer/02-read-sequencer-feed.md), [build the Nitro locally](/run-arbitrum-node/nitro/01-build-nitro-locally.md) and [run the sequencer coordinator manager UI tool](/run-arbitrum-node/sequencer/03-run-sequencer-coordination-manager.md)
 - Step-by-step instructions for [how to configure a Data Availability Committee](/run-arbitrum-node/data-availability-committees/01-get-started.md)
 - [Troubleshooting page](/run-arbitrum-node/06-troubleshooting.md)

arbitrum-docs/run-arbitrum-node/02-quickstart.md

@@ -43,13 +43,13 @@ For detailed instructions on how to run an Arbitrum full node, see [here](/run-a
 
 While full nodes offer numerous advantages, there are situations where running an archive node may be more appropriate. Archive nodes store the complete history of the Arbitrum network, making them suitable for users who require extensive historical data access or advanced analytical purposes. However, it's important to note that archive nodes are more resource-intensive, requiring significant storage capacity and computational power.
 
-For detailed instructions on how to run an Arbitrum archive node, see [here](/run-arbitrum-node/more-types/01-run-archive-node.md).
+For detailed instructions on how to run an Arbitrum archive node, see [here](/run-arbitrum-node/more-types/01-run-archive-node.mdx).
 
 ### Considerations for running an Arbitrum classic node
 
-The significance of running an Arbitrum classic node is mainly applicable to individuals with specific needs for an archive node and access to classic-related commands. More details can be found [here](/run-arbitrum-node/more-types/01-run-archive-node.md).
+The significance of running an Arbitrum classic node is mainly applicable to individuals with specific needs for an archive node and access to classic-related commands. More details can be found [here](/run-arbitrum-node/more-types/01-run-archive-node.mdx).
 
-For detailed instructions on how to run an Arbitrum classic node, see [here](/run-arbitrum-node/more-types/03-run-classic-node.md).
+For detailed instructions on how to run an Arbitrum classic node, see [here](/run-arbitrum-node/more-types/03-run-classic-node.mdx).
 
 ### Considerations for running a feed relay
 

arbitrum-docs/run-arbitrum-node/more-types/01-run-archive-node.md → arbitrum-docs/run-arbitrum-node/more-types/01-run-archive-node.mdx

@@ -25,7 +25,7 @@ Running an Arbitrum One **full node** in **archive mode** lets you access both p
 | Access the **Arbitrum network** without running your own node                   | Fully managed by third-parties, exposed via RPC endpoints | [RPC endpoints and providers](/build-decentralized-apps/reference/01-node-providers.md)             |
 | Run an **archive node** for **Arbitrum Sepolia (testnet)** or **Arbitrum Nova** | Full node (Nitro)                                         | [How to run a full node (Nitro)](/run-arbitrum-node/03-run-full-node.md)                            |
 | Send **post-Nitro** archive requests                                            | Full node (Nitro)                                         | [How to run a full node (Nitro)](/run-arbitrum-node/03-run-full-node.md)                            |
-| Send **pre-Nitro** archive requests                                             | Full node (Classic)                                       | [How to run a full node (Classic, pre-Nitro)](/run-arbitrum-node/more-types/03-run-classic-node.md) |
+| Send **pre-Nitro** archive requests                                             | Full node (Classic)                                       | [How to run a full node (Classic, pre-Nitro)](/run-arbitrum-node/more-types/03-run-classic-node.mdx) |
 | Send **post-Nitro** _and_ **pre-Nitro** archive requests                        | Full node (Nitro) _and_ full node (Classic)               | That's what this how-to is for; you're in the right place.                                          |
 
 ### System requirements

arbitrum-docs/run-arbitrum-node/nitro/02-migrate-state-and-history-from-classic.md

@@ -22,7 +22,7 @@ Keep in mind that this process only applies to Arbitrum One. Other Arbitrum chai
 
 To successfully migrate the state and history of the chain from a classic (pre-Nitro) node to a Nitro node, you'll need:
 
-- A fully synced classic node: you can find instructions on how to run a classic node in [this page](/run-arbitrum-node/more-types/03-run-classic-node.md).
+- A fully synced classic node: you can find instructions on how to run a classic node in [this page](/run-arbitrum-node/more-types/03-run-classic-node.mdx).
 - A clean, uninitialized Nitro node: you can find instructions on how to set up a Nitro node in [this page](/run-arbitrum-node/03-run-full-node.md).
 
 ## Step 1: Enable export options in your classic node
@@ -88,4 +88,4 @@ This state import operation requires more resources than a regular run of a Nitr
 ## See also
 
 - [How to run a full node (Nitro)](/run-arbitrum-node/03-run-full-node.md)
-- [How to run a full node (Classic, pre-Nitro)](/run-arbitrum-node/more-types/03-run-classic-node.md)
+- [How to run a full node (Classic, pre-Nitro)](/run-arbitrum-node/more-types/03-run-classic-node.mdx)