docs: update version of links

developers/arbitrum-full-node.md

@@ -20,7 +20,7 @@ with the difference being that you will use this image:
 in the Arbitrum docs.
 
 Note that you can either use the flags in the nitro binary + the flags
-[found in the celestia package](https://github.com/celestiaorg/nitro/blob/v2.3.3/das/celestia/celestia.go#L53-L65),
+[found in the celestia package](https://github.com/celestiaorg/nitro/blob/fbf5bba3ed76ed30f3c1f5d545d17f1d741940bf/das/celestia/celestia.go#L31-L46),
 or you can just provide a node `config.json` file with the `celestia-cfg`
 for them to run it, which would look something like this:
 
@@ -49,10 +49,10 @@ Configuration options for validating full nodes include:
 poster. The eth-rpc must be WSS. Otherwise, it won't be able to subscribe to events
 for Blobstream.
 - **`blobstream`:** address of the Blobstream X contract on the base chain.
-    - Note that the `SequencerInbox` contract for each chain has a constant
-    address for the `BlobstreamX` contract, thus make sure that the Blobstream X
-    address in the `SequencerInbox` being used for the templates in
-    `RollupCreator` matches the one in your config.
+  - Note that the `SequencerInbox` contract for each chain has a constant
+  address for the `BlobstreamX` contract, thus make sure that the Blobstream X
+  address in the `SequencerInbox` being used for the templates in
+  `RollupCreator` matches the one in your config.
 
 An example configuration with `validator-config` can be found below:
 

developers/arbitrum-integration.md

@@ -39,9 +39,9 @@ The Arbitrum Nitro code has a `DataAvailabilityProvider` interface that is used
 This integration implements the [`DataAvailabilityProvider` interface for Celestia DA](https://github.com/celestiaorg/nitro/blob/966e631f1a03b49d49f25bea67a92b275d3bacb9/arbstate/inbox.go#L366-L477)
 
 Additionally, this integration comes with
-[the necessary code for a Nitro chain node to post and retrieve data from Celestia](https://github.com/celestiaorg/nitro/tree/v2.3.1-rc.1/das/celestia).
+[the necessary code for a Nitro chain node to post and retrieve data from Celestia](https://github.com/celestiaorg/nitro/tree/celestia-v3.0.0/das/celestia).
 
-The core logic behind posting and retrieving data happens in [celestia.go](https://github.com/celestiaorg/nitro/blob/v2.3.1-rc.1/das/celestia/celestia.go) where data is stored on Celestia and serialized into a small batch of data that gets published in the sequencer inbox contract.
+The core logic behind posting and retrieving data happens in [celestia.go](https://github.com/celestiaorg/nitro/blob/celestia-v3.0.0/das/celestia/celestia.go) where data is stored on Celestia and serialized into a small batch of data that gets published in the sequencer inbox contract.
 Then the `Read` logic takes care of taking the deserialized Blob Pointer struct and consuming it in order to fetch the data from Celestia and additionally inform the fetcher about the position of the data on Celestia (we'll get back to this in the next section).
 
 The following represents a non-exhaustive list of considerations when running a Nitro node for a chain with Celestia underneath: