docs: remove usage of canonical deployment for Blobstream X (#1458)

* docs: remove usage of canonical deployment for Blobstream X

* Update developers/blobstream-x-deploy.md

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* docs: succint => succinct

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

.vitepress/config.ts

@@ -553,7 +553,7 @@ function sidebarHome() {
                   link: "/developers/requesting-data-commitment-ranges",
                 },
                 {
-                  text: "Non-canonical Blobstream X deployments",
+                  text: "New Blobstream X deployments",
                   link: "/developers/blobstream-x-deploy",
                 },
               ],

developers/blobstream-contracts.md

@@ -109,7 +109,7 @@ on Ethereum to query the `BlobstreamX.sol` contract for relayed `DataRootTuple`s
 The single interface method `verifyAttestation` verifies a Merkle inclusion
 proof that a `DataRootTuple` is included under a specific batch (indexed by
 batch nonce). In other words, analogously it verifies that a specific block
-header is included in the canonical Celestia chain.
+header is included in the Celestia chain.
 
 ## Querying the proof
 

developers/blobstream-x-deploy.md

@@ -1,8 +1,7 @@
-# Non-canonical Blobstream X deployments
+# New Blobstream X deployments
 
-If you want to deploy Blobstream X to a new chain, where a
-canonical Succinct Gateway contract does not exist, you
-need to do the following.
+If you want to deploy Blobstream X to a new chain, where a Gateway 
+contract does not exist, you need to do the following.
 
 If Succinct Gateway already exists on this chain, you can skip
 this step.

developers/blobstream.md

@@ -18,7 +18,7 @@ the first with Data Availability Sampling (DAS).
 
 An implementation of Blobstream, by [Succinct](https://docs.succinct.xyz/), called
 [Blobstream X](https://github.com/succinctlabs/blobstreamx), is out
-and will be used in the canonical deployments. This implementation proves the
+and will be used in the upcoming deployments. This implementation proves the
 validity of Celestia block headers on a target EVM chain using zero-knowledge (ZK)
 proofs, which allow inheriting all the security
 guarantees of Celestia.
@@ -97,9 +97,9 @@ along with code for:
 - [The Blobstream X circuits](https://alpha.succinct.xyz/celestia/blobstreamx)
 - [The Blobstream X contract Golang bindings](https://github.com/succinctlabs/blobstreamx/blob/main/bindings/BlobstreamX.go)
 
-Canonical deployments of Blobstream X will be maintained on the
+The first deployments of Blobstream X will be maintained on the
 following chains: Arbitrum One, Base and Ethereum Mainnet. Every 1
-hour, Succinct will post an update to the Blobstream X contract
+hour, the prover/relayer will post an update to the Blobstream X contract
 that will include a new data commitment range that covers a 1-hour
 block range from the `latestBlock` in the Blobstream X contract.
 On Ethereum Mainnet, the Blobstream X contract will be updated

developers/requesting-data-commitment-ranges.md

@@ -1,7 +1,7 @@
 # Requesting data commitment ranges
 
-By default, the Succinct team will be maintaining canonical Blobstream X
-deployments on Ethereum, updating every 4 hours, and on Arbitrum One
+By default, the Blobstream X deployments on Ethereum will be
+updating every 4 hours, and on Arbitrum One
 and Base, updating every 1 hour. If you wish for the Blobstream X contract
 to be updated at a different cadence, then you have several different
 options for how to update the smart contract.