docs: optimism updates and version update

.vitepress/config.ts

@@ -585,11 +585,7 @@ function sidebarHome() {
                       link: "/developers/gm-portal-bubs",
                     },
                     {
-                      text: "Deploy an OP Stack devnet",
-                      link: "/developers/optimism-devnet",
-                    },
-                    {
-                      text: "Deploy an OP Stack devnet on Celestia",
+                      text: "Run an OP Stack devnet posting Celestia",
                       link: "/developers/optimism",
                     },
                     {
@@ -601,7 +597,7 @@ function sidebarHome() {
                       link: "https://thirdweb.com/bubs-testnet",
                     },
                     {
-                      text: "Rollups-as-a-Service",
+                      text: "Rollups as a Service",
                       collapsed: true,
                       items: [
                         {

developers/blobstream-proof-queries.md

@@ -1,5 +1,8 @@
 ---
 description: Learn how to query the inclusion proofs used in Blobstream
+next:
+  text: "Requesting data commitment ranges"
+  link: "/developers/requesting-data-commitment-ranges"
 ---
 
 # Blobstream proofs queries

developers/blobstream-rollups.md

@@ -1,5 +1,11 @@
 ---
 description: Learn how to build rollups that use Blobstream.
+prev:
+  text: "Ethereum fallback mechanism"
+  link: "/developers/ethereum-fallback"
+next:
+  text: "Submitting data blobs to Celestia"
+  link: "/developers/submit-data"
 ---
 
 # Introduction to Blobstream rollups

developers/blobstream-x-deploy.md

@@ -1,3 +1,9 @@
+---
+next:
+    text: "Celestia-node key"
+    link: "/developers/celestia-node-key"
+---
+
 # New Blobstream X deployments
 
 If you want to deploy Blobstream X to a new chain, where a Gateway 

developers/blobstream-x-requesting-data-commitment-ranges.md

@@ -1,3 +1,9 @@
+---
+prev:
+   text: "Querying the Blobstream proofs"
+   link: "/developers/blobstream-proof-queries"
+---
+
 # Requesting data commitment ranges
 
 By default, the Blobstream X deployments on Ethereum will be

developers/bubs-testnet.md

@@ -1,14 +1,17 @@
 ---
 description: The first testnet built with OP Stack and Celestia.
+next:
+  text: "Deploy a smart contract on Bubs testnet"
+  link: "/developers/deploy-on-bubs"
 ---
 
 # Bubs testnet
 
 ![Bubs testnet](/img/Celestia_Bubs_Testnet.jpg)
 
-[Bubs Testnet](https://bubs-sepolia.hub.caldera.xyz/) is a fresh offering from
-[Caldera](https://caldera.xyz) with support from Celestia Labs,
-built with OP Stack and Celestia, and is dedicated to providing developers with
+[Bubs Testnet](https://bubs-sepolia.hub.caldera.xyz/) 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.
 
 ## Built with the OP Stack and Celestia
@@ -19,27 +22,12 @@ layer. This integration can be found in the
 [@celestiaorg/optimism repository](https://github.com/celestiaorg/optimism).
 The testnet is hosted by [Caldera](https://caldera.xyz),
 who makes it easy to launch rollups with no code required.
-
-In this setup, data handling is accomplished in two ways. Firstly, data is
-written to the DA layer, in this case, Celestia
-(on the [Mocha testnet](../nodes/mocha-testnet.md)). Then, the data
-commitment is written to the `op-batcher`. When reading, the `op-node`
-retrieves the data back from the DA layer by first reading the data commitment
-from the `op-batcher`, then reading the data from the DA layer using the data
-commitment. Hence, while previously `op-node` was reading from `calldata` on
-Ethereum, it now reads data from Celestia.
+Bubs' data is posted to Celestia
+on the [Mocha testnet](../nodes/mocha-testnet.md).
 [View the namespace for Bubs on Celestia's Mocha testnet](https://mocha-4.celenium.io/namespace/000000000000000000000000000000000000ca1de12ad45362e77e87).
 
-The tools involved in the data handling process include `op-batcher`,
-which batches up rollup blocks and posts them to Ethereum, `op-geth`
-that handles execution, and `op-proposer` responsible for state commitment
-submission.
-
-By using Celestia as a DA layer, existing L2s can switch from posting their
-data as `calldata` on Ethereum to posting to Celestia. The commitment to the
-block is posted on Celestia, which is purpose-built for data availability.
-This is more scalable than the traditional method of posting this data as
-`calldata` on monolithic chains.
+[Learn more about the setup of the integration in
+the introduction](./intro-to-op-stack.md#about-the-integration).
 
 ## Building on Bubs
 
@@ -102,8 +90,4 @@ To see the status and uptime information for Bubs,
 
 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:
-
-- [Deploy a smart contract on Bubs testnet](./deploy-on-bubs.md)
-- [Deploy a GM Portal dapp on Bubs testnet](./gm-portal-bubs.md)
-<!-- - [Deploy a smart contract with Thirdweb](https://thirdweb.com/bubs-testnet) -->
+capabilities.

developers/build-whatever.md

@@ -32,7 +32,7 @@ Here are a few options that are currently available for developers.
   <UrlImageButton url="https://rollkit.dev" imageSrc="/build/rollkit.webp" text="Rollkit" notes="Sovereign" alt="Rollkit logo" aria-label="Rollkit"/>
 </div>
 
-### Rollups-as-a-Service
+### Rollups as a Service
 
 Deploy your rollup with a RaaS provider.
 

developers/celestia-node-key.md

@@ -1,8 +1,8 @@
 ---
 description: Use the cel-key utility to generate a wallet on celestia-node.
 prev:
-  text: "Rollkit"
-  link: "/developers/rollkit"
+  text: "New Blobstream X deployments"
+  link: "/developers/blobstream-x-deploy"
 ---
 
 # Create a wallet with celestia-node

developers/deploy-on-bubs.md

@@ -1,3 +1,9 @@
+---
+prev:
+  text: "Bubs testnet"
+  link: "/developers/bubs-testnet"
+---
+
 # Deploy a smart contract on Bubs testnet
 
 In this tutorial, we will deploy a smart contract to the

developers/ethereum-fallback.md

@@ -1,5 +1,11 @@
 ---
 description: The DA fallback mechanism to Ethereum for rollups.
+next:
+  text: "Blobstream rollups"
+  link: "/developers/blobstream-rollups"
+prev:
+  text: "Run an OP Stack devnet posting Celestia"
+  link: "/developers/optimism"
 ---
 
 # Ethereum fallback

developers/intro-to-op-stack.md

@@ -7,43 +7,69 @@ description: Learn about the integration of OP Stack with Celestia.
 [Optimism](https://optimism.io) is a low-cost and lightning-fast Ethereum
 L2 blockchain, built with [the OP Stack](https://stack.optimism.io/).
 
-[Celestia](https://celestia.org) is a modular consensus and data network,
+[Celestia](https://celestia.org) is a modular consensus and data availability (DA) network,
 built to enable anyone to easily deploy their own blockchain with
 minimal overhead.
 
-## About the integration
-
-_Discover how to integrate existing blockchain frameworks
-like the OP Stack with Celestia in this category._
-
-:::tip
-Tested on a machine with 8GB RAM, 160 GB SSD,
-Ubuntu 22.10, and a 4 core AMD CPU.
-:::
+Together, they allow developers to create rollups that
+post data to Celestia and settle on Ethereum.
 
-This is a **beta integration** and we are working on resolving
-[open issues](https://github.com/celestiaorg/optimism/issues).
+## About the integration
 
 [Optimism](https://www.optimism.io/) uses Ethereum as
-a data availability (DA) layer. Currently, settlement and DA for
+a DA layer. Currently, settlement and DA for
 Optimism are on Ethereum, both onchain. `op-batcher` batches up
 rollup blocks and posts to Ethereum.
 
-### Table of contents of the category
+The integration of OP Stack with Celestia underneath for DA
+allows rollup operators to reduce overhead that is associated with posting
+data as `calldata` on Ethereum. Instead, `op-batcher` batches up
+rollup blocks and posts them to Celestia's DA network.
 
-- [Bubs testnet](./bubs-testnet.md)
-- [Deploy a smart contract on Bubs testnet](./deploy-on-bubs.md)
-- [Deploy a GM Portal dapp on Bubs testnet](./gm-portal-bubs.md)
-- [Deploy an OP Stack devnet](./optimism-devnet.md)
-- [Deploy an OP Stack devnet on Celestia](./optimism.md)
+Data is managed in two ways. First, data is written
+to the data availability (DA) layer i.e. in this case Celestia, then the
+data commitment is written to the `op-batcher`. When reading `op-node`
+simply reads the data back from the DA layer by reading the
+data commitment from the `op-batcher` first, then reading the
+data from the DA layer using the data commitment. While
+previously `op-node` was reading from `calldata` on Ethereum, it now reads data from Celestia.
+
+There are a few tools involved in the data handling process. `op-batcher`
+batches up rollup blocks and posts them to Ethereum. `op-geth` handles
+execution, while `op-proposer` is responsible for state commitment
+submission.
 
-## Celestia and OP Stack repository
+By using Celestia as a DA layer, existing L2s can switch from posting
+their data as `calldata` on Ethereum, to posting to Celestia.
+The commitment to the block is posted on Celestia, which is
+purpose-built for data availability. This is a more scalable than
+the traditional method of posting this data as `calldata` on monolithic chains.
+
+### GitHub repository
 
 Find the
 [repository for this integration](https://github.com/celestiaorg/optimism/)
 at `https://github.com/celestiaorg/optimism`.
 
-### What are Optimism and the OP Stack?
+:::warning
+This is a **beta integration** and we are working on resolving
+[open issues](https://github.com/celestiaorg/optimism/issues).
+:::
+
+## Category contents
+
+This category will guide you through interacting with existing OP Stack rollups
+with Celestia underneath, then how to start your own devnet
+with a modified version of `optimism-bedrock` that uses Celestia as a
+DA layer.
+
+- [Bubs testnet](./bubs-testnet.md): learn about
+the first testnet made with OP Stack with Celestia underneath
+- [Deploy a smart contract on Bubs testnet](./deploy-on-bubs.md)
+- [Deploy a GM Portal dapp on Bubs testnet](./gm-portal-bubs.md)
+- [Run an OP Stack devnet posting Celestia](./optimism.md)
+
+<!-- ### What are Optimism and the OP Stack?
 
 Optimism, an Ethereum L2 blockchain, is powered by the OP Stack,
 which is also the foundation for the
@@ -61,47 +87,7 @@ blockchain infrastructure to governance systems. This software suite aims
 to simplify L2 blockchain creation and support the Optimism ecosystem's
 growth and development.
 
-Learn [more about Optimism](https://www.optimism.io/).
-
-### What is Celestia?
-
-Celestia is a modular consensus and data network, built to enable anyone to
-easily deploy their own blockchain with minimal overhead.
-
-Celestia is a minimal blockchain that only orders and publishes transactions
-and does not execute them. By decoupling the consensus and application
-execution layers, Celestia modularizes the blockchain technology stack
-and unlocks new possibilities for decentralized application builders.
-Learn more at [Celestia.org](https://celestia.org).
-
-## OP Stack and Celestia
-
-This category will guide you through how to start your own devnet
-with a modified version of `optimism-bedrock` that uses Celestia as a
-DA layer.
-
-The handling of data is accomplished in two ways. First, data is written
-to the data availability (DA) layer i.e. in this case Celestia, then the
-data commitment is written to the `op-batcher`. When reading `op-node`
-simply reads the data back from the DA layer by reading the
-data commitment from the `op-batcher` first, then reading the
-data from the DA layer using the data commitment. Hence, while
-previously `op-node` was reading from calldata on Ethereum,
-but now it reads data from Celestia.
-
-There are a few tools involved in the data handling process. `op-batcher`
-batches up rollup blocks and posts them to Ethereum. `op-geth` handles
-execution, while `op-proposer` is responsible for state commitment
-submission.
-
-By using Celestia as a DA layer, existing L2s can switch from posting
-their data as `calldata` on Ethereum, to posting to Celestia.
-The commitment to the block is posted on Celestia, which is
-purpose-built for data availability. This is a more scalable than
-the traditional method of posting this data as `calldata` on monolithic chains.
-
-If you'd like to go modular, bedrock has
-made it easy to swap this out!
+Learn [more about Optimism](https://www.optimism.io/). -->
 
 ## Next steps