converting file to mdx; fixing broken links

pete-vielhaber · pete-vielhaber · commit d93158796d8e · 2025-12-15T11:56:38.000-06:00
diff --git a/docs/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/02-deploying-an-arbitrum-chain.mdx b/docs/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/02-deploying-an-arbitrum-chain.mdx
@@ -22,7 +22,7 @@ You can explore the code of these contracts in the [nitro-contracts repository](
 
 Upon deployment, an Arbitrum chain can be configured as a <a data-quicklook-from="arbitrum-rollup-chain">Rollup</a> or <a data-quicklook-from="arbitrum-anytrust-chain">AnyTrust</a> chain, and use `ETH` or any standard `ERC-20 `token as its gas token.
 
-This page explains how to deploy an <a data-quicklook-from="arbitrum-chain">Arbitrum chain</a> using the Arbitrum Chain SDK. See the [Overview](/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.md) for an introduction to the process of creating and configuring an Arbitrum chain.
+This page explains how to deploy an <a data-quicklook-from="arbitrum-chain">Arbitrum chain</a> using the Arbitrum Chain SDK. See the [Overview](/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.mdx) for an introduction to the process of creating and configuring an Arbitrum chain.
 
 :::info About custom gas token Arbitrum chains
 
diff --git a/docs/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/05-deploying-token-bridge.mdx b/docs/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/05-deploying-token-bridge.mdx
@@ -16,11 +16,11 @@ The Arbitrum stack doesn't natively support specific token bridging standards at
 
 The token bridge architecture includes contracts deployed on the parent and child chains. These entities communicate via the <a data-quicklook-from='retryable-ticket'>retryable ticket</a> protocol, ensuring efficient and secure interactions.
 
-Once you have deployed your Arbitrum chain and have a node running, you can deploy a token bridge for your chain. See the [Overview](/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.md) for an introduction to creating and configuring an Arbitrum chain.
+Once you have deployed your Arbitrum chain and have a node running, you can deploy a token bridge for your chain. See the [Overview](/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.mdx) for an introduction to creating and configuring an Arbitrum chain.
 
 Before reading this guide, we recommend:
 
-- Becoming familiar with the general process of creating new chains explained in [How to deploy an Arbitrum chain](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/02-deploying-an-arbitrum-chain.md)
+- Becoming familiar with the general process of creating new chains explained in [How to deploy an Arbitrum chain](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/02-deploying-an-arbitrum-chain.mdx)
 - Learning about the canonical token bridge in the [Token bridging](/build-decentralized-apps/token-bridging/01-overview.mdx) section
 
 ## Parameters used when deploying a token bridge
diff --git a/docs/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/07-canonical-factory-contracts.mdx b/docs/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/07-canonical-factory-contracts.mdx
@@ -14,7 +14,7 @@ This page describes the benefits of using these canonical factory contracts and
 
 :::info Use the Arbitrum Chain SDK
 
-You can use these contracts to create Arbitrum chains. However, it is strongly recommended to go through the [Chain SDK](/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.md) to interact with them. Doing so prevents misconfiguring parameters and using appropriate defaults for most of them.
+You can use these contracts to create Arbitrum chains. However, it is strongly recommended to go through the [Chain SDK](/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.mdx) to interact with them. Doing so prevents misconfiguring parameters and using appropriate defaults for most of them.
 
 :::
 
diff --git a/docs/launch-arbitrum-chain/05-customize-your-chain/customize-arbos.mdx b/docs/launch-arbitrum-chain/05-customize-your-chain/customize-arbos.mdx
@@ -109,7 +109,7 @@ It should be noted that when you initialize the state (initial code is in [custo
 Also, please make sure your program cannot call the `state.SetNewMyNumber` or other functions may change the value of `myNumber` before ArbOS v21.
 To prevent this, if you are using an external call to the precompile contract to change the value, you can refer to [point 1](./customize-arbos.mdx#1-add-a-new-method-to-existing-precompile-on-a-specific-arbos-version) or
 [point 2](./customize-arbos.mdx#2-create-a-new-precompile-contract-on-a-specific-arbos-version) to set the activation time of the precompile contract method.
-If your nitro code needs to call this method to change the state, you can continue reading [point 4](./customize-arbos.mdx#4-any-changes-in-the-stf-logic-that-will-affect-the-final-execution-result).
+If your nitro code needs to call this method to change the state, you can continue reading [Step 4](./customize-arbos.mdx#4-any-changes-in-the-stf-logic-that-will-affect-the-final-execution-result-arbos-version-control).
 
 ### 4. Any changes in the STF logic that will affect the final execution result (ArbOS version control)
 
diff --git a/docs/launch-arbitrum-chain/06-third-party-integrations/01-bridged-usdc-standard.md b/docs/launch-arbitrum-chain/06-third-party-integrations/01-bridged-usdc-standard.md
@@ -41,7 +41,7 @@ Other requirements:
 
 - It is assumed there is already a `USDC` token deployed and used on the parent chain.
 - Also, it is assumed that the standard Arbitrum chain ownership system is used, i.e., `UpgradeExecutor` is the owner of the `ownable` contracts, and there is an EOA or multi-sig that has the executor role on the `UpgradeExecutor`.
-- Refer to the [token bridge overview page](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/05-deploying-token-bridge.md) for more information about the token bridge design and operational dynamics. You can learn more in our [overview of gateways operating models](/build-decentralized-apps/token-bridging/03-token-bridge-erc20.mdx#other-flavors-of-gateways).
+- Refer to the [token bridge overview page](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/05-deploying-token-bridge.mdx) for more information about the token bridge design and operational dynamics. You can learn more in our [overview of gateways operating models](/build-decentralized-apps/token-bridging/03-token-bridge-erc20.mdx#other-flavors-of-gateways).
 
 ## Deployment steps
 
diff --git a/docs/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.mdx b/docs/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.mdx
@@ -38,12 +38,12 @@ Additionally, Arbitrum chains can be configured to use `ETH` or any standard `ER
 
 ## 2. Deploy your chain
 
-After selecting a chain type, follow [this guide](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/02-deploying-an-arbitrum-chain.md) to deploy your chain using the Chain SDK.
+After selecting a chain type, follow [this guide](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/02-deploying-an-arbitrum-chain.mdx) to deploy your chain using the Chain SDK.
 
 ## 3. Configure your Arbitrum chain's node
 
 Once the chain is deployed, you'll need to generate the configuration to run its node. To learn how, visit [Configure your Arbitrum chain's node](/launch-arbitrum-chain/how-tos/arbitrum-chain-sdk-preparing-node-config.md).
 
 ## 4. Deploy your Arbitrum chain's token bridge
 
-Your Arbitrum chain's token bridge contracts allow `ERC-20` tokens to move between your Arbitrum chain and its underlying parent chain. Read [Deploy your Arbitrum chain's token bridge](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/05-deploying-token-bridge.md) to learn how to set up your bridge.
+Your Arbitrum chain's token bridge contracts allow `ERC-20` tokens to move between your Arbitrum chain and its underlying parent chain. Read [Deploy your Arbitrum chain's token bridge](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/05-deploying-token-bridge.mdx) to learn how to set up your bridge.
diff --git a/docs/launch-arbitrum-chain/features/common/configure-aep/configure-aep-fees.mdx b/docs/launch-arbitrum-chain/features/common/configure-aep/configure-aep-fees.mdx
@@ -45,7 +45,7 @@ The configuration ensures compliance with the AEP terms, streamlines reporting,
 
 :::warning Caution
 
-This is an abbreviated set of instructions on how to configure AEP fees. For a complete set of instructions refer to the [AEP fee router introduction](/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/01-aep-fee-router-introductions.mdx).
+This is an abbreviated set of instructions on how to configure AEP fees. For a complete set of instructions refer to the [AEP fee router introduction](/launch-arbitrum-chain/02-configure-your-chain/advanced-configurations/aep-fee-router/01-aep-fee-router-introduction.mdx).
 
 Additional resources:
 
diff --git a/docs/launch-arbitrum-chain/features/common/data-availability/choose-anytrust.mdx b/docs/launch-arbitrum-chain/features/common/data-availability/choose-anytrust.mdx
@@ -26,7 +26,7 @@ It's ideal for use cases where ultra-low fees are a priority over Ethereum's ful
 
 <AnytrustPCPartial />
 
-This option reflects the growing trend toward modular <a data-quicklook-from="blockchain">blockchain</a> architectures, where DA handling is separate to scale ecosystems like Arbitrum without compromising core security. For implementation, refer to the docs or your RaaS; a [list of RaaSes is on the Third-party providers page](/launch-arbitrum-chain/06-third-party-integrations/02-third-party-providers.md#rollup-as-a-service-providers).
+This option reflects the growing trend toward modular <a data-quicklook-from="blockchain">blockchain</a> architectures, where DA handling is separate to scale ecosystems like Arbitrum without compromising core security. For implementation, refer to the docs or your RaaS; a [list of RaaSes is on the Third-party providers page](/launch-arbitrum-chain/06-third-party-integrations/02-third-party-providers.md#rollup-as-a-service-raas-providers).
 
 ## How to configure
 
diff --git a/docs/launch-arbitrum-chain/features/common/data-availability/choose-rollup.mdx b/docs/launch-arbitrum-chain/features/common/data-availability/choose-rollup.mdx
@@ -32,4 +32,4 @@ For implementation, refer to the docs or your <a data-quicklook-from="raas">RaaS
 
 For an example standard (`ETH` as gas token) configuration of deploying an Arbitrum chain as a Rollup, refer to the [`create-rollup-eth`](https://github.com/OffchainLabs/arbitrum-chain-sdk/tree/main/examples/create-rollup-eth) example in the Arbitrum Chain SDK repo.
 
-To use a custom gas token you can read more on the [Use a custom gas token Rollup](/launch-arbitrum-chain/02-configure-your-chain/02-use-a-custom-gas-token-rollup.mdx) page, or you can view an example deployment configuration in the Arbitrum Chain SDK repo, [`create-rollup-custom-fee-token`](https://github.com/OffchainLabs/arbitrum-chain-sdk/tree/main/examples/create-rollup-custom-fee-token).
+To use a custom gas token you can read more on the [Use a custom gas token Rollup](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx) page, or you can view an example deployment configuration in the Arbitrum Chain SDK repo, [`create-rollup-custom-fee-token`](https://github.com/OffchainLabs/arbitrum-chain-sdk/tree/main/examples/create-rollup-custom-fee-token).
diff --git a/docs/launch-arbitrum-chain/features/common/gas-and-fees/choose-custom-gas-token.mdx b/docs/launch-arbitrum-chain/features/common/gas-and-fees/choose-custom-gas-token.mdx
@@ -41,4 +41,4 @@ For implementation, refer to the docs or your <a data-quicklook-from="raas">RaaS
 For detailed instructions on how to configure a custom gas token, there are several resources available depending on your data availability type:
 
 - **AnyTrust**: [How to configure a custom gas token for your AnyTrust Arbitrum chain](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/01-use-a-custom-gas-token-anytrust.mdx)
-- **Rollup**: [How to configure a custom gas token for your Rollup Arbitrum chain](launch-arbitrum-chain/02-configure-your-chain/common-configurations/01-use-a-custom-gas-token-rollup.mdx)
+- **Rollup**: [How to configure a custom gas token for your Rollup Arbitrum chain](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx)
diff --git a/docs/launch-arbitrum-chain/features/common/validation-and-security/choose-bold.mdx b/docs/launch-arbitrum-chain/features/common/validation-and-security/choose-bold.mdx
@@ -38,7 +38,7 @@ BoLD is required for Rollup mode with custom gas tokens posting to Ethereum (to
 
 :::info Still unsure?
 
-The [BoLD adoption for Arbitrum chains](/launch-arbitrum-chain/02-configure-your-chain/bold-adoption-for-arbitrum-chains.mdx) page has a lot more detailed specifics about the inner workings of BoLD if you are unsure about whether to adopt it for your chain.
+The [BoLD adoption for Arbitrum chains](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/bold-adoption-for-arbitrum-chains.mdx) page has a lot more detailed specifics about the inner workings of BoLD if you are unsure about whether to adopt it for your chain.
 
 Additional resources are:
 
@@ -50,6 +50,6 @@ Additional resources are:
 
 ## How to configure
 
-For specfics on configuration refer to the [How to adopt Arbitrum BoLD](/launch-arbitrum-chain/02-configure-your-chain/bold-adoption-for-arbitrum-chains.mdx#how-to-adopt-arbitrum-bold) section on that page.
+For specfics on configuration refer to the [How to adopt Arbitrum BoLD](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/bold-adoption-for-arbitrum-chains.mdx#how-to-adopt-arbitrum-bold) section on that page.
 
 This upgrade aligns with Arbitrum's modular ethos, bolstering trust-minimization while inheriting Ethereum's security. For implementation, refer to the official docs, or your <a data-quicklook-from="raas">RaaS</a>; a [list of RaaSes is on the Third-party providers page](/launch-arbitrum-chain/06-third-party-integrations/02-third-party-providers.md#rollup-as-a-service-raas-providers).
diff --git a/docs/launch-arbitrum-chain/how-tos/arbitrum-chain-sdk-preparing-node-config.md b/docs/launch-arbitrum-chain/how-tos/arbitrum-chain-sdk-preparing-node-config.md
@@ -12,9 +12,9 @@ import RaaSNotice from '../partials/_raas-providers-notice.mdx';
 
 <RaaSNotice />
 
-Once you have successfully deployed and initialized the Arbitrum chain core contracts, the next step is to configure and run an Arbitrum <a data-quicklook-from="arbitrum-nitro">Nitro</a> node for your chain. You configure a Nitro node using a `JSON` file describing all the parameters for the node, including settings for the batch poster, validator, and the chain itself. See the [Overview](/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.md) for an introduction to creating and configuring an Arbitrum chain.
+Once you have successfully deployed and initialized the Arbitrum chain core contracts, the next step is to configure and run an Arbitrum <a data-quicklook-from="arbitrum-nitro">Nitro</a> node for your chain. You configure a Nitro node using a `JSON` file describing all the parameters for the node, including settings for the batch poster, validator, and the chain itself. See the [Overview](/launch-arbitrum-chain/arbitrum-chain-sdk-introduction.mdx) for an introduction to creating and configuring an Arbitrum chain.
 
-Before reading this guide, we recommend that you're familiar with the general process for creating new chains explained in the introduction and the first section of [How to deploy an Arbitrum chain](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/02-deploying-an-arbitrum-chain.md).
+Before reading this guide, we recommend that you're familiar with the general process for creating new chains explained in the introduction and the first section of [How to deploy an Arbitrum chain](/launch-arbitrum-chain/03-deploy-an-arbitrum-chain/02-deploying-an-arbitrum-chain.mdx).
 
 ## Structure of a Nitro node configuration JSON object
 

Original file line number	Diff line number	Diff line change
`@@ -32,4 +32,4 @@ For implementation, refer to the docs or your <a data-quicklook-from="raas">RaaS`
`32`	`32`
`33`	`33`	For an example standard (`ETH` as gas token) configuration of deploying an Arbitrum chain as a Rollup, refer to the [`create-rollup-eth`](https://github.com/OffchainLabs/arbitrum-chain-sdk/tree/main/examples/create-rollup-eth) example in the Arbitrum Chain SDK repo.
`34`	`34`
`35`		-To use a custom gas token you can read more on the [Use a custom gas token Rollup](/launch-arbitrum-chain/02-configure-your-chain/02-use-a-custom-gas-token-rollup.mdx) page, or you can view an example deployment configuration in the Arbitrum Chain SDK repo, [`create-rollup-custom-fee-token`](https://github.com/OffchainLabs/arbitrum-chain-sdk/tree/main/examples/create-rollup-custom-fee-token).
	`35`	+To use a custom gas token you can read more on the [Use a custom gas token Rollup](/launch-arbitrum-chain/02-configure-your-chain/common-configurations/02-use-a-custom-gas-token-rollup.mdx) page, or you can view an example deployment configuration in the Arbitrum Chain SDK repo, [`create-rollup-custom-fee-token`](https://github.com/OffchainLabs/arbitrum-chain-sdk/tree/main/examples/create-rollup-custom-fee-token).