diff --git a/docs/blob-transactions-the-hard-way.mdx b/docs/blob-transactions-the-hard-way.mdx
index b2cda6ca..e25e8a51 100644
--- a/docs/blob-transactions-the-hard-way.mdx
+++ b/docs/blob-transactions-the-hard-way.mdx
@@ -6,7 +6,7 @@ title: "Blob transactions the hard way"
 * Walks you through crafting and broadcasting blob (type-3) transactions on Ethereum, including creating 128 KB blobs and verifying the KZG commitment and blob versioned hash.
 * Explains how blob data is stored on the consensus layer for 18 days, while the blob versioned hash lives on the execution layer.
 * Dives into EIP-4788 & EIP-4844, detailing how to map execution-layer blocks to consensus-layer slots to fetch and verify blob data.
-* Provides full Python scripts for a “bare bones” approach to building, sending, and verifying blob transactions from start to finish.
+* Provides full Python scripts for a "bare bones" approach to building, sending, and verifying blob transactions from start to finish.
 
 ## Main article
 
@@ -302,7 +302,7 @@ Let's retrieve the blob data from the network.
 
 Since we are working with the consensus layer now, make sure you now use the consensus client endpoint from your Chainstack node details.
 
-Our example transaction is included in [block 6090748](https://sepolia.etherscan.io/txs?block=6090748\&isblob=true) on the execution layer. The call we are going to use is [Retrieve blob sidecar](/reference/ethereum_beacon_chain_api/state/getBlobSidecarByRoot).
+Our example transaction is included in [block 6090748](https://sepolia.etherscan.io/txs?block=6090748&isblob=true) on the execution layer. The call we are going to use is [Retrieve blob sidecar](/reference/getblobsidecarbyslot).
 
 To provide a specific pointer for the blob data on the consensus layer, we can use one of the following:`head`, `genesis`, `finalized`, or `slot_number`.
 
@@ -320,7 +320,7 @@ Here's our call
   ```
 </CodeGroup>
 
-This will retrieve all the four blobs referenced by the four type-3 transactions in [block 6090748](https://sepolia.etherscan.io/txs?block=6090748\&isblob=true) on the execution layer. One of them is our blob data.
+This will retrieve all the four blobs referenced by the four type-3 transactions in [block 6090748](https://sepolia.etherscan.io/txs?block=6090748&isblob=true) on the execution layer. One of them is our blob data.
 
 ### Compute the KZG commitment
 
@@ -415,7 +415,7 @@ This one is less fancy, let's do the hash of our KZG commitment and see if it ma
   ```
 </CodeGroup>
 
-Remember that the blob versioned hash is stored on the execution layer. To retrieve it, you can do a simple [eth\_getTransactionByHash](/reference/ethereum_node_api/transaction_info/eth_getTransactionByHash).
+Remember that the blob versioned hash is stored on the execution layer. To retrieve it, you can do a simple [eth\_getTransactionByHash](/reference/ethereum-gettransactionbyhash).
 
 Example for our transaction on Sepolia:
 
diff --git a/docs/yellowstone-grpc-geyser-plugin.mdx b/docs/yellowstone-grpc-geyser-plugin.mdx
index 18d6923b..225cfaae 100644
--- a/docs/yellowstone-grpc-geyser-plugin.mdx
+++ b/docs/yellowstone-grpc-geyser-plugin.mdx
@@ -34,6 +34,20 @@ Click **Add-ons** > **Yellowstone gRPC Geyser Plugin** > **Install**.
 </Step>
 </Steps>
 
+## Limits
+
+$149/month:
+* Unlimited stream events
+* 5 streams available per platform account
+* Up to 50 Solana accounts per stream
+
+$449/month:
+* Unlimited stream events
+* 25 streams available per platform account
+* Up to 50 Solana accounts per stream
+
+Note that on a dedicated Solana node with Yellowstone gRPC Geyser plugin limit customization is available.
+
 ## Tooling
 
 See: