Fix broken internal links and some 404s

how-to-guides/arabica-devnet.md

@@ -175,7 +175,6 @@ There are multiple explorers you can use for Arabica:
 
 - [https://arabica.celenium.io](https://arabica.celenium.io)
 - [https://explorer.celestia-arabica-11.com](https://explorer.celestia-arabica-11.com)
-- [https://celestiascan.com](https://celestiascan.com)
 
 ## Network upgrades
 

how-to-guides/arbitrum-integration.md

@@ -47,7 +47,7 @@ Then the `Read` logic takes care of taking the deserialized Blob Pointer struct
 
 The following represents a non-exhaustive list of considerations when running a Batch Poster node for a chain with Celestia underneath:
 - You will need to use a consensus node RPC endpoint, you can
-[find a list of them for Mocha](../how-to-guides/mocha-testnet#community-rpc-endpoints)
+[find a list of them for Mocha](../how-to-guides/mocha-testnet.md#community-rpc-endpoints)
 - The Batch Poster will only post a Celestia batch to the underlying chain if the height for which it posted is in a recent range in BlobstreamX and if the verification succeeds, otherwise it will discard the batch. Since it will wait until a range is relayed, it can take several minutes for a batch to be posted, but one can always make an on-chain request for the BlobstreamX contract to relay a header promptly.
 
 The following represents a non-exhaustive list of considerations when running a Nitro node for a chain with Celestia underneath:

how-to-guides/bridge-node.md

@@ -84,7 +84,7 @@ add the port after the IP address or use the
 port if you prefer.
 
 Refer to
-[the ports section of the celestia-node troubleshooting page](../how-to-guides/celestia-node-troubleshooting.md#ports)
+[the ports section of the celestia-node troubleshooting page](/how-to-guides/celestia-node-troubleshooting.md#ports)
 for information on which ports are required to be open on your machine.
 
 Using an RPC of your own, or one from the
@@ -136,7 +136,7 @@ celestia bridge start --core.ip validator-1.celestia-arabica-11.com \
   --p2p.network arabica
 ```
 
-You can create your key for your node by [following the `cel-key` instructions](../../tutorials/celestia-node-key).
+You can create your key for your node by [following the `cel-key` instructions](/tutorials/celestia-node-key.md).
 
 Once you start the bridge node, a wallet key will be generated for you.
 You will need to fund that address with Testnet tokens to pay for

how-to-guides/bubs-testnet.md

@@ -9,7 +9,7 @@ next:
 
 ![Bubs testnet](/img/Celestia_Bubs_Testnet.jpg)
 
-[Bubs Testnet](https://bubs-sepolia.hub.caldera.xyz/) is a the first
+[Bubs Testnet](https://bubstestnet.com/) is a the first
 OP Stack testnet with Celestia underneath hosted by
 [Caldera](https://caldera.xyz) with support from Celestia Labs. Bubs is dedicated to providing developers with
 an EVM-compatible execution layer to deploy their EVM applications on.
@@ -37,7 +37,7 @@ execution layer, making it an ideal platform for developers looking to
 build and test applications in a setting that closely mirrors an OP Stack
 rollup on Celestia.
 
-Learn more at [https://bubs-sepolia.hub.caldera.xyz/](https://bubs-sepolia.hub.caldera.xyz/).
+Learn more at <https://bubs-sepolia.hub.caldera.xyz/>.
 
 ### RPC URLs
 
@@ -50,11 +50,11 @@ For the Bubs Testnet, you can connect to the following RPC URLs:
 
 #### HTTPS
 
-- `https://bubs-sepolia.rpc.caldera.xyz/http`
+- `https://bubs.calderachain.xyz/http`
 
 #### WSS
 
-- `wss://bubs-sepolia.rpc.caldera.xyz/ws`
+- `wss://bubs.calderachain.xyz/ws`
 
 This URL serves as the entry point to the Bubs Testnet. You can use it
 in your applications to connect to the testnet and interact with the smart
@@ -67,27 +67,12 @@ Remember, Bubs Testnet is a testing environment!
 Bridging is a process that enables the transfer of assets between
 different blockchains.
 
-To bridge between Ethereum Sepolia and Bubs Testnet,
-visit the [Bubs Testnet bridge](https://bubs-sepolia.bridge.caldera.xyz/).
+To bridge between Ethereum Sepolia and Bubs Testnet, visit the [Bubs Testnet bridge](https://bubs-sepolia.bridge.caldera.xyz/).
 
 ### Faucet
 
-To visit the Bubs testnet faucet, go to
-[`https://bubs-sepolia.hub.caldera.xyz/`](https://bubs-sepolia.hub.caldera.xyz/)
-and click the "Faucet" tab.
-
-### Explorer
-
-To visit the explorer, go to
-[`https://bubs-sepolia.explorer.caldera.xyz/`](https://bubs-sepolia.explorer.caldera.xyz/).
-
-### Status
-
-To see the status and uptime information for Bubs,
-[visit the status page](https://bubs-sepolia.betteruptime.com/).
+To visit the Bubs testnet faucet, go to <https://bubstestnet.com/> and click the "Request Faucet Funds on Bulbs rollup" button.
 
 ## Next steps
 
-Now that you have a better understanding of the Bubs Testnet and its
-integration of OP Stack and Celestia, you can start exploring its
-capabilities.
+Now that you have a better understanding of the Bubs Testnet and its integration of OP Stack and Celestia, you can start exploring its capabilities.

how-to-guides/full-storage-node.md

@@ -73,7 +73,7 @@ node's account balance, a gRPC endpoint of a validator
 (core) node must be passed as directed below.
 
 Refer to
-[the ports section of the celestia-node troubleshooting page](../../how-to-guides/celestia-node-troubleshooting/#ports)
+[the ports section of the celestia-node troubleshooting page](/how-to-guides/celestia-node-troubleshooting.md#ports)
 for information on which ports are required to be open on your machine.
 
 ```sh
@@ -91,7 +91,7 @@ provides the light node with access to state queries (reading balances, submitti
 transactions, and other state-related queries).
 
 You can create your key for your node by following
-[the `cel-key` instructions](../../tutorials/celestia-node-key)
+[the `cel-key` instructions](/tutorials/celestia-node-key.md)
 
 Once you start the full storage node, a wallet key will be generated for you.
 You will need to fund that address with testnet tokens to pay for

how-to-guides/instantiate-testnet.md

@@ -12,7 +12,7 @@ or if you want to test out new features to build as a core developer.
 ## Hardware requirements
 
 You will need to
-[follow hardware requirements](./validator-node#hardware-requirements).
+[follow hardware requirements](./validator-node.md#hardware-requirements).
 
 ## Setup dependencies
 

how-to-guides/light-node.md

@@ -90,7 +90,7 @@ node's account balance, a gRPC endpoint of a validator
 (core) node must be passed as directed below.
 
 Refer to
-[the ports section of the celestia-node troubleshooting page](../../how-to-guides/celestia-node-troubleshooting/#ports)
+[the ports section of the celestia-node troubleshooting page](/how-to-guides/celestia-node-troubleshooting.md#ports)
 for information on which ports are required to be open on your machine.
 
 ::: code-group
@@ -114,7 +114,7 @@ Tip: you can replace the core.ip with a consensus node RPC endpoint from [Mainne
 ### Keys and wallets
 
 You can create your key for your node by running the following command with the
-[`cel-key` utility](../../tutorials/celestia-node-key) in the
+[`cel-key` utility](/tutorials/celestia-node-key.md) in the
 `celestia-node` directory:
 
 ```sh

how-to-guides/mainnet.md

@@ -121,8 +121,8 @@ your own node.
 
 ### Consensus nodes
 
-- [Consensus node](./consensus-node)
-- [Validator node](./validator-node)
+- [Consensus node](./consensus-node.md)
+- [Validator node](./validator-node.md)
 
 #### Community consensus RPC endpoints
 
@@ -283,7 +283,6 @@ There are multiple explorers you can use for Mainnet Beta:
 
 - [https://celenium.io](https://celenium.io)
 - [https://celestia.explorers.guru](https://celestia.explorers.guru)
-- [https://explorer.modular.cloud/celestia-mainnet](https://explorer.modular.cloud/celestia-mainnet)
 - [https://mintscan.io/celestia](https://mintscan.io/celestia)
 - [https://explorer.nodestake.top/celestia](https://explorer.nodestake.top/celestia)
 - [https://stakeflow.io/celestia](https://stakeflow.io/celestia)

how-to-guides/mocha-testnet.md

@@ -24,8 +24,8 @@ participate in Mocha:
 
 Consensus:
 
-- [Consensus node](./full-consensus-node)
-- [Validator node](./validator-node)
+- [Consensus node](./consensus-node.md)
+- [Validator node](./validator-node.md)
 
 Data Availability:
 
@@ -136,19 +136,19 @@ as REST endpoints. This allows for communication with the node using REST
 calls, which can be useful if the client does not support gRPC or HTTP2.
 The default port is 1317.
 
-- [https://api-mocha.pops.one](https://api-mocha.pops.one)
-- [https://api.celestia-mocha.com/](https://api.celestia-mocha.com/)
-- [https://celestia-testnet.brightlystake.com/api](https://celestia-testnet.brightlystake.com/api)
-- [https://api-celestia-mocha.trusted-point.com](https://api-celestia-mocha.trusted-point.com)
-- [https://api-celestia-testnet-01.stakeflow.io/](https://api-celestia-testnet-01.stakeflow.io/)
-- [https://mocha.api.cumulo.me/](https://mocha.api.cumulo.me/)
-- [https://api.archive.mocha.cumulo.com.es](https://api.archive.mocha.cumulo.com.es)
-- [https://api-mocha-full.avril14th.org](https://api-mocha-full.avril14th.org)
-- [https://api-1.testnet.celestia.nodes.guru](https://api-1.testnet.celestia.nodes.guru)
-- [https://api-2.testnet.celestia.nodes.guru](https://api-2.testnet.celestia.nodes.guru)
-- [https://celestia-testnet-api.itrocket.net](https://celestia-testnet-api.itrocket.net)
-- [https://api-celestia-testnet.cryptech.com.ua](https://api-celestia-testnet.cryptech.com.ua)
-- [https://celestia-t-api.noders.services](https://celestia-t-api.noders.services)
+- `https://api-mocha.pops.one`
+- `https://api.celestia-mocha.com/`
+- `https://celestia-testnet.brightlystake.com/api`
+- `https://api-celestia-mocha.trusted-point.com`
+- `https://api-celestia-testnet-01.stakeflow.io/`
+- `https://mocha.api.cumulo.me/`
+- `https://api.archive.mocha.cumulo.com.es`
+- `https://api-mocha-full.avril14th.org`
+- `https://api-1.testnet.celestia.nodes.guru`
+- `https://api-2.testnet.celestia.nodes.guru`
+- `https://celestia-testnet-api.itrocket.net`
+- `https://api-celestia-testnet.cryptech.com.ua`
+- `https://celestia-t-api.noders.services`
 
 ## Community gRPC endpoints
 
@@ -225,21 +225,20 @@ Faucet has a limit of 10 tokens per week per address/Discord ID.
 
 The following websites provide analytics for Mocha Testnet:
 
-- [https://cosmoslist.co/testnet/celestia](https://cosmoslist.co/testnet/celestia)
+- <https://cosmoslist.co/testnet/celestia>
 
 ## Explorers
 
 There are several explorers you can use for Mocha:
 
-- [https://testnet.mintscan.io/celestia-testnet](https://testnet.mintscan.io/celestia-testnet)
-- [https://celestiascan.com](https://celestiascan.com)
-- [https://mocha.celenium.io](https://mocha.celenium.io)
-- [https://explorer.nodestake.top/celestia-testnet/](https://explorer.nodestake.top/celestia-testnet)
-- [https://stakeflow.io/celestia-testnet](https://stakeflow.io/celestia-testnet)
-- [https://testnet.celestia.explorers.guru](https://testnet.celestia.explorers.guru)
-- [https://testnet.itrocket.net/celestia](https://testnet.itrocket.net/celestia)
-- [https://explorers.cryptech.com.ua/Celestia-Testnet](https://explorers.cryptech.com.ua/Celestia-Testnet)
-- [https://testnet.celestia.valopers.com/](https://testnet.celestia.valopers.com/)
+- `https://testnet.mintscan.io/celestia-testnet`
+- `https://mocha.celenium.io`
+- `https://explorer.nodestake.top/celestia-testnet/`
+- `https://stakeflow.io/celestia-testnet`
+- `https://testnet.celestia.explorers.guru`
+- `https://testnet.itrocket.net/celestia`
+- `https://explorers.cryptech.com.ua/Celestia-Testnet`
+- `https://testnet.celestia.valopers.com/`
 
 ## Network upgrades
 

how-to-guides/multiaccounts.md

@@ -60,7 +60,7 @@ use the [`cel-key` library](https://github.com/celestiaorg/celestia-node/blob/ma
 ./cel-key import
 ```
 Learn more on the
-[Create a wallet with celestia-node](./celestia-node-key#create-a-wallet-with-celestia-node)
+[Create a wallet with celestia-node](/tutorials/celestia-node-key.md#create-a-wallet-with-celestia-node)
 page.
 
 ## Optional flags for write transactions

how-to-guides/nodes-overview.md

@@ -11,10 +11,10 @@ Celestia node operators can run several options on the network.
 
 Consensus:
 
-- [Validator node](./validator-node):
+- [Validator node](./validator-node.md):
   This type of node participates
   in consensus by producing and voting on blocks.
-- [Consensus node](./consensus-node): A celestia-app full node
+- [Consensus node](./consensus-node.md): A celestia-app full node
   to sync blockchain history.
 
 Data Availability:

how-to-guides/rollup-stacks.md

@@ -86,7 +86,7 @@ any monolithic chain. But, the data of those transactions get sent to a
 layer 1 blockchain to carry out the remaining functions.
 
 If you want to brush up on your understanding of modular blockchains,
-head over to [learn modular](../learn/how-celestia-works/monolithic-vs-modular).
+head over to [learn modular](../learn/how-celestia-works/monolithic-vs-modular.md).
 
 ## Benefits of modular blockchains
 

how-to-guides/sp1-blobstream-deploy.md

@@ -26,7 +26,7 @@ cd sp1-blobstream
 [sp1-blobstream README](https://github.com/succinctlabs/sp1-blobstream?tab=readme-ov-file#deployment).
 
 3. If you're deploying on a chain where there isn't a canonical verifier listed in the
-[SP1 contract addresses](https://github.com/succinctlabs/sp1/blob/main/book/onchain-verification/contract-addresses.md), you'll need to:
+[SP1 contract addresses](https://github.com/succinctlabs/sp1/blob/main/book/verification/onchain/contract-addresses.md), you'll need to:
 
    a. Deploy your own SP1 Verifier from the [sp1-contracts](https://github.com/succinctlabs/sp1-contracts) matching your `sp1-sdk` version.
    b. Set the `SP1_VERIFIER_ADDRESS` in your `.env` file to the address of your deployed verifier.

how-to-guides/submit-data.md

@@ -190,7 +190,7 @@ Using `blob.Submit`:
 celestia blob submit <hex-encoded namespace> <hex-encoded data>
 ```
 
-Learn more in the [node tutorial](./node-tutorial.md).
+Learn more in the [node tutorial](/tutorials/node-tutorial.md).
 
 ### The celestia-node API golang client
 

how-to-guides/validator-node.md

@@ -30,7 +30,7 @@ The following tutorial is done on an Ubuntu Linux 20.04 (LTS) x64
 instance machine.
 
 First, follow the instructions on
-[setting up a consensus node](/how-to-guides/consensus-node#set-up-a-consensus-node).
+[setting up a consensus node](/how-to-guides/consensus-node/md#set-up-a-consensus-node).
 
 ### Wallet
 
@@ -117,7 +117,7 @@ celestia bridge init --core.ip <URI>
 
 :::tip
 Refer to
-[the ports section of the celestia-node troubleshooting page](../../how-to-guides/celestia-node-troubleshooting/#ports)
+[the ports section of the celestia-node troubleshooting page](/how-to-guides/celestia-node-troubleshooting.md#ports)
 for information on which ports are required to be open on your machine.
 :::
 
@@ -138,7 +138,7 @@ celestia bridge start
 #### Optional: start the bridge node with SystemD
 
 Follow
-[the tutorial on setting up the bridge node as a background process with SystemD](../systemd).
+[the tutorial on setting up the bridge node as a background process with SystemD](/how-to-guides/systemd.md).
 
 You have successfully set up a bridge node that is syncing with the network.
 

tutorials/integrate-celestia.md

@@ -14,12 +14,11 @@ explorers, integrating the Celestia network.
 
 When getting started with Celestia, we recommend checking out these resources first:
 
-- [Introduction to Celestia](../learn/how-celestia-works/overview.md)
-- [Monolithic v. Modular](../learn/how-celestia-works/monolithic-vs-modular.md)
-- [Celestia's DA Layer](../learn/how-celestia-works/data-availability-layer.md)
-- [Learn modular](https://celestia.org/learn)
-- [Overview to running nodes on Celestia](../how-to-guides/nodes-overview.md)
-- [Rollup stacks](./rollup-stacks.md)
+- [Introduction to Celestia](/learn/how-celestia-works/overview.md)
+- [Monolithic v. Modular](/learn/how-celestia-works/monolithic-vs-modular.md)
+- [Celestia's DA Layer](/learn/how-celestia-works/data-availability-layer.md)
+- [Overview to running nodes on Celestia](/how-to-guides/nodes-overview.md)
+- [Rollup stacks](/how-to-guides/rollup-stacks.md)
 
 ## Celestia service provider notes